Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Can you list some advantages of automation testing?
There are several benefits of employing automation testing. Some of the most notable ones are: Allows parallel execution. Makes unattended execution possible. Reduces human error. Saves money and time. Supports testing a big test matrix.
There are several benefits of employing automation testing. Some of the most notable ones are:
- Allows parallel execution.
- Makes unattended execution possible.
- Reduces human error.
- Saves money and time.
- Supports testing a big test matrix.
See lessWhat do you need to prepare the acceptance plan?
We need the following for making the acceptance plan: Requirements Document - Specifies the needs of the customer. Customer Input - Gained through discussion, emails, et cetera. Project Plan - Finalizes the acceptance test.
We need the following for making the acceptance plan:
- Requirements Document – Specifies the needs of the customer.
- Customer Input – Gained through discussion, emails, et cetera.
- Project Plan – Finalizes the acceptance test.
See lessPlease explain the various categories of defects?
Following are the three primary categories of software defects: Wrong - Results when there is a deviation from the given specifications. This type of defect occurs when requirements are implemented incorrectly. Missing - This happens when customer specifications are missed, i.e., they are notRead more
Following are the three primary categories of software defects:
- Wrong – Results when there is a deviation from the given specifications. This type of defect occurs when requirements are implemented incorrectly.
- Missing – This happens when customer specifications are missed, i.e., they are not implemented. This might also happen when customer requirements are not clear but implemented.
- Extra – Caused by requirements that are implemented but are not provided by the customer(s). Although this type of defect is variances from the customer specifications, they might be desired by the end-users.
See lessState the difference between validation and verification in software testing.
While validation is a dynamic analysis technique, verification is a static analysis technique. We execute the code invalidation, whereas no code execution takes place in verification. Inspection, reviews, and walkthroughs are examples of verification, while functional and non-functional testing comeRead more
While validation is a dynamic analysis technique, verification is a static analysis technique. We execute the code invalidation, whereas no code execution takes place in verification.
Inspection, reviews, and walkthroughs are examples of verification, while functional and non-functional testing comes under validation.
See lessPlease compare functional and non-functional forms of testing?
Following are the important differences between functional testing and non-functional testing: Based On - While functional testing is based on customer requirements, non-functional testing is based on customer expectations. Defines - Functional testing describes what aspect of a software product. NoRead more
Following are the important differences between functional testing and non-functional testing:
- Based On – While functional testing is based on customer requirements, non-functional testing is based on customer expectations.
- Defines – Functional testing describes what aspect of a software product. Non-functional testing, on the other hand, defines how the aspect of a software application.
- Order of Performing – Non-functional testing follows functional testing.
See lessCould you define a test case?
A test case can be defined as that particular set of conditions and/or variables under which a software tester determines whether the system/software under testing works correctly and satisfies the specified requirements or not.
A test case can be defined as that particular set of conditions and/or variables under which a software tester determines whether the system/software under testing works correctly and satisfies the specified requirements or not.
See lessWhat do you mean by Bug Life Cycle?
Bug Life Cycle explains the various phases of a software bug or defect's entire lifetime. It starts with detecting a bug and sums up when the same is closed, and it is ensured that it will not reproduce. Its various phases are: Detection/new Assigned Active Rejected Deferred Tested Reopened (goes toRead more
Bug Life Cycle explains the various phases of a software bug or defect’s entire lifetime. It starts with detecting a bug and sums up when the same is closed, and it is ensured that it will not reproduce. Its various phases are:
The Bug Life Cycle, also known as Defect Life Cycle, varies according to a range of factors, most notably organization policy and the SDLC methodology used, such as agile or RAD. Other Defect Life Cycle shaping factors include project timelines and team structure.
See lessCan you name the various levels of software testing?
Usually, software testing starts with unit testing and sums up with acceptance testing. The hierarchy followed is; unit testing -> integration testing -> system testing -> acceptance testing.
Usually, software testing starts with unit testing and sums up with acceptance testing. The hierarchy followed is; unit testing -> integration testing -> system testing -> acceptance testing.
See lessPlease explain the various strategies of software testing.
There are three types of software testing: Black Box Testing - Based completely on testing requirements and specifications. Demands no knowledge about: Internal paths, Code structures, or Software implementation. White Box Testing - Necessitates advanced programming skills. This testing strategy buiRead more
There are three types of software testing:
- Black Box Testing – Based completely on testing requirements and specifications. Demands no knowledge about:
- Internal paths,
- Code structures, or
- Software implementation.
- White Box Testing – Necessitates advanced programming skills. This testing strategy builds upon the internal paths, code structures, and software implementation.
- Grey Box Testing – This software testing strategy falls between the domains of black box and white box testing strategies. Here, the internal details of the software under testing are little-known.
See lessWhat is the Software Testing Life Cycle?
The Software Testing Life Cycle refers to the systematic process of software testing. STLC defines the entire thing, from the start to the end. It is composed of several sub-processes called phases, which are: Requirements Gathering Requirements Analysis Test Planning Test Case Development EnvironmeRead more
The Software Testing Life Cycle refers to the systematic process of software testing. STLC defines the entire thing, from the start to the end. It is composed of several sub-processes called phases, which are:
- Requirements Gathering
- Requirements Analysis
- Test Planning
- Test Case Development
- Environment Setup
- Test Execution
- Test Cycle Closure
See less