10
votes
Accepted
Should I be unit testing during prototyping/preparing for beta?
I've worked on projects with no testing, development driven testing and actual red-green-refactor TDD, and what you describe is something I might have written before trying actual TDD.
I’ve rapidly ...
- 11.5k
6
votes
Are API-changes expected in beta releases?
To cite from Semantic Versioning 2.0.0
Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
Hence, if you talking ...
- 2,434
5
votes
Accepted
Are API-changes expected in beta releases?
As you have mentioned, your users are currently complaining on the road to a new major version.
Isn't it expected that due to a major version bump the API may change?
Either you don't make ...
- 718
3
votes
Should I be unit testing during prototyping/preparing for beta?
Testing early is important – but not everything has to be tested, and a lot of code is not served well by TDD-style unit tests.
For a prototype, it's completely fine to temporarily ignore best ...
- 135k
2
votes
Accepted
Justifications for developing applications that work on beta versions of iOS?
Beta releases are by definition "works in progress". Until the vendor (Apple in this case) formally releases the software, there are no guarantees as to what will be in the final release (a feature ...
- 13.8k
2
votes
Accepted
Is it a bad idea to use a Beta warning on an onworking web application?
Releasing a piece of software as not beta should only be done after testing. You will lose most of your customers, when only one GUI element is not working. For example, a well known online clothing ...
- 136
Only top scored, non community-wiki answers of a minimum length are eligible