@paulocheque / @RevMob,
First of all I must say that I like Revmob very much…but…
As a former Test manager (yes…I switched to the dark side
), I can see that RevMobSDK has symptoms of a bad test/quality process. Maybe you even don’t have an explicit test process at all.
This is a bad thing because:
- Inefficient development process, you spend to much time on releasing bug fixes and communicating about it
- You let us, the developers, test the stuff you should do. App developers spend, unnecessary, a lot of to time with testing if a new revMob build still works. This is very frustrating.
Please rethink you release process and make testing explicitly part of it. The effort is minimal and your gain is huge!
A few things:
- Define separate testlevels…at least 2: development tests + e2e acceptance test.
- Define a time slot for the acceptance test in your dev process
- Define acceptance criteria for accepting a new release (how many open defects, which functionality should work, x% test coverage, etc…)
- Make, for all test levels, test scripts for current + new functionality…
- The person who decides to release a new build, should decide this with input of results of the e2e acceptance test. So he should have insight in the quality of the release candidate.
This sounds like much effort but defining a explicit test process, introducing acceptance test + make test scripts for it, is maybe 1 day work!. executing an e2e acceptance test is just 2 hours extra per release…but you need eventually less bug fix releases…so you save time!
Just my 2ct [import]uid: 106768 topic_id: 25797 reply_id: 132228[/import]