Kinh doanh - Marketing
Kinh tế quản lý
Biểu mẫu - Văn bản
Tài chính - Ngân hàng
Công nghệ thông tin
Tiếng anh ngoại ngữ
Kĩ thuật công nghệ
Khoa học tự nhiên
Khoa học xã hội
Văn hóa nghệ thuật
Sức khỏe - Y tế
Văn bản luật
Nông Lâm Ngư
Kỹ năng mềm
Luận văn - Báo cáo
Giải trí - Thư giãn
Tài liệu phổ thông
Văn mẫu
Giới thiệu
Đăng ký
Đăng nhập
Tìm
Danh mục
Kinh doanh - Marketing
Kinh tế quản lý
Biểu mẫu - Văn bản
Tài chính - Ngân hàng
Công nghệ thông tin
Tiếng anh ngoại ngữ
Kĩ thuật công nghệ
Khoa học tự nhiên
Khoa học xã hội
Văn hóa nghệ thuật
Y tế sức khỏe
Văn bản luật
Nông lâm ngư
Kĩ năng mềm
Luận văn - Báo cáo
Giải trí - Thư giãn
Tài liệu phổ thông
Văn mẫu
Thông tin
Điều khoản sử dụng
Quy định bảo mật
Quy chế hoạt động
Chính sách bản quyền
Giới thiệu
Đăng ký
Đăng nhập
0
Trang chủ
Công Nghệ Thông Tin
Kỹ thuật lập trình
Lecter Java: Program design - Chapter 13: Testing and debugging
Đang chuẩn bị liên kết để tải về tài liệu:
Lecter Java: Program design - Chapter 13: Testing and debugging
Phương Nghi
91
17
ppt
Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
After completing this unit, you should be able to: Introduce various testing techniques including black-box testing, white-box testing, unit testing, integration testing, and system testing; present and explain the value of inspections and code reviews; introduce techniques for developing effective and efficient test cases such as statement coverage, path coverage, and equivalence partitioning. | Testing and Debugging Testing Fundamentals Test as you develop Easier to find bugs early rather than later Prototyping helps identify problems early Categories of bugs software crashes or data corruption failure to meet or satisfy the specification poor or unacceptable performance hard or difficult to use Testing fundamentals Impossible to test a program completely Three distinct paths through the program If the loop executes 20 times, there are 320 different sequences of executions Reviews and inspections Inspections Formal process of reviewing code First employed by IBM in 1976 Early work showed that design and review inspections remove 60 percent of the bugs in a product Reviews and inspections Roles of participants Moderator Runs the inspection Ensure that the process moves along Referees the discussion Ensures action items done Inspector Someone other than author Some interest in the code Carefully review code before inspection meeting Author Minor role May answer questions about | Testing and Debugging Testing Fundamentals Test as you develop Easier to find bugs early rather than later Prototyping helps identify problems early Categories of bugs software crashes or data corruption failure to meet or satisfy the specification poor or unacceptable performance hard or difficult to use Testing fundamentals Impossible to test a program completely Three distinct paths through the program If the loop executes 20 times, there are 320 different sequences of executions Reviews and inspections Inspections Formal process of reviewing code First employed by IBM in 1976 Early work showed that design and review inspections remove 60 percent of the bugs in a product Reviews and inspections Roles of participants Moderator Runs the inspection Ensure that the process moves along Referees the discussion Ensures action items done Inspector Someone other than author Some interest in the code Carefully review code before inspection meeting Author Minor role May answer questions about code Reviews and inspections Roles of participants Scribe Record all errors detected Keep list of action items Reviews and inspections Inspection process Planning Code to review chosen Moderator assigns task Checklists created Moderator assigns a presenter (usually one of the inspectors) Overview Author describes high-level aspects of project that affected the design or code Sometimes skipped (if all participants are knowledgeable) Reviews and inspections Inspection process Preparation Working alone, each inspector reviews code noting problems or questions Shouldn’t take more than a couple of hours Inspection meeting Presenter walks through the code Problems are discussed Scribe records all errors and action items Errors are not fixed at this time Inspection report Moderator prepares a written report Black-box and white-box testing White-box testing indicates that we can “see” or examine the code as we develop test cases Block-box testing indicates that we cannot examine the code as .
TÀI LIỆU LIÊN QUAN
Lecter Java: Program design - Chapter 2: Java basics
Lecter Java: Program design - Chapter 6: Iteration
Lecter Java: Program design - Chapter 10: Exceptions
Lecter Java: Program design - Chapter 1: Introduction
Lecter Java: Program design - Chapter 4: Classes
Lecter Java: Program design - Chapter 8: Arrays
Lecter Java: Program design - Chapter 3: Objects
Lecter Java: Program design - Chapter 5: Decisions
Lecter Java: Program design - Chapter 7: Programming withmethods and classes
Lecter Java: Program design - Chapter 9: Inheritance and polymorphism
crossorigin="anonymous">
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.