|
| |
 |
TESTING(QA) & VALIDATION SERVICES |
| |
| |
Our independent testing services employ modern testing methodologies and tools that allow you to minimize the many risks associated with software bugs, incomplete functionality and inadequate application performance. We also offer independent consulting to determine which tests are needed to ensure that your product meets industry-standard criteria.
• Usability testing
• Performance/Load testing
• Compatibility/Configuration testing
• Documentation testing
• Product / Project Release
We have highly experienced resources who are qualified and capable of delivering a Software Testing and QA service either ON SITE or Off Site depending on the project requirement.
TechMind can perform following Testing Functions for you, Click on the Levels or Methods for more detail
Testing Levels
• Unit Level Testing
• Integration Testing
• Validation Testing
• Release Testing
• System Testing
• User Acceptance Testing
• Alpha Testing
• Beta Testing
TechMind testing teams follow each step very carefully in order to give bug free software to our clients.
Unit Level Testing
• Objective
• To test a software unit for its primary attributes and behavior
• Object under test
• Source code
• Screens
• Reports
• Common/shared functions
• Testing Coverage
• Validation rules
• Navigation requirements
• User interface
• Processing of the unit
• Logical path
•If –then-else
•Case / while
• Test case design methodology
• Black box testing
• White box testing
• Regression Component
• Success Factors
• Code coverage
• Conformance with standards
• Test environment creation
Integration Testing
• Objective
• To test the software for dependencies in a module
• To test the interfaces within modules
• Object under test
• Modules / sub modules
• Functionality of the module
• Shared data
• Common modules
• Design philosophy
• Testing Coverage
• Conformance to the functional specification
• Consistent implementation of standards
• Module specific parameters
• Test case design methodology
• Black box testing
• Regression testing
• Test sequence
• Success Factors
• Consistent system
• Functionality coverage
• Modularity
Validation Testing
• Objective
• To check whether software functions in a manner that reasonably satisfies customer expectations.
• Object under test
• Modules / sub modules
• Functionality across module / environment
• Testing Coverage
• Conformance to the functional specifications
• Conformance to the performance requirements
• Conformance to customer requirements
• Conformance to Review
• Test case design methodology
• Black box testing
• Alpha and Bets testing
• Test sequence
• Success Factors
• Configuration Review
• Conformance with standards
• Conformance with customer requirements
System Testing
• Objective
• To test system behavior in operational environment .
• Object under test
• Modules / sub modules
• Functionality across module / environment
• Shared data / system data
• External interfaces
• Operational environments
• Testing Coverage
• Conformance to the functional specifications
• Consistent implementation of standards
• Module specific parameters
• Test case design methodology
• Black box testing
• Regression testing
• Test sequence
• Success Factors
• Consistent system
• Functionality coverage
Release Testing
• Objective
• To ensure successful ship out of all components of the software.
• Object under test
• Installation / Release notes / Release procedure
• Documentation – user/ system / training
• Feature / function / requirements list
• Source / object / executable
• Interfaced objects / utilities
• Test case design methodology
• Black box testing
• Reviews
• Sample sequence
• Success Factors
• Predictable installation process
• Timely delivery
• Availability of environments
User Acceptance Testing
• Objective
• To test the software to be delivered to certain pre-determined criteria for acceptance
• Test case design methodology
• Stress testing
• Regression testing
• Abnormal testing
• Boundary testing
• Functional requirements testing
• Volume testing
• Performance testing
• User interfaces
• Success Factors
• Conformance to customer requirement
• Consistent system
• Software component fits into the ‘system’
Regression Testing
• Objective
• To re-execute some subset of tests that have already been conducted to ensure the changes have
not propagated unintended side effects.
• Object under test
• Modules / sub modules
• Functionality of the module
• Shared data
• Common modules
• Test case design methodology
• Black box testing
• White box testing
• Regression component
• Success Factors
• Consistent system
Alpha Testing
• Test conducted at developer’s location by customer
• Testing in a controlled environment
• Developer is present during Testing
Beta Testing
• Test conducted at customer’s location by end user
• Developer is not present during testing
• Pre-released test conducted by end user in live condition
• Useful for making final release acceptable by end user
|
|
|
