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
Lecture Software engineering: Lecture 8 - Ivan Marsic
Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Software engineering: Lecture 8 - Ivan Marsic
Bảo Vân
122
28
ppt
Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Lecture 8: Software testing. The main contents of this chapter include all of the following: Overview of software testing, test coverage and code coverage, practical aspects of unit testing, integration and system testing. | Ivan Marsic Rutgers University LECTURE 8: Software Testing Topics Overview of Software Testing Test Coverage and Code Coverage Practical Aspects of Unit Testing Integration and System Testing Overview of Software Testing “Testing shows the presence, not the absence of bugs.” —Edsger W. Dijkstra A fault, also called “defect” or “bug,” is an erroneous hardware or software element of a system that can cause the system to fail Test-Driven Development (TDD) Every step in the development process must start with a plan of how to verify that the result meets a goal The developer should not create a software artifact (a system requirement, a UML diagram, or source code) unless they know how it will be tested A test case is a particular choice of input data to be used in testing a program A test is a finite collection of test cases Why Testing is Hard A key tradeoff of testing: testing as many potential cases as possible while keeping the economic costs limited Our goal | Ivan Marsic Rutgers University LECTURE 8: Software Testing Topics Overview of Software Testing Test Coverage and Code Coverage Practical Aspects of Unit Testing Integration and System Testing Overview of Software Testing “Testing shows the presence, not the absence of bugs.” —Edsger W. Dijkstra A fault, also called “defect” or “bug,” is an erroneous hardware or software element of a system that can cause the system to fail Test-Driven Development (TDD) Every step in the development process must start with a plan of how to verify that the result meets a goal The developer should not create a software artifact (a system requirement, a UML diagram, or source code) unless they know how it will be tested A test case is a particular choice of input data to be used in testing a program A test is a finite collection of test cases Why Testing is Hard A key tradeoff of testing: testing as many potential cases as possible while keeping the economic costs limited Our goal is to find faults as cheaply and quickly as possible. Ideally, we would design a single “right” test case to expose each fault and run it In practice, we have to run many “unsuccessful” test cases that do not expose any faults Logical Organization of Testing Unit test Unit test Unit test Integration test Component code Component code Component code Tested component Integrated modules Function test Quality test Acceptance test Installation test System test System in use Ensure that each component works as specified Ensures that all components work together Verifies that functional requirements are satisfied Verifies non-functional requirements Customer verifies all requirements Testing in user environment ( Not necessarily how it’s actually done! ) Acceptance Tests - Examples [ Recall Section 2.2: Requirements Engineering ] Test with the valid key of a current tenant on his/her apartment (pass) Test with the valid key of a current tenant on someone else’s apartment (fail) .
TÀI LIỆU LIÊN QUAN
Lecture Software requirements engineering - Lecture 8: Requirements elicitation process
Lecture Software requirements engineering - Lecture 8: Requirements elicitation process
Lecture Software engineering: Lecture 8 - Ivan Marsic
Lecture Software engineering: Chapter 8 – Software Testing
Lecture Software engineering (9/e): Chapter 8 - Sommerville
Lecture Software Engineering - Chapter 8: Software Testing (Trường Đại học Bách Khoa TP.HCM)
Lecture Software engineering - Chapter 8: Design concepts
Lecture Software engineering (7/e): Chapter 8 – Ian Sommerville
Lecture Software engineering II: Chapter 8 - Dr. Muzafar Khan
Lecture Software engineering II: Chapter 8 - Dr. Muzafar Khan
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.