App Test Software

AppTest Software can work with both incremental integration testing and consolidated integration testing. In the case of incremental integration test, new builds are frequently provided with more components and fixes of prior integration defects. In the case of consolidated integration test, the full build is provided. The AppTest Software team decides between incremental and consolidated approach based on the development schedule. AppTest Software test engineers focus on rapid turn around during integration testing.

AppTest Software analyzes the application design documents. Based on this analysis, the AppTest Software team creates the integration test cases with respect to all applicable interactions between any pair of components. Test cases and test data are created covering each method call from one component to another and covering each parameter in each method. The integration test cases are internally reviewed and a traceability is created..

It is common to use a duplicate of the stable development environment during integration testing. However, if planned, the App Test Software team prepares a separate integration test environment in consultation with the development team.

The AppTest Software team executes integration test cases in the order of priority (highest priority first) given in the traceability. Any blocked test cases are immediately discussed with the development team to rule out incompleteness in the build or configuration problems in the integration test environment.

Immediately upon discovering defects, they are isolated with respect to their scope (e.g. problem in the interface call or problem with a method of a component) and immediately shared with the development team. Usually, a formal defect tracking system is not used during integration testing because of a relatively large number of defects and need for quick turn around time. However, the AppTest Software team maintains the list of defects and executed test cases within the traceability and the daily progress status is based on the updated traceability.

The Graphical User Interface (GUI) of the application is important because it is the only means for most end-users to interact with the application. We check each aspect of the GUI against AppTest Software's comprehensive checklist including but not limited to the following:

• Navigation (Identification of navigation scheme and home screen, clarity and consistency of navigation buttons and labels, navigation using the minimum number of user operations and navigation across windows and frames)
• Content (Relevance, completeness, organization and balance, screen layouts, screen and message box titles, font styles/ sizes/ spacing/ colors, working buttons, correct spelling and grammar, lists/ dropdowns with sorted data and buttons with correct tooltips).
• User friendliness (Intuitive organization of user menus, toolbars, buttons and double click/ select/ cut-paste/ drag-drop operations, usage of standard/ self-explanatory words and images, default or example user data, handling blank/ zero/ null user inputs correctly and easily understandable and consistent error or warning messages).
• Performance (Refresh/ download speed and partial versus full screen loads).
• Accessibility (Keyboard only operation, minimum contrast ratio on every screen, alternate content for every image, audio, animation or video, time sufficiency for user operations and context sensitive help).