Which of the following is not part of performance testing?

Correct Answer: The parameters of Quality Cost are: Speed Accuracy Efficiency Performance Customer Satisfaction

Correct Answer: Usability testing

Correct Answer: Error guessing

Explanation:

Static Testing, a software testing technique in which the software is tested without executing the code. This Techniques provide a powerful way to improve the quality and productivity of software development by assisting engineers to recognize and fix their own defects early in the software development process.

 

It has two parts as listed below:

Review - Typically used to find and eliminate errors or ambiguities in documents such as requirements, design, test cases, etc.

Static analysis - The code written by developers are analysed (usually by tools) for structural defects that may lead to defects.

 

In this software is tested without executing the code by doing Review, Walk Through, Inspection or Analysis etc.

 

Hence, Error guessing is not a static software testing technique.

Correct Answer: Deliverable base-lining

Correct Answer: A test plan is the master document that contains all details pertaining to testing of the application Its contents include: Testing scope - what is included and what is not included in the testing of the current project Assumptions - what are the assumptions that are made for this project Milestones - major dates like when testing is going to begin, when it is planned to end, what is the trace review date, what is the production date etc Resources - the resources working on this project along with their contact details Defect tracking mechanism - what defect tracking tool will be used, what is the SLA for fixing Critical to Low level IRs etc Test management procedures - who will be notified when there is a critical IR, what reports will be sent daily, if status calls will be held daily or weekly, where will it be held, who is required to join etc Work allocation - resource distribution if more projects are being tested Entry and exit criterion - when can a project be accepted for testing (eg only when smoke testing passes) and when can a project be termed as testing complete (eg when all testcases are executed and all high level bugs are fixed)

Correct Answer: BackTracking

Explanation:

BackTracking is used for solving N-Queens problem

Correct Answer: Testing is a process used for revealing defects in s/w and for establishing that the s/w has attained a specific degree of quality The s/w testing group?s main objective is to ensure that the s/w is doing what it is supposed to do as well as the s/w is not doing what it is not supposed to do With this objective, it is clear that it is necessary to have a separate group for testing the s/w other than the group which developed it Also, bugs in the s/w can cause severe monetary as well as other loss to the organization So it is important to allocate some budget for the testing group

Correct Answer: Integration testing is done at module level when various modules are integrated with each other to form a system or sub-system Its main purpose is to ensure that interfaces between various modules are working properly; ie modules which are working individually are also working correctly together System testing is done on a complete, integrated system to evaluate the system?s compliance with its specified requirements It validates that the system meets its functional and non-functional requirements From these definitions, it is clear that the purpose of Integration and purpose of System Testing are different Therefore, Integration test cases focus more on the interfaces between modules (interface integrity) - the data transfer and their interaction with each other System test cases focus on testing the product as a whole; ie whether the functional, non-functional requirements of the System are met or not Since System Testing is the final phase before delivery of the product, System test cases should pinpoint configuration related errors along with testing for performance, security, reliability etc

Correct Answer: Capability Maturity Model (CMM) is a model of 5 levels of process 'maturity' that determine effectiveness in delivering quality software The 5 levels of CMM are described as below: Level 1: Initial: - characterized by chaos, periodic panics, and heroic efforts required by individuals to successfully complete projects Very few or none of the processes are in place Level 2: Repeatable: - Software Project Tracking, Requirements Management, Realistic Planning and Configuration Management Processes are in place; successful practices can be repeated Level 3: Defined: - Standard Software Development and Maintenance Processes are integrated throughout an organization A Software Engineering Process Group is in place to oversee software processes, and training programs are used to ensure understanding and compliance Level 4: Managed: - Metrics are used to track productivity, processes, and products Project performance is predictable, and quality is consistently high Level 5: Optimizing: - The focus is on continuous process improvement The impact of new processes and technologies can be predicted and effectively implemented when required Any organization can start from any level, but its motto is to reach level 5; where the focus is continuous process improvement By doing this, high quality s/w delivery is assured From this, we can see that the whole essence of CMM or CMMI is to produce quality software It targets the whole organizational practices (or processes), which are believed to be the best across industries Testing is part of Quality Assurance CMM levels play an important role in an organization?s Quality Assurance effort Thus testing plays an important role in determining CMM level

Correct Answer: Risk analysis is a method to determine how much risk is involved in something In testing, it can be used to determine when to test something or whether to test something at all Items with higher risk values should be tested early and often Items with lower risk value can be tested later, or not at all It can also be used with defects Severity tells us how bad a defect is: "how much damage can it cause?" Priority tells us how soon it is desired to fix the defect: "should we fix this and if so, by when?" Defects with High Severity and Priority are tested first