1 / 37

Part V: Working with Test Documentation

Part V: Working with Test Documentation. Outline. 17 Planning Your Test Effort 18 Writing and Tracking Test Cases  19 Reporting What You Find 20 Measuring Your Success. Planning Your Test Effort. The purpose of test planning

josemmoore
Download Presentation

Part V: Working with Test Documentation

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. Part V: Working with Test Documentation

  2. Outline • 17 Planning Your Test Effort • 18 Writing and Tracking Test Cases  • 19 Reporting What You Find • 20 Measuring Your Success

  3. Planning Your Test Effort • The purpose of test planning • is a by-product of the detailed planning process that's undertaken to create it. • The ultimate goal of the test planning process is communicating (not recording) the software test team's intent, its expectations, and its understanding of the testing that's to be performed

  4. Test Planning Topics • High-Level Expectations • What's the purpose of the test planning process and the software test plan? Who know that? • What product is being tested? • What are the quality and reliability goals of the product? • People, Places, and Things • Files ,Sotware,hardware

  5. Test Planning Topics • Definitions • concepts that need to be defined for a software project • terms • Build • Test release document (TRD). • Alpha release • Beta release • Feature complete • Bug committee

  6. Test Planning Topics • Inter-Group Responsibilities

  7. Test Planning Topics • What Will and Won't Be Tested • Test Phases • unique phases, or stages, of testing should be performed over the course of the project • Test Strategy • manually and other code with tools and automation? • Resource Requirements • People, Equipment, Office and lab space, Software, Outsource companies, Miscellaneous supplies

  8. Test Planning Topics • Tester Assignments

  9. Test Planning Topics • Test Schedule

  10. Test Planning Topics • Test Cases • write,maintains • Bug Reporting and trace • Bugzilla • Metrics and Statistics • Risks and Issues • identifying risks during the planning process and communicating your concerns to your manager and the project manager.

  11. Writing and Tracking Test Cases • writing and tracking test cases • test design specification • test case specification • How test procedures should be written? • How test cases should be organized?

  12. Writing and Tracking Test Cases • Carefully and methodically planning test cases • Organization & manage test case • Repeatability • Tracking result • Proof of testing (or not testing).

  13. Writing and Tracking Test Cases • different levels of test documents • IEEE 829 • Word template

  14. Writing and Tracking Test Cases • Test Design • Identifiers • Features to be tested. • Approach • Test case identification. • ID#15326 • Pass/fail criteria.

  15. Writing and Tracking Test Cases • Test Cases • Identifiers • Test item • Input specification. • Output specification. • Environmental needs • Special procedural requirements. • Intercase dependencies

  16. Writing and Tracking Test Cases • Test Procedures • Identifier • Purpose • Special requirements • Procedure steps • Log Setup Start Procedure Measure. Shut down. Restart. Stop. Wrap up Contingencies.

  17. Writing and Tracking Test Cases • Test Case Organization and Tracking • In your head • Paper/documents • Spreadsheet • Custom database.

  18. Reporting What You Find • why not fixing all the bugs • There's not enough time • It's really not a bug • It's too risky to fix • It's just not worth it. • Ineffective bug reporting

  19. Reporting What You Find • fundamental principles reporting a bug • Report bugs as soon as possible • Effectively describe the bugs • Minimal, Singular, Obvious and general, Reproducible • Be nonjudgmental in reporting bugs • Follow up on your bug reports.

  20. Reporting What You Find • Isolating and Reproducing Bugs • Don't take anything for granted • Look for time-dependent and race condition problems • boundary condition bugs, memory leaks, and data overflows • State bugs show up only in certain states • resource dependencies and interactions with memory,network… • Don't ignore the hardware

  21. Reporting What You Find • Not All Bugs Are Created Equal • Severity indicates how bad the bug is; the likelihood and the degree of impact when the user encounters the bug. • System crash, data loss, data corruption, security breach • Operational error, wrong result, loss of functionality • Minor problem, misspelling, UI layout, rare occurrence • Suggestion

  22. Reporting What You Find • Priority indicates how much emphasis should be placed on fixing the bug and the urgency of making the fix. • Immediate fix, blocks further testing, very visible • Must fix before the product is released • Should fix when time permits • Would like to fix but the product can be released as is

  23. A Bug's Life Cycle

  24. Bug-Tracking Systems • The Test Incident Report • Identifier • Summary • Incident Description. • Impact • Manual Bug Reporting and Tracking • Automated Bug Reporting and Tracking

  25. Measuring Your Success • What areas of the software you're testing have the most bugs? The fewest bugs? • How many resolved bugs are currently assigned to Martha? • Bob is leaving for vacation soon. Will he likely have all his bugs fixed by then? • Which software tester has entered the most bugs? • Does the software look like it's on track to meet the scheduled release date?

  26. Measuring Your Success • databases have a means to build queries that return the specific information you're looking

  27. Measuring Your Success

  28. Part VI: The Future

  29. 质量保证 • Software Testing • The goal of a software tester is to find bugs, find them as early as possible, and make sure they get fixed. • can't make an inherently poor-quality product better. Quality can't be tested in. Period. • Quality Assurance • Software Quality Assurance person's main responsibility is to examine and measure the current software development process and find ways to improve it with a goal of preventing bugs from ever occurring.

  30. Test Management and Organizational Structures

  31. Software Quality Assurance • Capability Maturity Model (CMM) • 1-5 • ISO 9000 • ISO 9001 is for businesses that design, develop, produce, install, and service products. • ISO 9000-3 is for businesses that develop, supply, install, and maintain computer software.

  32. Career as a Software Tester • Job as a Software Tester • Software Test Technician. • Software Tester or Software Test Engineer • Software Test Toolsmith or Software Development Engineer in Test • Software Test Lead • Software Test Manager

  33. Formal Training Opportunities • Conferences • International Software Testing Conference (ISTC) • Software Testing Analysis & Review (STAR), • International Conference on Software Quality (ICSQ) • International Conference on Software Testing (ICSTEST), • The World Conference for Software Quality (WCSQ)

  34. 实习四 • 运用测试技巧 • 执行《运用测试技巧》各项测试 • 可以交换测试

  35. 完成课程报告 • 测试用例的设计、实现 • 静态白盒测试 • 问题 • 解决方法 • 单元测试 • 用例 • Bug和解决方案 • 运用测试技术 • Bug • 解决方案

More Related