Quality Assurance Flashcards
What is Quality?
Quality is the totality of features and charateristics of a product or service which bear on its ability to satisfy a given need.
What are Quality objectives?
Right order - Right people - professional standards - controlled manner.
What are Quality techniques?
Requirements driven testing - walkthrough and inspections - post project reviews - service level agreements (sla).
Why is Testing necessary?
Because software systems are everywhere, failed software may result in financial loss, wasted time, loss of repoutation, injury or death. Therefore, testing reduces the risk of software failure.
What are the three main causes of defects?
Error (human action that product an incorrect fault) - Defect (flaw in the system that can cause it to fail) - Failure (deviation of system from its expected delivery).
What are the five fundamental test processes?
Test Planning and Control - Test Analysis and Design - Test Implementation and Execution - Evaluating Exit Criteria and Reporting - Test Closure Activities.
What is risk-based Testing?
It is virtually impossible to Test everything therefore we must use a targeted approach that is based on RISK.
What is requirements driven Testing?
Testing will be based off the requirements in the test basis. In UML FR are expressed as Use Cases, therefore the Test Basis is a set of Use Cases.
What is Black-Box Testing?
Testing, either functional or non-functional, without reference to the internal structure of the component or system.
What is White-Box Testing?
Testing based on an analysis of the internal structure of the component or system.
What is a Test Condition?
An item or event of a software that can be verified by one or more tests.
What is a Test Case?
A set of input values, execution pre-conditions, expected results and execution post-conditions developer for a particular test condition.
What is Input Data in Testing?
Input required to test the condition.
What is Base Data in Testing?
Stored data.
Can Tests be derived from a Main Flow?
Yes - by analysing the flow and consider the input data and the base data.
What is a Test Procedure?
Created to support test cases. They should include instructions for grouping of test cases, intiating tests, executing tests, recording test results, termianting tests, inspecting the results.
What is Testing in Agile?
It takes form of anumber of ‘acceptance criteria’ which are nnotated at the back of the user story. Tests verify and determine when the user story is done. It is called test-driven requirements engineering.
How can we Test NFRs?
Testing NFRs is difficult prior to release, NFRs are subject to the SLAs signed with operations.
What are some charateristics of Informal Reviews?
A review with no formal process, inexepensive, recordings are optional. Usually called buddy reviews or desk checks.
What are some charateristics of Walkthroughs?
Contain formal elements, scenarios and dry runs take place. These are open ended sessions. Purpose is to learn and gain an understanding.
What are some charateristics of Technical Reviews?
There are some formal elements, it is documented and defined. Ideally led by a moderator. Main purpose is to discuss the product, make decisions, evaluate alternatives, find defects, solve problems.
What are some charateristics of Inspections?
A formal process based on rules, checklists and entry/exit criteria, led by a moderator with defined roles.
What are the key activities in Inspections?
Planning - kick-off - individual preparation - review meeting - rework - follow-up
What are the key roles in Inspections?
Moderator/leader - author - reviewers - manager - scribe
What are the objectives of a Post Project Review?
Review the development project, document lessons learnt, document probblem areas, prepare a post project report.
What is the typical information gathered in a Post Project Review?
Information on approach, techniques, communications, technology, project management, estimating, risks and issues, user involvmenent.
What is a Post Project Review Report?
Report produced to document the finidngs. Requires stakeholder agreement. It will aim to realise benefits of system, avoid reinventing the wheel, improve estimates and plans, re-use what worked, avoid what didn’t work, correct any mistake.
What is a Service Level Agreement (SLA)?
Document that descibres the relationship between two parties, the service provider and the service user.
What happens if an SLA is used properly?
Identify and define user needs, provide a framework for understanding, simplify complex issues, reduces areas of conflict, encourage dialogue in the event of disputes, eliminate unrealistic expectations.
What are the factors addressed by SLA?
Services to be delivered, performance, tracking and reporting, problem management, legal compliance and resolution, customer duties and responsabilities, security, IPR, termiantion.
