My guest post @PractiTest QA Learning center
As testers, we all worked with Excel at some point in our career. If you are using
excel now this article is for you 🙂 Excel is used as test management, documentation
and reporting tool by many test teams. At early stages, most teams rely on excel
spreadsheets for planning and documenting tests, as well as reporting test
results. As teams grow, sharing information using excel sheets becomes problematic.
What used to be easy and intuitive, becomes very challenging. Encountering
difficult work scenarios like the below, becomes a day-to-day reality:
- The simple task of figuring out which excel has the test cases you need to run, takes longer and longer.
- Gathering the status of the testing tasks and your project can only be done by going to each desk one by one and asking them.
- A tester mistakenly spent 6 hours running wrong tests in the wrong environment because of an incorrect excel sheet which was not the updated copy.
- Tester’s routinely lose their work or test results because of saving/ overwriting or losing their excel sheets.
- Most test activities are not being documented or accounted for because writing tests is considered a luxury.
If one or more of these scenarios sound familiar to you, you are being held back in
your testing efforts by excel!
In my latest guest post for PractiTest, I have written about how excel can be a roadblock instead of a useful tool for your testing. To read the complete article, click here—->
In here I talk about issues related with use of excel in relation to
- Visibility within the test team
- Configuration Management of test items
- Test Planning and Execution
- Test Status and Reporting
Please give it a read and share your thoughts!