1 / 10

Test

Test. V-model. Wikipedia : http://en.wikipedia.org/wiki/V-Model_(software_development). Verification & Validation. Verification Phases Requirements analysis System Design Architecture Design Module Design Validation Phases Unit Testing Integration Testing System Testing

mckenzie-may
Download Presentation

Test

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test

  2. V-model Wikipedia: http://en.wikipedia.org/wiki/V-Model_(software_development)

  3. Verification & Validation • Verification Phases • Requirements analysis • System Design • Architecture Design • Module Design • Validation Phases • Unit Testing • Integration Testing • System Testing • User Acceptance Testing

  4. Types (or Stages) of Testing(Validation) • Developer Testing • Normal testing by the developer / programmer – to see it do work • Independent and Stakeholder Testing • Independent Testing denotes the test design and implementation that it is most appropriate for someone independent from the team of developers to do. • Unit Tests • Systematic automatic test of a unit (testing from a black box view) • Integration Test • integration testing is performed to ensure that the components in combination do work (e.g. that classes across packages do work) • System Test • System testing is done when the software is functioning as a whole. Do the whole system works • Acceptance Test • The users do the testing and accepting as a final test action prior to deploying the software. Check that all use-cases and all non-functional requirements work

  5. Unit testing • White box testing • where you check all programming lines have been executed with an accepted result • Black box testing • where you check all methods have been executed and all parameter boundaries have been checked – of cause again with an accepted result

  6. Black-box (UPedu) • input argument • Normal values from each equivalence class. • Values on the boundary of each equivalence class. • Values outside the equivalence classes. • Illegal values. • output argument • Normal values from each equivalence class. • Values on the boundary for each equivalence class. • Values outside the equivalence classes. • Illegal values.

  7. Set up test-cases • Follow / Fill out schema

  8. Example - Book • Constrains: • The title must be not null and not empty. • The Author must be not null and not empty. • The isbn must be not null and the length must be greater than 9 • copyId must be in the range 1-15

More Related