Question-51. What is the most effective way to map automation testing success?

Answer- The success of Automation testing can be measured using the following criteria:

  • Savings on labor & other costs.
  • Defect Detection Ratio.
  • Automating the execution process and reducing the release time.

Question-52. What are the different types of severity you can assign to a bug?

Answer- Though it varies depending on the size and structure of the software development teams, typically, a bug can be assigned the following types of severities, going from low to high:

Low

  • User Interface bugs.
  • Accessibility issues.

Medium

  • Leaky abstractions.
  • Software hangs.
  • Users unable to perform a specific action.
  • Boundary conditions.

High

  • Crashing under high load.
  • Business logic and/or calculation errors.
  • Any user action that causes the software to crash.
  • Exposing sensitive user data.
  • Security problems.
  • Loss of data.

Question-53. Which test cases are written first: white boxes or black boxes?

Answer- Test cases for the black box testing are usually written first, followed by test cases for the white box testing. An outline of the design or project plan and the requirements document is required to write black-box test cases. Documents such as these are readily available at the beginning of the project. The initial phase of a project isn’t the right time to start white box testing because it requires more architecture clarification that isn’t available yet. Therefore, white-box test cases are typically written after black-box test cases have been developed.

Question-54. What is alpha testing?

Answer- Before you ship the software to the customers, the internal testing team performs alpha testing. Alpha testing is part of the user acceptance testing. Its goal is to identify bugs before the customers start using the software.

Question-55. What is beta testing?

Answer- Once you ship the software to the customers after alpha testing, the software’s actual users perform the beta testing in a real production environment. It is one of the final components of user acceptance testing. Beta testing is helpful to get feedback from real people using your software in real environments.

Question-56. What is meant by browser automation?

Answer- It’s a process of automatically testing a web application’s functionality in a browser, where a program launches the browser, navigates to the application, and interacts with the user interface by clicking buttons or links, just like an average user would.

The only difference is that the browser automation can test this very quickly and often, whereas the same test would take a human tester a long time. It’s part of automated testing. Some essential tools for browser testing include Selenium, protractor.js, and cypress.

Question-57. What do you mean by Test Matrix and Traceability Matrix?

Answer- Test Matrix: It is referred to as a testing tool that is used to capture actual quality, effort, resources, plan, and time required to capture all the phases of software testing. It only covers the testing phase of the life cycle.

Requirement Traceability Matrix (RTM): It is referred to as a document, usually present in the form table, that is used to trace and demonstrate the relationship between the requirements and other artifacts of the project right from start to end. In simple words, it maps between test cases and customer requirements.

Question-58. What is the V model in software testing?

Answer- V-models, also known as validation or verification models, are SDLC models where the process occurs sequentially in a V-shape. This method consists of associating a testing phase with each corresponding development stage. As each development activity is accompanied by a testing activity, the next test phase occurs only after the previous phase has been completed.

  • Validation: It is defined as a process that involves dynamic testing of software products by executing the code. This process validates whether we are building the right software that meets that customer’s requirement or not. It involves various activities like system testing, integration testing, user acceptance testing, and unit testing.
  • Verification: The technique involves static analysis (review) without running the code. It is defined as a process that involves analyzing the documents. This process verifies whether the software conforms to specifications or not.  Its ultimate goal is to ensure the quality of software products, design, architecture, etc.

Question-59. State difference between verification and validation in software testing.

Answer- Validation: It is defined as a process that involves dynamic testing of software products by running it. This process validates whether we are building the right software that meets that customer requirement or not. It involves various activities like system testing, integration testing, user acceptance testing, and unit testing.

Verification: It is defined as a process that involves analyzing the documents. This process verifies whether the software conforms to specifications or not.  Its ultimate goal is to ensure the quality of software products, design, architecture, etc.

Verification Vs Validation:

Verification Validation
It checks whether the software meets the specification or not. It checks whether the specification captures the customer’s needs or not.
It is a type of static testing. It is a type of dynamic testing.
There is no requirement of executing the code. There is a requirement for executing the code.
This process is performed by the QA team to make sure that the software is built as per the specifications in the SRS document. This process is performed with the involvement of the testing team.
Reviews, walkthroughs, inspections, and desk-checking are some methods that can be used in verification. Black box testing, white box testing, and non-functional testing are some methods that can be used during validation.
It identifies the bugs or errors early in the development process. It can identify the bugs or errors that the verification process cannot catch.
It is performed before the validation process. It is performed after the verification process.

Question-60. What is static software testing?

Answer- Static testing is a technique in which you test the software without actually executing it. It involves doing code walkthroughs, code reviews, peer-reviews, or using sophisticated tools such as eslint, StyleCop to perform static analysis of the source code. Static testing is typically performed during software development.

Pages: 1 2 3 4 5 6 7