QASentinel helps you write better, more effective automated tests, and use these tests to produce world-class test reports and development documentation.
QASentinel helps you write cleaner and more maintainable automated and regression tests faster. QASentinel also uses the test results to produce illustrated, narrative reports that document and describe what your application does and how it works. QASentinel tells you not only what tests have been executed, but more importantly, what requirements have been tested.
QASentinel is a fundamental tool in modern software development. QASentinel helps on how to set up an effective Continuous Integration that will reduce integration issues, improve code quality, and improve communication and collaboration between team members.
In software engineering, this is the first step in a QA process, creating and writing a set of Test Cases for testing a piece of software. This Test Case specification typically is performed by a QA Analyst, who should specify one Test Case for every flow that could be performed in the application under testing.
During every Test Cycle, the whole set of Test Suites are executed automatically or by hand, following a prioritized list of Test Cases. Basically, with a given input value, the tester needs to determine if system responses matches with the expected results, predicted before the test is run.
Once a particular Test Case detects a bug, it should be reported in a bug-tracking tool, from beginning to closure, and implementing new versions of the software that fix the defects.Analysis and prioritization according their severity and/or priority should be done.
In this section, the QA Team provides a report with the results of every Test Case executed during the last Test Cycle, green or red ball for every one of them, grouping the detected bugs by criticality and/or severity. Blockers and critical bugs have to be fixed before deployment into production. Rest of them are communicate to the Product Owner, and he should determine to proceed with or abandon the Release Candidate before deployment.
No matter how good a QA team is, there is always opportunity to improve. After every Test Cycle, usually the last thing done, team should dedicated a period to reflect on how are they doing and to find ways to improve.