Softwaretest. Kvalitetssikring og kvalitetskontrol. Kvalitetssikring og kvalitetskontrol. Kvalitetssikring.

Transcription

1 Softwaretest Version: 30/11 10:30 Kvalitetssikring og kvalitetskontrol Kvalitetssikring The planned and systematic activities implemented in a quality system so that quality requirements for a product or service will be fulfilled Kvalitetssikring og kvalitetskontrol Kvalitetskontrol a system of routine technical activities, to measure and control the quality of the inventory as it is being developed. The QC system is designed to: Provide routine and consistent checks to ensure data integrity, correctness, and completeness; Identify and address errors and omissions; Document and archive inventory material and record all QC activities. 1

2 Formål med test (kvalitetskontrol) Testens Faser Komponenttest (unittest) Integrationstest Systemtest Brugertest Alfatest Betatest Acceptest funktionstest What sort of tests shall we write? System integration testing (Tester) Component X Functional/ Nonfunctional Testing Alfa/ Beta (Tester) Class A Component Y Class B Integration testing (Developer) Class C Class D Unit testing (Developer) 2

3 Different focus of tests during lifecycle Unit tests essential quality control, focus on each distinct unit of work: improve design, serves as documentation, enable refactoring Integration tests interactions between components (objects, services, subsystems) Functional tests expecting end results, testing apps use cases Stress/load tests testing under the stress (a lot of users, requests) Usability tests easy of use from the user point of view Acceptance tests does application meets customer s needs? Brugertest Planlæg brugertest sæt klare mål Beskriv testaktiviteter (test af scenarier i UC) Lav test cases for hver aktivitet Hvordan skal vi teste hvert scenarie Opstil testmiljø Gennemføres efter hver iteration Inception Elaboration Construction Transition Accepttest Acceptance testing is formal testing conducted to determine whether or not a system satisfies its acceptance criteria, and to enable the customer, user or authorized entity to determine whether or not to accept the system. acceptance criteria is described in the Product Acceptance Plan 3

4 Artifact: Product Acceptance Plan describes how the customer will evaluate the deliverable artifacts from a project to determine if they meet a predefined set of acceptance criteria Acceptance Test test cases To ensure an effective User Acceptance Testing Test cases are created. These Test cases can be created using various use cases identified during the Requirements definition stage. The Test cases ensure proper coverage of all the scenarios during testing. Each Test Case describes in a simple language the precise steps to be taken to test something. Test cases 4

5 Test cases Following each possible path through the use case in the above diagram, the different use-case scenarios can be identified. Beginning with the basic flow and then combining the basic flow with alternate flows, the following use-case scenarios can be identified: Scenario 1 Basic Flow Scenario 2 Basic Flow Alternate Flow 1 Scenario 3 Basic Flow Alternate Flow 1 Alternate Flow 2 Scenario 4 Basic Flow Alternate Flow 3 Scenario 5 Basic Flow Alternate Flow 3 Alternate Flow 1 Scenario 6 Basic Flow Alternate Flow 3 Alternate Flow 1 Alternate Flow 2 Scenario 7 Basic Flow Alternate Flow 4 Scenario 8 Basic Flow Alternate Flow 3 Alternate Flow 4 UAT the process 1) User Acceptance Test (UAT) Planning 2) Designing UA Test Cases 3) Selecting a Team that would execute the (UAT) Test Cases 4) Executing Test Cases 5) Documenting the Defects found during UAT 6) Resolving the issues/bug Fixing 7) Sign Off Test og UML Test af UML diagrammer Brug reviews Reviews er formelle, dvs kræver planlægning, forberedelse, gennemførelse og opfølgning Fordele ved reviews: Giver fælles sprog og forståelse på tværs 5

6 Test og UML Test af use cases Test at modellen beskriver de rigtige krav Hver use case er grundlag for fortsat test Core Process Workflows Business Modeling Requirements Analysis & Design Implementation Test Models Realized By Business Use- Case Model Use-Case Model Realized By Implemented By Verified By B OK OK B B B Business Object Model Automated By Design Model Implementation Model Fail Test Model Use Cases and Test Early Specification of test cases will improve quality of the requirement specification Acceptance specification Perform the User acceptance test Use Case specification Requirements User acceptance test Creation of test cases are directly tied to the flow detailed in the Use Case Design System test Implementation Test og UML Test af klassediagrammer (Statisk) Test at klassemodellen stemmer overens med kravene fra (fra use cases) og sekvensdiagramet Test af sekvensdiagrammer (dynamisk) Test at sekvensdiagrammet stemmer overens med kravene og klassediagrammet 6

7 Testteknikker Whitebox Interne dele testes Blackbox Systemet testes udefra Review (mange typer) Gennemgang af materiale fortaget af en gruppe Test strategier 7

8 Test i UP faserne 4 milestones in test perspective time Inception Elaboration Construction Transition Agreement on scope, priorities, estimations? How to proceed? Risks identified? Set up acceptance test Stable product to be deployed? System test Stable vision, requirements, architecture? Demonstrated? Risks mitigated? Test approach proven? Plan for construction? Continuos functional testing Is the user satisfied? Acceptance test 8

9 Målet med iterativ testing Nøglen til succes 9