What is software?
Another part of the computer software and hardware system interdependent,
The software includes a program document +
What is software testing?
(1) Software testing is to find defects existing software (programs + document) process;
(2) software testing is the use of manual or automatic means to run or test a system, designed to test the system meets the requirements in the requirements specification
The purpose of software testing?
The purpose of the test is to find errors in the software product, the software as much as possible in line with the requirements of users.
Black Box Testing:
Called functional test, the program as a black box, and the structure does not consider internal processing of the program, according to specifications, by the same whether or not a predetermined function of the operating software specification verification process.
White box:
Also known as structural testing, the test is based on the code, detecting whether the program work properly predetermined according to the requirements of the internal logical structure of the program.
Regression Testing:
Regression testing refers to the old code modified, re-tested to confirm the modification does not introduce new bugs or cause other code to generate an error.
Smoke testing:
What is the test?
Test cases are by the document testers before test execution written to guide the testing process
What is a software bug? (How to identify bug)
(1) the requirements specification required features not implemented
(2) Requirements Specification say not achieve the required functions
(3) there is a problem the program specified in the requirements specification should not appear
(4) Requirements Specification Although not explicitly mentioned, but the functions must be implemented not implemented
(5) the program difficult to understand, easy to use, the interface is pretty, the user experience is not good, etc.
(6) refer to requirements documents, and document does not match the actual bug is
(7) discussions with the demand, developers, users
(8) reference test case expected results, actual results and expected results is bug
The first computer was born at what time? What name is called?
1946-2-15 called "Aini Akbar"
Level computer?
The computer is divided into three levels: application software, operating systems, computer hardware / bare metal
Bare metal includes software? How to enter?
Bare metal also includes software, mainly bios program;
Boot or reboot later, quickly press the "delete" key (if it is a notebook, generally function keys such as F2)
Classification software?
Software includes system software and application software
Divided according to system software?
Operating system, operating system patches, drivers
Divided according to software architecture?
It can be divided into stand-alone software and distributed software;
The characteristics of the client software distributed into c / s structure and b / s structure
What is the c / s structure and b / s structure?
①C / S structure: client / server client / server architecture, clients need to use specialized software provided by the company in order to enjoy the service, QQ, micro letter, a taxi drops
②B / S structure: browser / server browser / server architecture, the client as long as the browser can access the service, sites, search engines, forums
What is a bug report?
Defect report documents the test defects found during testing is an important tool for testers and developers to exchange and communication
Defect reports include those (important)?
1. Defect Number: Defect
2. defective title: Summary
3. defects belongs modules: Subject
4. discoverer defects: Detected By
The defects found Date: Detected on date
Defects found in version 6: Detected in release
7. Defect assigned: Assigned to
8. The state of defects: Status
9. severity of defects: Serverity
10. The defect priority: Priority
11. Defect Description: Description
When submitting a bug report, defect classification
Severity (S1): system crashes, data loss, data corruption
More serious (S2): the process that leads to nowhere, operational errors, the result of an error
Module of error (S3): function missing, function not implemented
General error (S4): small problems, typos, interface layout unreasonable
Recommendations error (S5): does not affect product quality defects
Defect processing flow report?
1. testers found a new bug, change their status to new, transferred to the Development Manager
2. Development Manager to verify that the bug is valid:
If a defect, to the Open state, assigned to the respective developer
If it is not a defect, change their status to rejected
3. assigned to developers see their bug, modify, modify finished, the defect status to fixed
4. testers bug fixes were back test:
If successful counter-measure, the defect status to closed
If the returned test fails, the defective state to reopen
Use defect report?
1. Record bug
2. Classification of the bug on the line expression
3. bug tracking and management
4. bug analyzed statistics
What is the severity of the defect? Which is divided into levels? What does each represent?
The severity of defects is to show the impact of software bug caused by the user or how much
1.Urgent: cause crashes, system crashes and other fatal problems
2.Veryhigh: very serious problem
3.High: serious problems
4.Medium: moderate problem
5.Low: small problem (try to solve before the release)
What is the priority defects? Which is divided into levels? What does each represent?
Priority is to defect programmer at what time, or bug fixes in which version of the program
1.Urgent: immediately amend, or otherwise affect the progress of the development of test
2.Veryhigh: This modified version
3.High: the next version modified
4.Medium: Modify before release
5.Low: allows bug exists in the publication
Priority focus on what factors to consider?
1. Severity: generally the higher the severity, the higher the priority (but not strictly proportional)
2. scope: the scope of the larger general, the higher the priority
3. Development Task pressure groups: the smaller the task pressure, the higher the priority
4. Cost solve bug: the lower the cost, the higher the priority
What is the description of the defect?
The bug discovery procedure, process the data, using the record, described by the programmer importance bug
All bug in the software before release must solve it?
Not all of the bug can be resolved before the software is released;
For bug is not resolved, usually through the discussion of the project team, clearly does not solve the bug risk of loss caused to the user as well as the cost of defects resolved
What are some ways to write test cases? Application of each method?
1. equivalence partitioning method
As long as there is data input area can be used to pick out a few representative data from an infinite number of data for testing
2. boundary value method
Wherever there can be used the data input, and the equivalence partitioning method often used together to form a complete testing method; found valid data and invalid data boundary point, boundary point and the point on both sides of the tested individually
3. cause and effect diagram method
In one interface has a plurality of controls, there is a certain relationship between a combination of limits and control relationships, different input combinations produces different output results, in order to clarify the corresponding relationship between the combination of input and output, cause selection method of FIG.
4. The method determination table
And FIG cause determination table is essentially a method, composition control is to solve the problem, a simplified method is a cause determination table of FIG Method
The orthogonal arrangement method
6. scenes Law
7. Test outline law
A reference when writing use cases?
1. Requirements Document (document if you can develop the best reference)
2. Control procedures have been developed
3. and demand, developers, users communicate
Test Ideas?
Exhaustive testing is the most complete testing methods, but because of the high cost of time, the actual work should not be used.
Therefore, to ensure quality, while using a minimum of data to complete the testing process.
What is a valid equivalence class?
Meaningful specification description of the program, a reasonable set of data, the program receives a valid equivalence class data should be calculated correctly performed
What is invalid equivalence class?
Program specifications meaningless, unreasonable collection of data, the program received an invalid equivalence class data, you should give an error message, or simply not allowed to enter
Invalid equivalence class main factors to consider?
1. demand requirements can not be empty or required, invalid equivalence class is empty
2. The data has a range of requirements, invalid equivalence class is out of range
3. The number of characters have claim invalid equivalence class is beyond the prescribed range
4. Data type style formatted request is invalid equivalence class test pattern format. Type illegal
There needs 5 decimal places claim invalid equivalence class is reserved bits exceeds the range
6. demand requirements can not be repeated, it is to repeat invalid equivalence class
A basic feature of good software?
1. To achieve the required functionality
2. With strong exception handling capabilities (robustness)
V model and the advantages and disadvantages
advantage:
1. The testing phase is clearly defined
2. The correspondence between the developed and clear
3. The bottom of the test contains both (Unit Test) further comprises a user-level test (acceptance)
Disadvantages:
1. easy to understand software testing it is to be involved in the development after completion
2. The test does not reflect the work early (write a plan, for example, test document using), does not comply with the principles of the earlier tests and continuous testing
In-depth understanding of:
1. demand, the development of test documentation
2. the preparation of test plans, test cases and other documentation in accordance with the development, use cases perform the most prepared
What is software?
Another part of the computer software and hardware system interdependent,
The software includes a program document +
What is software testing?
(1) Software testing is to find defects existing software (programs + document) process;
(2) software testing is the use of manual or automatic means to run or test a system, designed to test the system meets the requirements in the requirements specification
The purpose of software testing?
The purpose of the test is to find errors in the software product, the software as much as possible in line with the requirements of users.
Black Box Testing:
Called functional test, the program as a black box, and the structure does not consider internal processing of the program, according to specifications, by the same whether or not a predetermined function of the operating software specification verification process.
White box:
Also known as structural testing, the test is based on the code, detecting whether the program work properly predetermined according to the requirements of the internal logical structure of the program.
Regression Testing:
Regression testing refers to the old code modified, re-tested to confirm the modification does not introduce new bugs or cause other code to generate an error.
Smoke testing:
What is the test?
Test cases are by the document testers before test execution written to guide the testing process
What is a software bug? (How to identify bug)
(1) the requirements specification required features not implemented
(2) Requirements Specification say not achieve the required functions
(3) there is a problem the program specified in the requirements specification should not appear
(4) Requirements Specification Although not explicitly mentioned, but the functions must be implemented not implemented
(5) the program difficult to understand, easy to use, the interface is pretty, the user experience is not good, etc.
(6) refer to requirements documents, and document does not match the actual bug is
(7) discussions with the demand, developers, users
(8) reference test case expected results, actual results and expected results is bug
The first computer was born at what time? What name is called?
1946-2-15 called "Aini Akbar"
Level computer?
The computer is divided into three levels: application software, operating systems, computer hardware / bare metal
Bare metal includes software? How to enter?
Bare metal also includes software, mainly bios program;
Boot or reboot later, quickly press the "delete" key (if it is a notebook, generally function keys such as F2)
Classification software?
Software includes system software and application software
Divided according to system software?
Operating system, operating system patches, drivers
Divided according to software architecture?
It can be divided into stand-alone software and distributed software;
The characteristics of the client software distributed into c / s structure and b / s structure
What is the c / s structure and b / s structure?
①C / S structure: client / server client / server architecture, clients need to use specialized software provided by the company in order to enjoy the service, QQ, micro letter, a taxi drops
②B / S structure: browser / server browser / server architecture, the client as long as the browser can access the service, sites, search engines, forums
What is a bug report?
Defect report documents the test defects found during testing is an important tool for testers and developers to exchange and communication
Defect reports include those (important)?
1. Defect Number: Defect
2. defective title: Summary
3. defects belongs modules: Subject
4. discoverer defects: Detected By
The defects found Date: Detected on date
Defects found in version 6: Detected in release
7. Defect assigned: Assigned to
8. The state of defects: Status
9. severity of defects: Serverity
10. The defect priority: Priority
11. Defect Description: Description
When submitting a bug report, defect classification
Severity (S1): system crashes, data loss, data corruption
More serious (S2): the process that leads to nowhere, operational errors, the result of an error
Module of error (S3): function missing, function not implemented
General error (S4): small problems, typos, interface layout unreasonable
Recommendations error (S5): does not affect product quality defects
Defect processing flow report?
1. testers found a new bug, change their status to new, transferred to the Development Manager
2. Development Manager to verify that the bug is valid:
If a defect, to the Open state, assigned to the respective developer
If it is not a defect, change their status to rejected
3. assigned to developers see their bug, modify, modify finished, the defect status to fixed
4. testers bug fixes were back test:
If successful counter-measure, the defect status to closed
If the returned test fails, the defective state to reopen
Use defect report?
1. Record bug
2. Classification of the bug on the line expression
3. bug tracking and management
4. bug analyzed statistics
What is the severity of the defect? Which is divided into levels? What does each represent?
The severity of defects is to show the impact of software bug caused by the user or how much
1.Urgent: cause crashes, system crashes and other fatal problems
2.Veryhigh: very serious problem
3.High: serious problems
4.Medium: moderate problem
5.Low: small problem (try to solve before the release)
What is the priority defects? Which is divided into levels? What does each represent?
Priority is to defect programmer at what time, or bug fixes in which version of the program
1.Urgent: immediately amend, or otherwise affect the progress of the development of test
2.Veryhigh: This modified version
3.High: the next version modified
4.Medium: Modify before release
5.Low: allows bug exists in the publication
Priority focus on what factors to consider?
1. Severity: generally the higher the severity, the higher the priority (but not strictly proportional)
2. scope: the scope of the larger general, the higher the priority
3. Development Task pressure groups: the smaller the task pressure, the higher the priority
4. Cost solve bug: the lower the cost, the higher the priority
What is the description of the defect?
The bug discovery procedure, process the data, using the record, described by the programmer importance bug
All bug in the software before release must solve it?
Not all of the bug can be resolved before the software is released;
For bug is not resolved, usually through the discussion of the project team, clearly does not solve the bug risk of loss caused to the user as well as the cost of defects resolved
What are some ways to write test cases? Application of each method?
1. equivalence partitioning method
As long as there is data input area can be used to pick out a few representative data from an infinite number of data for testing
2. boundary value method
Wherever there can be used the data input, and the equivalence partitioning method often used together to form a complete testing method; found valid data and invalid data boundary point, boundary point and the point on both sides of the tested individually
3. cause and effect diagram method
In one interface has a plurality of controls, there is a certain relationship between a combination of limits and control relationships, different input combinations produces different output results, in order to clarify the corresponding relationship between the combination of input and output, cause selection method of FIG.
4. The method determination table
And FIG cause determination table is essentially a method, composition control is to solve the problem, a simplified method is a cause determination table of FIG Method
The orthogonal arrangement method
6. scenes Law
7. Test outline law
A reference when writing use cases?
1. Requirements Document (document if you can develop the best reference)
2. Control procedures have been developed
3. and demand, developers, users communicate
Test Ideas?
Exhaustive testing is the most complete testing methods, but because of the high cost of time, the actual work should not be used.
Therefore, to ensure quality, while using a minimum of data to complete the testing process.
What is a valid equivalence class?
Meaningful specification description of the program, a reasonable set of data, the program receives a valid equivalence class data should be calculated correctly performed
What is invalid equivalence class?
Program specifications meaningless, unreasonable collection of data, the program received an invalid equivalence class data, you should give an error message, or simply not allowed to enter
Invalid equivalence class main factors to consider?
1. demand requirements can not be empty or required, invalid equivalence class is empty
2. The data has a range of requirements, invalid equivalence class is out of range
3. The number of characters have claim invalid equivalence class is beyond the prescribed range
4. Data type style formatted request is invalid equivalence class test pattern format. Type illegal
There needs 5 decimal places claim invalid equivalence class is reserved bits exceeds the range
6. demand requirements can not be repeated, it is to repeat invalid equivalence class
A basic feature of good software?
1. To achieve the required functionality
2. With strong exception handling capabilities (robustness)
V model and the advantages and disadvantages
advantage:
1. The testing phase is clearly defined
2. The correspondence between the developed and clear
3. The bottom of the test contains both (Unit Test) further comprises a user-level test (acceptance)
Disadvantages:
1. easy to understand software testing it is to be involved in the development after completion
2. The test does not reflect the work early (write a plan, for example, test document using), does not comply with the principles of the earlier tests and continuous testing
In-depth understanding of:
1. demand, the development of test documentation
2. the preparation of test plans, test cases and other documentation in accordance with the development, use cases perform the most prepared