what software testing tools

Time flies, from graduation to now has been 10 years, 10 years has been engaged in the work of software testing. From a nothing, to test technicians to test management, during the confusion, there is pain, there are detours, there are shortcuts. Today on their own past 10 Test experience to do a summary, one is to give yourself a fresh start to increase motivation, the second is to just humanely, confused t

software. What is closely related to the software also requires our software testers to test the software. For example, the product manual is very important. It involves issues such as the customer experience when your software i

(Zhu shaomin is copyrighted? 2014: Indicate the real source for any reference and forwarding) Is there always a starting point for software testing? Where can I start analysis? What is the test design based on? Simply put, what drives the test work? This is a basic problem. Based on my years of understanding of

Kaner has a set of bbst courses for black box testing. Can be found online... A full range of English lecture videos and supporting reading materials are provided. It is suitable for three months of black box testing. Black box testing is the basic skill of All testers later. It is not necessary to study after graduation, but it is too easy to learn. His core id

First, the software testing the basic article Introduction to Software Quality testing basics Software quality and software testing 0

further refined in later versions.In some cases, even if the developer has found a flaw and did not improve the repair, on the one hand may be limited development time can only be enhanced in subsequent releases, or because some defects do not affect the normal use of the software, so can be a small ignore.PS: Software defects and software vulnerabilities can be

institutions and think that they can step into the Hall of test experts after several days of capacity improvement. This is wrong, it is also a big loss. Another mistake is that, without learning the basic concepts of testing, I blindly learned a variety of large commercial automated testing software. The results took a lot of time and money, but I learned the s

1. IntroductionDesigning test inputs and corresponding expected outputs is one of the most basic technical activities of any testing organization. Both the test input data and the corresponding expected output are written to the test case. A collection of test cases is a test set. Currently, a number of guidelines, techniques, and support tools exist to generate test cases. The next step is to introduce a l

. Improving code quality means saving timeSome research shows that more than 80% of software development time is used in the following aspects:. debug your own code (UnitTesting). debug yourself and other related code (Inter-Module Testing). debug the entire system (System Testing) worseIt may take 10-times for you to find a bug, which may be easy at the beginnin

development.Agile TestingIsn't that the agile test? How does it look like the test is not a dime of agility? People are agile, but also to test what to do?In the agile development process, testing is no longer a part of the Waterfall trial development process, but is involved throughout the entire development process.In a variety of ways to ensure the quality of the product, whether the principle of "frequ

effectively test the increasingly complex embedded software. Just like the tools needed for car repair, good programmers should be able to use various software tools skillfully. Different tools have different application scopes and functions. With these

; "alt=" bb40472fefda4440a3c2bd1071a09058_th.jpg "/>Experience and lessons of software testing　　A good software testing team is not born, but created, through a lot of hard work and effective communication created. In this process, there are many pitfalls that can skew a well-crafted plan so that the project cannot be

normal queue is a defect that needs to be queued for repair, and low priority means that the defect can be corrected when the developer has time. Correctly assessing and distinguishing the severity and priority of software defects is a major event for testers and developers, as well as for all project team members. This is not only to ensure the smooth test of the requirements, but also to ensure the quality of s