Group items tagged

Traditional Testing and Agile Testing are two important testing techniques used to test the credibility, reliability, quality, functionality, and other important components of the software. Traditional Testing: Offers full coverage of the software. Allows one to detect the maximum number of defects. Agile Testing: Involves rigorous planning, analysis, and testing. Offers effective and efficient risk management.

As we all know, test case and test plan are two significant components of software testing, as they define and manage the procedure of testing. Moreover, these documents, offer the testing team vital information regarding software testing and elaborate on various other important components related to the project.

Test Plan is an important document, prepared before the beginning of software testing activities. It defines important aspects of the software that are tested or evaluated, during the process. An effective test plan helps the team in estimating the size of the project, the time required for the test, among other things.

Though considered to be synonymous, Ad-hoc Testing & Exploratory Testing are two types of testing techniques, with different qualities, specifications, and functionalities. Testers perform Ad-hoc and Exploratory test with a varying level of planning, to assess different components of the software. Hence, to help you differentiate between these two types of testing techniques, here is a detailed comparison of the two.

Ad-hoc testing is an informal test that is performed randomly, without any plans or strategies, with the intention to break the software system. Compared to traditional testing, this is a beneficial test that helps the team to find the majority of defects, as it uses various innovative methods to test the software.

Delta testing is a type of software testing that is used by testers to evaluate a product by partially releasing it. It does not require maintaining the record of expected results and is implemented by elaborating a test plan, which is further led to the designing of various test suites.

Test Execution, a process of executing prepared test cases & test plans, is one of the stages of Software Testing Life Cycle, which is used to get expected results as well as to evaluate & validate the efforts of the team members associated with the development of the software.

Experience is that precious tool of the tester, which is always required in performing all types of testing. To provide reliable and effective results one must utilize gained experience in creating strategy and planning documentation.

I have written below reply for a question asked about "Framework in QTP" in our QTP knol The below link may help to get some idea about Keyword driven testing. http://mercuryquicktestprofessional.blogspot.com/2006/11/whats-your-automation-framework.html In case of keyword driven testing, we need to do proper planning and initial huge effort. Anyway it will give benefit of easy maintenance and easily adding more test cases/scenarios.

Software Development Life Cycle (SDLC) SDLC involves different phases such as Initial/Planning phase, Requirement analysis phase, Design phase, Coding phase, Testing phase, Delivery and Maintenance phase.

Termed as the first stage of Software Testing Life Cycle, Software Verification helps ensure the precision of the end product by conducting a thorough software review, inspection, & evaluating documents, plans, requirements & specifications, to determine whether the software meets the specified requirements or not.