Magellan allows tests once written to be executed in either config mode or in UI mode.
The differences between tests running in config mode vs UI mode is explained below
| Config Mode | UI Mode |
| In config mode the tests run more like in a unit-test framework mode working directly with the XML View instance. Tests do not run in a browser | In UI mode the test runs in a browser as a user performing actions against the UI elements present on the screen |
| Pros 1. Very fast Cons 1. Requires understanding of the ViewInstance and how fragments are structured 2. Cannot interact with the UI elements and tests still need to be run in UI mode to attain 100% confidence. | Pros 1. Verifies whether UI is running correctly 2. Allows the same test to be run across different browsers to ensure cross-browser compatibility Cons 1. Executes full page loads against an actual server running against an actual database rendering actual HTML |
| Support Option to run in config mode will appear for all Operating systems | Support – Dependent on Operating System Windows UI – Chrome UI – Edge UI – Firefox UI – Internet Explorer Linux UI – Chrome UI – Firefox Mac UI – Chrome UI – Firefox UI – Safari UI – Edge |
To run a feature
On the context menu of the feature file, choose Run Test(s)
- UI – Chrome
- UI – Edge
- UI – Firefox
- UI – Internet Explorer
- UI – Safari
- Config
Browsers Operating systems: Some browsers will not show up if the operating system doesn’t support them. For example, Safari is only supported by Mac, but in the example above we are showing all.
Scenario is a group of steps. One feature file can contain 1 scenario or multiple scenarios. Users might want to group multiple scenarios in 1 feature that tests specific conditions.
To run a scenario
On the context menu of the desired scenario, point to Run, and then choose Run Test(s)
- UI – Chrome
- UI – Edge
- UI – Firefox
- UI – Internet Explorer
- UI – Safari
- Config
The example below is Windows OS browsers.
0
