1 / 25

JAD Session Testing

JAD Session Testing. Types of Tests. Unit Testing Sub-system Testing System Integration Testing Performance Testing Acceptance Testing Beta Testing. Unit Testing. GIS Data* Bridge Data* Restrictions Routing Mapping Restriction Editor Web Interface.

annem
Télécharger la présentation

JAD Session Testing

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. JAD Session Testing

  2. Types of Tests • Unit Testing • Sub-system Testing • System Integration Testing • Performance Testing • Acceptance Testing • Beta Testing

  3. Unit Testing • GIS Data* • Bridge Data* • Restrictions • Routing • Mapping • Restriction Editor • Web Interface * Items covered by both Unit Testing and System Integration Testing

  4. Unit Testing – GIS Data • All TxDOT roads correctly identified • Load Zone roads correctly identified • All other TRM data correctly identified

  5. Unit Testing – Bridge Data • Bridges marked and identified correctly • Verified against BRINSAP? • Verified against permit book • Verified through other methods

  6. Unit Testing - Restrictions • Restrictions comprehensive and complete • Restrictions cover all scenarios • Restrictions match permit book

  7. Unit Testing - Routing • Routing w/o restrictions acceptable to TxDOT • Routing around restrictions work

  8. Unit Testing - Mapping • Map display acceptable to TxDOT • Maps display restrictions acceptably • Maps display all other needed data

  9. Unit Testing – Restriction Editor • Acceptable operation both locally and remotely • Display map data • Acceptable display and marking of restrictions

  10. Unit Testing – Web Interface • Correct operation • Map display • Location entry • Navigation

  11. Sub-system Testing • Routing • Restriction Editor • Web Interface • Re-route • Reporting • Updating

  12. Sub-system Testing - Routing • Routing with restrictions acceptable to TxDOT

  13. Sub-system Testing – Restriction Editor • Restrictions saved correctly • Routing around restrictions match web routing • Restriction retirement notification process works correctly • Correct operation of restriction initialization/retirement process

  14. Sub-system Testing – Web Interface • Bid Routes work correctly • Save/recall user trips • Correct routing/map display • Correctly saves trips • Permit officer routing

  15. Sub-system Testing – Re-route • Correct notification

  16. Sub-system Testing - Reporting • Correct reporting of trips • Canned reports

  17. Sub-system Testing - Updating • Correct updating of TxDOT data • Correct migration of restrictions • Correct display of historical trips over deactivated road segments • Correct routing of historical trips • Correct display of historical restrictions

  18. System Integration Testing • GIS Data • Bridge Data • CPS

  19. System Integration Testing – GIS Data • All TxDOT road correctly identified • Load Zone roads correctly identified • All other TRM data correctly identified

  20. System Integration Testing – Bridge Data • Bridges marked and identified correctly • Verified against BRINSAP? • Verified against permit book • Verified through other methods

  21. System Integration Testing – CPS • Start routing session for new permit • Start routing session for existing permit • Correctly return session to CPS • CPS updates permit information • Passing route and map information back to CPS • Bid route interface

  22. Performance Testing • Single system test • Ultimate load to failure • System behavior at failure • Multi-system test • Scaling estimates • DB server load • System responsiveness at peak loads

  23. Acceptance Testing • GIS/Bridge database accurate • Routing acceptable • Restriction process acceptable • Interface with CPS acceptable • Web interface acceptable • Report generation acceptable • Re-route notification acceptable • Update process acceptable • Performance acceptable • Installation/operation acceptable

  24. Beta Testing • Users able to understand and use the system • Documentation helpful

  25. Q & A

More Related