On This Page

This set of Software Testing and Quality Assurance (STQA) Multiple Choice Questions & Answers (MCQs) focuses on Software Testing Quality Assurance Set 14

Q1 | Boundary value analysis belongs to which testing method?
  • black box testing
  • white box testing
Q2 | It measures the quality of a product It is a specific part of the QA procedure, It is a corrective process, It applies for particular product & Deals with the product.
  • validation
  • verification
  • quality assurance
  • quality control
Q3 | What are the Types of Integration Testing?
  • big bang testing
  • bottom up testing
  • top down testing
  • all the above
Q4 | Product Risk affects The quality or performance of the software.
  • true
  • false
Q5 | A metric used to measure the characteristic of documentation and code called as
  • process metric
  • product metric
  • test metrics
Q6 | Which is non-functional software testing?
  • unit testing
  • block box testing
  • performance testing
  • regression testing
Q7 | The process that deals with the technical and management issues of software development called as?
  • delivery process
  • testing process
  • software process
Q8 | Executing the same test case on a modified build called as
  • regression testing
  • retesting
  • ad hoc testing
  • sanity testing
Q9 | Which is Black-Box Testing method?
  • equivalence partitioning
  • code coverage
  • fault injection
Q10 | Business Risk affects The Organization developing or Procuring the software.
  • true
  • false
Q11 | Stratification is a Technique used to analyze/divide a universe of data into homogeneous groups(stratA..
  • true
  • false
Q12 | Informing to the developer which bug to be fix first is called as
  • severity
  • priority
  • fix ability
  • traceability
Q13 | Software Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements or identity differences between expected and actual results.
  • true
  • false
Q14 | Retesting modules connected to the program or component after a change has been made?
  • full regression testing
  • unit regression
  • regional regression
  • retesting.
Q15 | An Important metric is the number of defects found in internal testing compared to the defects found in customer tests, Status of test activities against the plan, Test coverage achieved so far, comes under
  • process metric
  • product metric
  • test metric
Q16 | Alpha testing will be done at,
  • user\s site
  • developers\ site
Q17 | SPICE Means
  • software process improvement and capability determination
  • software process improvement and compatibility determination.
  • software process invention and compatibility determination.
  • software process improvement and control determination
Q18 | It provides a set of levels and an assessment model, and presents a set of recommended practices that allow organizations to improve their testing processes.
  • tim (testing improving model)
  • tmm (testing maturity model)
  • tqm(total quality management)
Q19 | Standards and procedures for managing changes in an evolving software product is called?
  • confirmation management
  • confederation mangement
  • configuration management
  • compartability management
Q20 | Path Tested = Number of Path Tested / Total Number of Paths
  • true
  • false
Q21 | This Testing Technique examines the basic program structure and it derives the test data from the program logic; Ensuring that all statements and conditions executed at least once. It is called as
  • block box testing
  • white box testing
  • grey box testing
  • closed box testing
Q22 | This type of test include, how well the user will be able to understand and interact with the system?
  • usability testing
  • user acceptance testing
  • alpha testing
  • beta testing.
Q23 | Defects generally fall into the following categories?
  • wrong
  • missing
  • extra
  • all the above
Q24 | What is correct Software Process Cycle?
  • plan(p)------>check(c)------>act(a)----->do(d)
  • plan(p)------>do(d)------>check(c)----->act(a)
  • plan(p)------>do(d)------>act(a)----->check(c)
Q25 | Conducted to validate that the application, database, and network they may be running on can handle projected volumes of users and data effectively. The test is conducted jointly by developers, testers, DBA’s and network associates after the system Testing called as
  • functional testing
  • stress/load testing
  • recovery testing
  • integration testing