Running tests
Qampanion is based on comparing screenshots of the expected and actual application states. Before executing any actions, each step verifies that the current application state matches the expected one. If the states are different, the step is marked as failed.
The application supports three launch modes:
- running a test case
- running a set of test cases
- running a single step (Debug mode)
Run a test case
A single test case is executed by clicking the Launch button (icon).
A full run:
- removes the previously installed version of the application
- reinstalls it
- launches all steps of the test case
Step statuses
During execution, each step shows its current state and receives a terminal status after completion (Passed / Failed / Skipped).
If the actual screen state does not match the expected one:
- the step is marked as Failed
- the test case is considered failed
- the dropdown menu provides access to:
- expected screenshot
- actual screenshot
- diff between them
Run a test plan
To validate a feature or story that includes multiple test cases, it is recommended to use a Test plan. For running a test plan, open it and start it the same way as a single test case.
Status display
During execution:
- test case statuses are shown on the test plan page
- in the overall test case list
- on the page of a single test case
- in the logs panel with details for each test case
You can open any test case from the list and observe its step execution in real time.
Results
After execution completes:
- terminal statuses for each test case are shown in the test plan and in the test cases list
- error details are available when opening the failed test case
Debug a step
This mode is intended for development, adjustments, and quick logic verification (Debug Mode).
To run a single step:
- Open the test case.
- Choose a step.
- Click the Debug button (icon).
- Wait until the step launch completes.
⚠️ Debug mode:
- does not reinstall the application
- does not reset it to the initial state
- does not start the simulator/emulator
Debug mode assumes that the device and the application are already in the required state. Step results in Debug mode follow the same validation rules as a full test case run. On success or failure, the step status and screenshot differences are displayed the same way as in a regular launch.
Logs
During test case, test plan, or debug runs, the following events are logged:
- each executed step
- each action inside a step
These logs are displayed in a separate panel at the bottom of the screen.
Logs:
- update in real time
- reflect the actual execution order
- preserve the history of the current run