How well Rails developers actually test their apps
source link: https://blog.arkency.com/how-well-rails-developers-actually-test-their-apps/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
How well Rails developers actually test their apps
Here are the results of our State of Testing in Rails apps survey results. I have distilled the most interesting numbers for your reading pleasure and efficiency. Detailed charts here. I have highlighted what stands out as interesting for me. Number of surveyees: 142. Thanks for being one!
- 80% favor RSpec
- 79% find testing is inseparable from software development
- 54% say their app is well-tested
- 93% rely on unit tests
- 30% work with a project with over 100 db tables
- 33% work in a team of two or three
- 18% run a single test in “blink of an eye”, 46% under 5s
- 19% need more than half an hour to run the full suite on a development machine
- 86% run their tests on CI
- 15% wait longer than half an hour for CI result
- 60% are “pretty much” confident in their test suite
- 57% drop everything and fix the build, if it happens to fail
- 57% say their biggest problem with tests is that they take ages to run
- 39% never allow skipped test cases
- 83% say tests help them refactor code
- 23% say they mostly test their JavaScript code
- 73% use mocks, 72% stubs, 35% fakes
- 39% do not assess coverage, 56% use simplecov
- 32% do not aim for a specific coverage level, 31% aim for over 90%
- 17% often get frustrated by random test failures
- 32% just retry the build upon encountering a random failure
- 50% do TDD sometimes, 23% do often, 9% do always
Want to see detailed charts? Jump into this twitter thread. Also, it’s the best place to comment or ask further questions.
Now, a plug 🔌. Join ARKADEMY.DEV and get access to our best courses: Rails Architect Masterclass, Anti-IF course, Blogging for busy programmers, Async Remote, TDD video class, Domain-Driven Rails video course and growing!
Recommend
-
184
Common Excuses Why Developers Don’t Test Their SoftwareExcuses for Not Testing Software — The Experts Guide (ISBN 6c6d66616f)I have never met a single pr...
-
11
Load Test Your Rails Apps with Apache JMeter Every Rails app has a breaking point; a level of activity that it simply cannot handle. Your braking point depends on big arch...
-
19
We want you! Well, no, actually, no, not really. Writing Software, technology, sysadmin war stories, and more. Friday, June 21, 2013 We want you! Well,...
-
3
Human resource management How to Get Employees to (Actually) Participate in Well-Being Programs ...
-
2
Twenty Questions... well, actually just TwoAuthor: Graham Mitchell Filename: TwentyQuestions.java Twenty Questions... well, actually just Two Make a program which plays a simple game of
-
4
What you think is bad about remote work, can, well, actually be good. 22 May 2020 I’ve been working remotely full-time at Sourcegraph for slightly over a year now and, in the five ye...
-
0
Birchtree By Matt Birchler I've been writing here since 2010! Back when personal blogs were all the rage. Kids, a...
-
2
Interview with Josh Grant about JavaScript fuzz testing "If developers get enabled to test their own code, everybody wins" JavaScript...
-
5
Phones are getting packed with AI features. But how helpful are they?We tried some of the most common AI tools built into modern phones to find the good and the gimmicky
-
6
Does sinusoid Positional Embeddings actually work well? The GPT part of my
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK