- Not heavy on bugs - could actually focus on testing instead of bug reporting
- Completely unknown domain: proper English language writing style "eprime" I had never heard of.
- WebUI with beautiful IDs
Session Charter: Explore EPrimer focusing on two kinds of documentation as output: test automation you can run (using e.g Robot Framework) and a mindmap. Time: 1 hour plus learning time for test automation tool if you have no experience and no expert available answering your questions in the moment.
- Quickly acquiring domain knowledge: no one knew what eprime is, and we had our choice of reading about it.
- Acquiring functional knowledge: using the application and figuring out what it does.
- Creating simple scripts with multiple inputs and outputs: using same test as template for data-driven helps repeat similar cases in groups.
- Identifying css selectors: if you wanted test automation scripts, you needed to figure out what to click and verify and how to refer to those from the scripts.
- Controlling scope of tests: see it yourself, see it blink with automation, repeat all, repeat only the latest.
- Creating an invisible or visible model: Seeing SFDPOT (Structure, Function, Data, Platform, Operations, Time) to understand coverage in selected or multiple dimensions
- Cleaning up test automation: Improving naming and structuring to make more sense than what was created in the moment.
- Using the application: Making space for chances to see problems beyond the immediate test
- Identifying problems: Recognizing problems with the application.
- Documenting problems: Writing down problems in either test automation or otherwise.
- Working to systematic coverage: Pick a dimension, and systematically cover it learning more on it.
- Reading the code: We had the code and we could read it. That could add to our understanding.
After 2 hours of #ExploratoryTesting documented with automation, it took another 2 hours to clean it up. 52 tests total, 38 passed, 14 failed. Quite many bugs as per specification. Time on app has been maybe 30 minutes of this 4 hours.— Maaret Pyhäjärvi (@maaretp) August 1, 2020