I finished looking over all the tests, it was pretty tedious but got easier towards the end since the testcases seemed to be more up to date. It wasnt really hard and I usually knew when I should and shouldn't invalidate something, but there was one testcase though that I wasn't sure about because it said to tap on an input field but it was a button. I didn't invalidate it because I was unsure and it didn't seem too important but I was thinking it made it sound like the button was a text field.
Most of these tests had the same error though because there was one wrong button but I did invalidate one today that had quite a few wrong buttons and pages listed in the instructions.
To really do a bang up job on this kind of project (and to make it feel less "tedious") you need to:
ReplyDelete1. Take ownership of it. If you feel that this test suite you are helping to maintain is your in some why, and feel the pride of authorship that goes with that, it will be easier to be engaged, since you will want the test suite to be as good as it can be for the benefit of the project.
2. Stay on top of it. The more you keep the test suite up to date through the rapidly changing process of software development, the easier it will be to keep it up to date and the less overwhelming the task will feel.
The app will begin to stabilize as it approaches a release version, so the rate of change will slow and you can fine tune the test suite to make it really solid. The cool thing is you are also getting a hands-on view of the software development process, so pay attention to that and learn from it.