First Exploratory Testing with eprimer

You can only have the very first experience with a new application once.

Each of these assignments uses the same system under test and suggest a very different constraint.

We encourage you to pick one to start from, and end up using an hour on each of the constraints.

We provide an example of how we completed the assignment as a reference of what it could look like.

Test target: eprimer at https://eviltester.github.io/TestingApp/apps/eprimer/eprimer.html

Assignment:

Constraint: Report results as test notes, and test as much as you can within one hour.

Expected background: You want to give a go at testing a fairly simple application which we expect not to have many problems.

Dynamic to pay attention to: where does time go? How far do you get on coverage? What do you think is coverage of your tests and you can you tell if that is good or not?

Theory you need for completing assignment 2

1. Install Robot Framework and know how to create and run tests there

Assignment 2: Exploratory testing of eprime with skeleton automation as documentation

Constraint: Report results as placeholder, skeleton automation where only implementation is to log into report. See how far you get with one hour of work.

Expected background: You get robot framework run on your computer so that you can run basic test cases that next do nothing

Dynamic to pay attention to: where does time go? Does this free time for exploring, particularly compared to the third option? How good are your test structures and what could make them better?

Theory you need for completing assignment 3

1. Install Robot Framework with Browser Library and know how to create and run tests there

2. Inspecting web pages for simple CSS

Assignment 3: Exploratory testing of eprime using test automation as documentation

Constraint: Report results as executable test automation you can create within one hour.

Expected background: You think you can test simple applications and want to challenge yourself in structuring lessons as test automation while you test.

Dynamic to pay attention to: where does time go? How much testing do you actually get done? Is automation enabling you to test further or is it slightly slowing you down? How well do you think you tested the application?

Turning this to a video course