New answers tagged agile-testing
0
I'm a huge fan of relying primarily on exploratory testing, possibly with checklists of features or James Bach's "Session Based Testing" approach, for the majority (or all) of the manual testing work. I find checklists or sessions help to avoid holes in exploratory testing. I prefer to run through manual test scripts / test cases only once I am confident ...
2
As Suchit said, it depends a lot on the nature of the update. I've seen a one-line code change trigger a full regression because that one line happened to be in one of the core calculation engines.
My suggestion for any development process, whether agile or not, is to have multiple suites of automated regression tests running on at minimum a daily basis. ...
0
If this is an update for an existing product then presumably you already have some tests for it and likely those tests are automated or can be started in a batch mode. Why would you not run all of them and then see which ones fail?
I think that's probably the first step once an update comes out of development. Then I'd take the list of failed tests and ...
1
It really depends on what the small update is. It might be a small change but it affects a lot of parts of the system e.g. Updating something in the db.
The testing shouldn't be tied to whether it is a small update or a big one, however defined. It should be tied to how much you think is the effect of the given update. A small but critical update may ...
Top 50 recent answers are included
