Jolene (2008) watch online
Sinners and Saints (2010) online
Into the Abyss (2011) online

A typical Quality Engineering workflow is blended in software development lifecycle. The figure below shows different testing phases in line with development process.



 Test Plan

Test plan defines the high level strategy for the various testing that will be carried on the application. The following elements will be detailed in the test plan document. As part of our Lean philosophy, Vercelon ensures only the most relevant information based on the required testing is defined and the document is simple and clear.


Environment in which the testing will be carried out. In a multi environment or multi client support requirement, this identifies the high level strategy for dividing the testing to each environment


Testing standards

Various standards to be followed in the testing lifecycle, like size of the test cases, classification of defects (cosmetic, critical etc), information that needs to be documented (for test case, defect, reports etc), frequency of reporting, test environment standards etc


Test repository

Repository in which the test cases are stored. In a complex test scenarios, this should be a standard versioning tool like Quality center™, JIRA etc. Various authorizations to roles in repository will be defined.


Defect Tracking

Defects found in various testing phases are logged in to the centralized defect tracker. This tracker classifies the defects based on criticality and ensures proper disposition of defects through a well defined workflow


Entry Exit criteria

Definition of Entry exit criteria ensures standard mechanism in which the sign-offs are given by testing team in each phase of testing.



Test case Preparation

Development of test cases is the critical phase in the test life cycle. Test cases should cover all functional requirements, non-functional requirements, Performance considerations, various clients that need to be verified etc. Each test case will detail all required input data, configurations and expected results. Application Interface requirements for white box testing also will be outlined at high level.
The level of detail in each test case should be properly defined and standardized.

Automation scripts

Test Automation enables rapid execution test cases and reduces running cost significantly. Automation is best suited in scenarios where test cases need to be executed for multiple times for various client versions, frequent release cycles, regular test requirements etc.
Automation can be implemented based on code or UI. In code based automation (similar to white box testing) automation scripts are developed for executing the application functions directly through interfaces. In UI based automation, the testing is carried out in a similar way the functionality is used by an end user.

Test Data Preparation

In complex Test scenarios, lot of input data might be required to test the complete system. These include various data files (images, documents, pdfs, xml etc), different levels of user access, records in database etc.
Defining these data and preparing them in advance before testing ensures consistent test results across multiple cycles.

Test Environment preparation

Ensuring proper test environment existence is very critical for the success of testing. The actual production environment should be replicated as much as possible for testing.
This phase of testing also prepares various test clients (client PCs for each Operating system to be validated on, Smartphone, Tablets etc).

System Testing

White Box testing
White box testing validates the system functionality at code level. Test scripts are developed to feed and receive data from application interfaces and each functionality of the application is validated for all possible test inputs. This form of testing ensures wide coverage of test scenarios for the functionality and consistent test results in different test cycles. A further UI testing after integration necessary to ensure the system performs according to the specification.
Black Box testing
Black box testing is run on the actual user interface of the application and covers the entire functionality as an end user. In automated systems, various tools are used to identify the UI component and the testing is carried out in the same way as the functionality is used. Defect identified in testing are logged in the defect tracking tool and follow the defined workflow until resolution.

Performance & Scalability Testing

Performance and scalability testing is performed to validate if the system performs in line with the required performance standards. On new application installation this will be based on the performance and scalability requirements as defined in the software requirements. In existing systems, current performance metrics will be benchmarked and the changes in the system will be validated against these benchmarks.

Regression Testing

Every change in the system need to be validated to ensure the change is not breaking the existing functions of the application. Impact analysis in the design phase identifies the modules or components affected by the change. Identification of regression test cases will be based on this impact analysis. This shortlisting of test cases reduces the efforts required for testing changes in the system and also ensures focus on the impact area

Joomla Template - by