The rest of the subject is fully covered in Software System Testing and Quality Assurance (BEIZ84).Every chapter has testability guidelines that illustrate how the technique discussed in the chapter can be used to make software more easily tested and therefore more reliable and maintainable Preface to the Second Edition I started to write the first edition of Software Testing Techniques in 1978.It was published in 1983, but most of the references predated 1980: the first edition was a book for the 80s that reported on the state of software testing as of the late 70s.
![]() Software Testing Techniques By Boris Beizer Ppt To Manual Process ToThe years between have been a decade of intensive research and development in software testing as an art and science; a decade in which the vocabulary of testing evolved from idiosyncratic usages into an accepted set of concepts and terms for those concepts; a decade that saw intensive research on the relative strength of different testing techniques; a decade in which testing emerged as a discipline in its own right; a decade that began with evangelism for proper testing and ended with widely accepted testing norms; a decade that saw testing change from a mostly manual process to an intensely automated process; the decade in which PCs and workstations became ubiquitous personal data management, programming, and test tools. Software Testing Techniques By Boris Beizer Ppt To Update The TechnicalA new edition was needed to update the technical material, but also for other reasons: software testing and quality assurance evangelism is no longer needed; theres less about which to be iconoclastic; some of the hot ideas of the 70s have passed into obscurity while formerly obscure concepts have come to the fore; testers have emerged as skilled professionals along with programmers and system analysts. Most important of all, many professional testers who began the decade as the whipping boys of software developers are ending it with the roles reversed. The final reasons for a new edition is the shift in audience. Although I wrote the first edition for all programmers (because testers as such hardly existed), Software Testing Techniques became one of the standard reference books on the professional testers shelf. A new edition was needed to shift the focus from a book for programmers (and testers) to a balanced book for testers and programmers. The most obvious change was the removal of Chapter 8DataBase-Driven Test Design. Its remnants are now in Chapter 6Domain Testing, Chapter 13Implementation, and scattered elsewhere. I removed material that the reader can find, better said, in Software System Testing and Quality Assurance (BEIZ84). The material based on a manual test development process, unaided by workstations and PCs, had a quaint ring to itso that went. I also removed other process material that Ive subsequently learned must be taken for granted if theres to be testing worth the doingdata dictionaries, to name one. Finally, I wanted to sharpen the focus of this book even more toward techniques and farther away from process because process is too big and too important to treat superficially. It is covered more thoroughly in BEIZ84, and there are many other sources for process information, which was not the case when I wrote the first edition. As for additions, the biggest changes reflect the rapid development of automated aids to programming and testing. Advanced testing techniques are processing-intensive and cant be applied without tools. The first edition did not meet the needs of test tool builders or users. The final major addition is the section on testability tips in most chapters. Weve gone full circle, back to putting the primary responsibility for software quality on the programmer. This approach requires that all test techniques be interpreted in the light of design for testability. Software testing and quality assurance can be looked at from three points of view: (1) our tools and techniques, (2) what we are testing, (3) and the process by which testing is done and quality is assured. What we test can likewise be divided into three domains: components (units), integration, and systems. Component testing is also covered in this book because most techniques are most easily applied to components.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |