T3 Softwares

The fundamental objective of manual testing requires application validation for conformation to its specifications so that applications behave as expected by end user.

The project team understands the requirements from various sources of information provided by client, there are discussions and meetings with during the project execution that are converted into change requests. The requirements are documented in T3 tools against which test cases are written to ensure the requirement coverage is fully maintained. The requirements are properly tracked with test case design methods. The quality methods are used though various coverage of end-to-end business scenarios supported by test cases for each business scenarios. The T3 manpower is well experienced to identifying intricate business scenarios that help in proactive and quick locating of bugs.

The team tests all the business features through regression , sanity test, browser compatibility usability and component testing procedures.

A.      Regression Testing:

Our experience with various software development stages show that regression testing have unique ways to representation of testing cycles. The testing cycles are repetitive. Regression testing provide adequate ways to cover the quality of application delivery.

We follow a rigorous testing regression procedure to test the following in a complete cycle through effort using Use Case Estimation, FPA, Anology Effort estimation techniques. The coverage areas during regression cycle cover any or all the processes

•           Various Configuration features
•           Test beds
•           Functionalities – It is the basic coverage at the minimum in regression.
•           Security
•           Third party API’s
•           Databases
•           Internationalization and localisations, if feature requests are covered as functionalities.
•           Integration testing with current builds/upgrades and previous builds/backward compatibilities.

 B.      Component Testing:

Unit testing during construction phase of software development life cycle is covered in component testing. We use the RAD tools and open source technologies to cover the component testing. In addition, programming tools are developed in various computing languages such as Perl, Phython, C, C++, Java, .Net that suite the application development. Black Box testing is also utilized to cover the component functionalities independently.

C.      Usability Test:

We support User Acceptance Test(UAT) that are actually tested by your end users. We share our testing guidelines with good understanding and information sharing through formal communication to ensure user friendliness of the application. We provide the business and technology support staff to perform UAT.

D.      Compatibility Test:

Our team makes a study of the system architecture of the application, the work flow rules and various component integration that include hardware, operating system, software, networking, internet, third party interfaces and different web browser requirements. The study gives a comprehensive view about plan to perform compatibility tests that can be a single or permutations of compatibilities mentioned below:

•          Browser compatibilities over the same functionalities or independent browser based functional requirements.
•          Compatibilities in functionalities between different operating systems and databases.
•          Compatibilities with third party interfaces between different operating systems and databases.