The first chapter of software testing background
Software defects
1, in this book, all software problems are referred to defect .
2, product description : the definition of the product development. Details given product, how to do, what to do, what not to do.
3, meet the following minimum one of five rules did occur, said a software defect.
(1) the software does not implement the functions required by the product specification.
(2) An error has occurred Software product manual specifies should not be there.
(3) the software product features not mentioned in the specification.
(4) Unrealized software product specifications but not explicitly mentioned objectives should be achieved.
(5) software difficult to understand, easy to use, run slowly.
(3) Article: Multi-function increase Although there has been better, but will increase the work test, and even bring more defects.
4, leading to software defects biggest reason is the product manual.
Software defects second largest source is the design.
5, the cost of repairing software defects is increasing over time. Exponentially.
6, the software testers goal is to find software defects as early as possible, and to ensure that it can be repaired.
Repair the defect does not mean we must correct software. It may mean an increase in the user manual a comment or to provide users with special training.
7. great software testers should possess the following qualities:
They are the group of explorers.
They are troubleshooting member.
They did not miss any clues.
They have creativity.
They are the group's pursuit of perfection.
They judge accurately.
They focus on strategy and diplomacy.
They persuasive.
In addition to these qualities, educated in software programming is also very important. Learn how to write software, you can find software defects from different angles, making testing more efficient and contribute to the development of testing tools.
The second chapter of the software development process
Part of the product
1, in the software industry, is used to describe manufactured and delivered terms other people's software product components are part of the deliverable. The easiest way to explain all deliverables are part of different categories.
2, writing software purpose is to meet the needs of some people, these people called the client.
3, to get direct feedback from potential customers software products in popular approach is to help people focus. Focus groups are usually located in commercial establishments by the office of an independent survey company to organize.
4, product brochures.
5, a key part of the software product is the schedule. The purpose is to understand what work is completed, there is still much work to be done, when completed.
6, software design documentation: For a slightly larger program, there must be a design process to plan how to write software.
7, common software design document list:
Structure of the document. Describes the overall design of the software documentation.
Data flow diagram. A schematic view showing how the normal data flow in the program. Also known as bubble chart, circles and lines drawn.
State transition diagram. The software is divided into the basic state or another condition regular schematic representation of different state transitions.
flow chart. Conventional manner with a graphical depiction of program logic.
Code comments.
8, test documentation.
Submit a list of the more important test:
Test Plan. Description is used to verify whether the software product specifications and consistent with the overall program customer demand.
Test case. Listed test project, described in detail the steps the software.
Defect report. Describes the implementation of test cases identified.
Testing tools and automated testing. If the test team used automated testing tools and test software, or whether it is prepared to buy their own tools, must be documented.
Metrics, and summary statistics. A summary of the testing process.
9, the error message is a software product the most overlooked part .
Software project members
The project manager from start to finish drives the entire project. Usually responsible for writing the product manual, schedule management, major decisions.
System Architect is the technical expert product team. Generally rich experience, we can do architecture or software design of the entire system.
Programmers design and write software to repair defects in the software.
Testers responsible for identifying and reporting software product problems.
Techniques for the preparation of software files and online documentation included with the product.
Configuration Administrator is responsible for combining the code written by the programmer and technical author wrote all the documentation, into one package.
Software development life cycle model
1, the software products from the initial idea to the public offering process is called software development life cycle model.
2, the four most common patterns:
The Big Bang model
while writing mode change
waterfall
spiral pattern
The Big Bang model
Together, the huge energy release a lot of things (human and financial) on the - often very brutal - had a great software product - or a pile of scrap.
Advantage of the big bang model is simplicity. Planning, scheduling, and almost no formal development process, all energy is spent on the development of software and write the code.
In most cases, the big bang model is almost no testing. If any, were crowded before product release.
Try to avoid testing in this mode.
While writing mode change
The project team developed the default mode when not deliberately use other development model. Explosion step closer ratio, at least consider the demand.
While writing mode for change is intended to quickly create and used to throw small projects.
Waterfall
Using waterfall project from the initial idea to the final product to go through a series of steps. At the end of each step, the project team organizational review. If the project is not ready, it slows down.
Waterfall great emphasis on the definition of the product.
The steps are separate, there is no cross.
I can not go back.
Pros: Everything has a complete and detailed description of the test object is very clear.
Cons: Only in the last test performed, so some of the fundamental problems that may arise in the early days, until ready to release products when possible discovery.
Spiral pattern
The overall idea is to start having to define in detail all the details. Start early, the definition of important functions, efforts to achieve these functions, accept customer feedback, and then proceed to the next stage. Repeat the process until the final product.
Spiral test contains a little waterfall (step analysis, design, development, and testing), little changed while writing mode (spiral test each) and a bit of the Big Bang model (viewed from outside).
This mode identify problems early, low cost.
PS: There is a development process called agile software development. Failed to mainstream, off-topic easy to create confusion.
