Mint Tree - IT Solutions
Quality Assurance and Testing
At Mint Tree, we believe that testing is a science and requires a great deal of specialized expertise. We employ modern techniques such as test automation & converge analysis and sophisticated methodologies in test strategy, planning, consulting, automation & execution, to produce key code stability and maturity metrics.
Off shore testing doesn't replace in-house testing. We complement your own development and testing processes, seamlessly filling any gaps in your testing schedules. If you don't have your own testing team (QA team) we can take full responsibility for your testing, integrating directly with your development team.
Testing at Mint Tree can give you following advantages:
Experienced Expertise: The testing team at Mint Tree has expertise & experience in a variety of domains and technologies.
The Cost Advantage: We provide world-class software QA & testing services at typically less than half the cost of maintaining your own Testing & QA setup, the offshore outsourcing advantage.
Standards: Our testing team is constantly trained on latest software Testing & QA techniques. That knowledge and expertise is directly utilized in ensuring the highest quality standards needed for your software product.
We can also:
- Complement your existing Testing / QA staff.
- Provide you a complete outsourced software testing solution.
- Extend your testing capabilities, specifically in localization development efforts.
Our range of Testing services include:
- The testing team at Mint Tree has expertise & experience in variety of domains and technologies. Based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths and conditions.
- Unit Testing is the first level of dynamic testing and is first the responsibility of the developers and then of the testers. Unit testing is performed after the expected test results are met or differences are explainable / acceptable.
- Alternate Testing is where the user reconciles the output of the new system to the output of the current system to verify that the new system performs the operations correctly.
- Usability testing, for 'user-friendliness'. Clearly this is subjective and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.
- Upon completion of unit testing, integration testing, will begin. The purpose is to ensure distinct components of the application still work in accordance to customer requirements. Test sets will be developed with the express purpose of exercising the interfaces between the components.
- Upon completion of integration testing, the Test Team will begin system testing. During system testing, the complete system is configured in a controlled environment to validate its accuracy and completeness in performing the functions as designed. The system test will simulate production which will occur in the "production-like" test environment and test all of the functions of the system that will be required in production.
- Similar to system testing, the 'macro' end of the test scale involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
- Although performance testing is described as a part of system testing, it can be regarded as a distinct level of testing. Performance testing will verify the load, volume and response times as defined by requirements.
- Installation testing is testing full, partial, or upgrades install/uninstall processes. The installation test for a release will be conducted with the objective of demonstrating production readiness. This test is conducted after the application has been migrated to the client's site. It will encompass the inventory of configuration items (performed by the application's System Administration) and evaluation of data readiness, as well as dynamic tests focused on basic system functionality. When necessary, a sanity test will be performed following the installation testing.
- Security Testing is to test how well the system protects against unauthorized internal or external access, willful damage, etc. This type of testing may require sophisticated testing techniques.
- Recovery/Error Testing: Testing how well a system recovers from crashes, hardware failures or other catastrophic problems.
- Acceptance testing will give the client the opportunity to verify the system functionality and usability prior to the system being moved to production. The acceptance test will be the responsibility of the client; however, it will be conducted with full support from the project team. The Test Team will work with the client to develop the acceptance criteria.
- Final Testing: Testing of an application when development is nearing completion. Minor design changes may still be made as a result of such testing. Alpha Testing is typically performed by end-users or others, not by programmers or testers.
- Testing when development and testing are essentially completed and final bugs and problems need to be found before the final release. Beta Testing is typically done by end-users or others, not by programmers or testers.
Talk to us today on how we can partner together to help you with your software development needs.
