Security

121T relies on black-box testing and runs on a client’s premises, therefore no part of the application under test is exposed to external people, except those managing 121T.

Agility

121T has a very small organizational impact on existing teams.

121T supports business agility because quality risks can be iteratively addressed as market and product conditions change.

It supports incremental development of new automated test cases.

121T relies on continuous updating of the test automation software to cope with changes in the system under test.

Which bugs

121T achieves full automation of regression tests with test cases that are based on  real platforms used by real users. As your team works on new features, tests cases covering them can be developed in parallel, leading to test cases being made available just when the corresponding feature can be tested.

Minimal workflow impact

Current workflow is preserved: 121T can fit existing work processes and roles. 121T relies a client’s representative that participates to sprint planning and review meetings. 121T relies on a client’s tester who launches tests and reads reports to understand if there are bugs, to triage them, to file bug reports, to periodically examine requirements coverage.

Not coupled

121T is not coupled to the particular technology used for building the system under test, as long as it is a web or Android application.

TDD practices

121T is compatible witch Test Driven Development practices: as soon as a feature is sufficiently well understood the 121T team models it and writes test cases that can be executed later on.

No new test frameworks

No need to learn new test frameworks. Test cases written in Gherkin are easy to understand and modify. CUTE FrontEnd is easy to use and simple.

Easy to read test reports

121T provides test reports with overall structural coverage, with detailed execution history, with screenshots of the system under test for each step, with requirements coverage via the well-know JIRA system. Informative bug reports can be easily generated by cutting and pasting information from the detailed steps being reported.

Scheduled tests

Test runs can be scheduled during the night or at lunch time, saving time to testers to perform other kinds of testing, such as exploratory testing.

Multiple kinds of conditions

Test cases can cover multiple kinds of conditions, such as interaction and navigation, such as data and text being presented on screens and such as layout of the screens: visibility of elements, alignments and overlaps.