![Phân tích tư tưởng của nhân dân qua đoạn thơ: Những người vợ nhớ chồng… Những cuộc đời đã hóa sông núi ta trong Đất nước của Nguyễn Khoa Điềm](https://timtailieu.net/upload/document/136415/phan-tich-tu-tuong-cua-nhan-dan-qua-doan-tho-039-039-nhung-nguoi-vo-nho-chong-nhung-cuoc-doi-da-hoa-song-nui-ta-039-039-trong-dat-nuoc-cua-nguyen-khoa-136415.jpg)
Bài giảng Công nghệ phần mềm: Software Testing - Nguyễn Thị Cẩm Hương
Số trang: 109
Loại file: pdf
Dung lượng: 2.76 MB
Lượt xem: 12
Lượt tải: 0
Xem trước 10 trang đầu tiên của tài liệu này:
Thông tin tài liệu:
Bài giảng "Công nghệ phần mềm: Software Testing - Nguyễn Thị Cẩm Hương" presentation of content: Why should we test, terminologies, functional testing, equivalence class testing, decision table based testing, levels of coverage,... Invite you to reference.
Nội dung trích xuất từ tài liệu:
Bài giảng Công nghệ phần mềm: Software Testing - Nguyễn Thị Cẩm HươngSoftware Testing What is Testing? Testing is the process of demonstrating that errors are not present The purpose of testing is to show that a program performs its intended functions correctly Testing is the process of establishing confidence that a program does what it is suppose to do. These definitions are incorrect. Why??? “Testing is the process of executing a program with the intent of finding errors” Why should We Test? Although Software Testing is an expensive activity. However, if we produce a software product without Testing may lead to cost potentially much higher than of testing In so-called “Life Critical System”, economics must not be the prime consideration while deciding whether a product should be released to a customer. In commercial system it is often difficult to estimate the cost of errors. Who should Do the Testing? It is very difficult for software developer to point out errors from own creations(Why?) Testing persons are different from Development persons for the overall benefit of the system Developers provide guide lines during testing Whole responsibility is owned by Testing persons What should We Test? It is not possible to test the software for all possible combination of input cases (example) It is impossible to execute all path the program (example) Complete Testing is impossible, although we may wish to do so. Organizations should develop strategies and policies for choosing effective testing techniques TERMINOLOGIES Error, Mistake, Bug, Fault and Failure Error: People make errors. A good synonym is MISTAKE. Mistakes during coding is called Bug Fault: An error may lead to one or more faults. Fault is the representation of error. Defect is a good synonym for fault Failure: occurs when a fault executes. One fault may lead to many Failures TERMINOLOGIES Test, Test Case, Test Suite A Test: is the act of exercising software with test cases. There are two distinct goals of a test: either to find failures, or to demonstrate correct execution. TERMINOLOGIES Test, Test Case, Test Suite Test Case: Describes an input description and an expected output description (example) A Good Test Case has high probability of finding an error The main objective of Test Case Designer is to identify good test cases Test Suite: the set of test cases. Any combination of test cases may generate a Test Suite TERMINOLOGIES Verification and Validation Verification: the process of conforming that software meets its specification (Checking the software with respect to specification) Validation: the process of conforming that software meets the customer’s requirements (Checking the software with respect to customer’s expectation) If there is a gap at SRS level that will only be know during validation activities Poor understand of expectation may lead to incorrect specifications TERMINOLOGIES Alpha, Beta and Acceptance Testing Alpha and Beta Testing: used when the software developed as a product for anonymous customers. Alpha tests are conducted at developer’s site by customer. This test may be stared when formal testing process near completion Beta tests are conducted by the customers/end users at their site. Beta testing is conducted in a real environment that cannot be control by the developer. TERMINOLOGIES Alpha, Beta and Acceptance Testing Acceptance Testing: used when the software is developed for a specific customer. A series of test are conducted to enable the customer to validate all requirements. These test are conducted by the end user/customer Example 1 A program requires two 8 bit integers as inputs, so total possible combinations are: 28 x 28 If one second is required to execute one set of inputs, it will take 18 hours. Example 2 Suppose we have a program which uses loop and If statement as following: The number of paths in the example is 1014 If only 1 minute is require to test one path, it may take 1/5 billion years to execute all path. Functional Testing 14 Complete Testing is not all possible We may like to reduce this incompleteness as much as possible. What we are looking for is a set of thought processes that allow us to select a set of data more intelligently. (the poorest methodology is random input testing) 15 What is Functional Testing? Functional Testing (also know as Behavior testing) is based on the Functionality of the program. It is involves only observation of the output for certain input values. There is no att ...
Nội dung trích xuất từ tài liệu:
Bài giảng Công nghệ phần mềm: Software Testing - Nguyễn Thị Cẩm HươngSoftware Testing What is Testing? Testing is the process of demonstrating that errors are not present The purpose of testing is to show that a program performs its intended functions correctly Testing is the process of establishing confidence that a program does what it is suppose to do. These definitions are incorrect. Why??? “Testing is the process of executing a program with the intent of finding errors” Why should We Test? Although Software Testing is an expensive activity. However, if we produce a software product without Testing may lead to cost potentially much higher than of testing In so-called “Life Critical System”, economics must not be the prime consideration while deciding whether a product should be released to a customer. In commercial system it is often difficult to estimate the cost of errors. Who should Do the Testing? It is very difficult for software developer to point out errors from own creations(Why?) Testing persons are different from Development persons for the overall benefit of the system Developers provide guide lines during testing Whole responsibility is owned by Testing persons What should We Test? It is not possible to test the software for all possible combination of input cases (example) It is impossible to execute all path the program (example) Complete Testing is impossible, although we may wish to do so. Organizations should develop strategies and policies for choosing effective testing techniques TERMINOLOGIES Error, Mistake, Bug, Fault and Failure Error: People make errors. A good synonym is MISTAKE. Mistakes during coding is called Bug Fault: An error may lead to one or more faults. Fault is the representation of error. Defect is a good synonym for fault Failure: occurs when a fault executes. One fault may lead to many Failures TERMINOLOGIES Test, Test Case, Test Suite A Test: is the act of exercising software with test cases. There are two distinct goals of a test: either to find failures, or to demonstrate correct execution. TERMINOLOGIES Test, Test Case, Test Suite Test Case: Describes an input description and an expected output description (example) A Good Test Case has high probability of finding an error The main objective of Test Case Designer is to identify good test cases Test Suite: the set of test cases. Any combination of test cases may generate a Test Suite TERMINOLOGIES Verification and Validation Verification: the process of conforming that software meets its specification (Checking the software with respect to specification) Validation: the process of conforming that software meets the customer’s requirements (Checking the software with respect to customer’s expectation) If there is a gap at SRS level that will only be know during validation activities Poor understand of expectation may lead to incorrect specifications TERMINOLOGIES Alpha, Beta and Acceptance Testing Alpha and Beta Testing: used when the software developed as a product for anonymous customers. Alpha tests are conducted at developer’s site by customer. This test may be stared when formal testing process near completion Beta tests are conducted by the customers/end users at their site. Beta testing is conducted in a real environment that cannot be control by the developer. TERMINOLOGIES Alpha, Beta and Acceptance Testing Acceptance Testing: used when the software is developed for a specific customer. A series of test are conducted to enable the customer to validate all requirements. These test are conducted by the end user/customer Example 1 A program requires two 8 bit integers as inputs, so total possible combinations are: 28 x 28 If one second is required to execute one set of inputs, it will take 18 hours. Example 2 Suppose we have a program which uses loop and If statement as following: The number of paths in the example is 1014 If only 1 minute is require to test one path, it may take 1/5 billion years to execute all path. Functional Testing 14 Complete Testing is not all possible We may like to reduce this incompleteness as much as possible. What we are looking for is a set of thought processes that allow us to select a set of data more intelligently. (the poorest methodology is random input testing) 15 What is Functional Testing? Functional Testing (also know as Behavior testing) is based on the Functionality of the program. It is involves only observation of the output for certain input values. There is no att ...
Tìm kiếm theo từ khóa liên quan:
Công nghệ phần mềm Bài giảng Công nghệ phần mềm Software Testing Why should we test Equivalence class testing Decision table based testingTài liệu liên quan:
-
62 trang 408 3 0
-
Giáo trình Công nghệ phần mềm nâng cao: Phần 2
202 trang 237 0 0 -
Giáo trình Công nghệ phần mềm nâng cao: Phần 1
151 trang 200 0 0 -
Lecture Introduction to software engineering - Week 3: Project management
68 trang 194 0 0 -
Báo cáo chuyên đề Công nghệ phần mềm: Pattern searching
68 trang 192 0 0 -
Xây dựng mô hình và công cụ hỗ trợ sinh tác tử giao diện
13 trang 187 0 0 -
6 trang 183 0 0
-
Bài giảng Công nghệ phần mềm - Chương 2: Quy trình xây dựng phần mềm
36 trang 166 0 0 -
Tìm hiểu về ngôn ngữ lập trình C: Phần 1 - Quách Tuấn Ngọc
211 trang 151 0 0 -
Cuộc chiến Phân kỳ - Tích hợp nhiều tranh cãi bậc nhất trong giới marketing
3 trang 151 0 0