program. Reusability is another problem; you may not be able to transfer a testing program fromone title (or platform) to another. And of course, there is always the "human factor" of testing thatcan never truly be replaced.Other successful alternatives or variation: Nothing is infallible. Realistically, a moderate splitof human and automated testing can rule out a wider range of possible bugs, rather than relyingsolely on one or the other. Giving the testere limited access to any automated tools can often helpspeed up the test cycleSQA India could be a useful resource for Software Quality assurance. We follow SoftwareQuality Assurance (SQA) methods that adhere to the quality assurance at every phase of SDLC(Software Development Life Cycle). A quality control checklist is developed for all phases of SDLC.We aim to provide quality and consistent results through automated process that have been testedover time. Purpose of the SQA Plan is to establish a uniform Web / Software DevelopmentProcess, which is applicable throughout the software development life cycle
Welcome to the Software Quality Assurance (QA) and Testing Information Center. It offersarticles, best practices, methodologies, FAQ, guides, books, directories, and tools that are relatedsoftware QA and testing. Popular materials include job interview FAQ, test plan samples, WinRunner FAQ, and more
Our Software Testing Procedure
A good test effort is driven by questions such as:
How could this software break?
In what possible situations could this software fail to work predictably?Software testing challenges the assumptions, risks, and uncertainty inherent in the work of other disciplines, and addresses those concerns using concrete demonstration and impartial evaluation.Testing focuses primarily on evaluating or assessing product quality, which is realizedthrough the following core practices:
Find and document defects in software quality.
Advise on the perceived software quality.
Validate and prove the assumptions made in design and requirement specifications throughconcrete demonstration.
Validate that the software product works as designed.
Validate that the requirements are implemented appropriately
Also called ‘Structural Testing / Glass Box Testing’ is used for testing the code keeping the system specsin mind. Inner working is considered and thus Developers Test..
Number of mutants of the same program created with minor changes and none of their resultshould coincide with that of the result of the original program given same test case.
Basic Path Testing
Testing is done based on Flow graph notation, uses Cyclometric complexity & Graph matrices.
Control Structure Testing
The Flow of control execution path is considered for testing. It does also checks :-Conditional Testing : Branch Testing, Domain Testing.Data Flow Testing.Loop testing :Simple, Nested, Conditional, Unstructured Loops.
Also called ‘Functional Testing’ as it concentrates on testing of the functionality rather than the internal