From our clients’ feedback, we had the following as the the most important User Interface testing requirements:
- Compare two single sequences performed by a given user and ensure consistency in the results
- Test the full chain of Summit FT technical components down to the database
- Record the test sequences easily and quickly and avoid a long development process
- Launch use cases previously recorded as a sequence in parallel to simulate a real production workload
- Monitor performances and compare them from one version to another
- Easy to implement and to use
- Compliant with a “continuous integration” already in place within the bank
- Scenario video recording
The module has been designed in .NET/C# to be close to the Summit FT technology and uses http/https.
- User sequence recording: creating the test cases.
- Test cases library: ordering, filtering & maintenance
- Replay a single test case: replay, statistics and intelligent comparison features
- Performance testing: replay in parallel X test cases Y times with several options to simulate real use cases.
- Matrices of concurrent virtual users and test cases
- Option to include “thinking time” meaning including all the time corresponding to no action from the users on the desktop
- Include or not latencies (laps) between the parallel connections
- Assign a desktop, program mode and scenario to a user
- Granular comparison results and performances statistics
Composite scenario with new path and user settings
It allows building complex scenario based on a combination of single scenarios. It typically permits to launch a trade entry with a Front-Office user and combines it with the related deal validation done with a Back-Office user. With a composite scenario we test the features themselves, but also the SAL and related access rights in one run. Note that the composite scenarios are compliant with the load tests
Dynamic Field Editor:
It allows to map a given field in the source environment with the same field in the target environment. For example if we have a scenario with actions on tradeId XXX on the source, we can now map XXX on YYY and play the scenario on YYY in the target environment
Allows to record a scenario with variable XX and then edit and rename the variable with another value. For example, record a trade with CUSTOMER1 and replay a scenario with CUSTOMER2, CUSTOMER3 etc
“QualityFactory Report Launcher” offers to run a Summit FT report, displays the outputs and uses pivot tables if needed. It also shows the structure of the report outputs that can be fully customized (choose the column to be tested, tolerance ranges for numeric fields and the record keys).
No issues anymore with a full report in diff just because a new column has been added in higher releases !
- Report editor allowing to download a list of Summit reports
- Report configuration to define properties to be checked during the comparison
- Tolerance check definitions
- Report launcher
Compliance with continuous integration tools
QualityFactory can be launched in batch and is fully compliant with continuous integration tools