Test data management is a key factor in efficient testing. You need to specify all the data a test requires to be executed effectively and you will need to ensure that all that data will be available during each execution of the test. If you can’t provide adequate test data, your testers will have to find or create their own test data each time they execute a test, making the result of the test highly dependent on their interpretation. Automated tests, however, won’t run at all if you don’t provide the required test data.
Looking at automated tests you have the chance to integrate your test data management into your test automation framework. But what would an effective process of such an integration look like?
30 days of testing are over and I certainly learned a lot by mastering some of the tasks, switching some of them around and failing at others.
My first point of advice to everyone pondering whether to take the challenge or not: Take it! You will have to fight, you will have to step outside of your comfort zone (not only on day 14) and you will most certainly invest more time than the minimum needed. At least for some tasks. But those are the tasks that will teach you the most.
So you want to start with UI test automation for your product but a complete overhaul of the product’s UI is already planned? Tough luck – there’s nothing for you to gain until the overhaul is completed. Or is there?
Yesterday I saw an interesting tweet following @ministryoftest stating that someone had just completed their 30 days of testing challenge.
As being challenged is the best driver for improvement I read about the challenge and decided to accept.