Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 1 _ 1.1 - Coggle Diagram

- - - - Review Docuement
        
        Design Testcase base on Document
    - - Planning and Design test start Early in the project
        
        The planing, analysis, and design work might indentify defects in the requirement, making testing a preventive activity
        
        Failure detection would start much later in the lifecycle, once system test execution begin
        
        Activities of each test level occurs concurrently with project activites
        
        Test planing and Test control == Project Plan and Control
        
        Test analysis and Design = Requirement, HL Design, LL Design
        
        Test Enviroment == coding + component test
        
        Test Execution == Test entry critearia all meet
        
        Evaluation criteria and reporting == Test Execution
        
        Test Closure Activities = All project activities are finished
    - - Schedule compression during testing at the end of the project
        
        Development group, likewise pressured to achieve dates, delivering unstable and often untestable system to test team
        
        The test team is involved late
  - - - Use a less formalized process and a much closer working realationship that allows changes to occur more easily within project
        
        Less comprehensive test document in a favor of a having a more rapid method of communication such as daily "standup" meeting
        
        Require the earliest involvement from the test anlyst and throughout project lifecycles:
        -- Working with the developers as they do their initial architecture and design work
        -- Reviews may not be formalized but are continous as the software evoles
        
        Good change management and configuration management are critical for testing
        
        Không có tài liệu đầy đủ, quy trình tối giản nhất
        
        Ít tài liệu document, thay vào đó là daily standup meeting
        
        Cần có sự tham gia sớm của Test Analyst đề:
        -- Làm việc với DEV khi họ khởi tạo thiết kế kiến trúc
        -- Review có thể ko cần thực hiện theo formal, mà chỉ cần peer reviews
        
        Cần quản lý về change management
  - - - The test team won't received a complete set of requirement early in the project
        
        Analyzing requirement at the outset of the project, the best test team can do is to identify and prioritize key quality risk areas
        
        Specific test designs and implementation will occur immediately before test execution, potenially reducing the preventive role of testing
        
        Defect detection start very ealry in the project, at the end of the first sprint, and continues in repetitive, short cycles throughout the project
        
        Testing process overlap and are concurrent with each other as well as with major activities in the software lifecycles
    - - Regression test all function and capabilities after the first interation
        
        Failure to plan for bugs and how to handle them
        
        The lack of rigor in and respect for testing
        
        The designer of the system will change
        
        Schedule can be quite unpredicable
        
        Regresstion test cho tất cả các tính năng và đặc điểm sau chu trình đầu tiên
        
        Kế hoạch cho bug bị false và làm thế nào để xử lý nó
        
        Sự thiếu nghiêm túc và tôn trọng với test
        
        Thiết kế của hệ thống sẽ bị thay đổi
        
        Kế hoạch thì khó dự đoán trước