The software testing and quality assurance is a wide area and I'll try to provide the best guidelines for understanding these processes, but you can also help me to understand what type of guidelines you need.
I'll try to cover in my next posts and to provide useful information about:
- fundamental test processes (test planning and control, test analysis, test design, test implementation, test execution, exit criteria, reporting)
- software development models (V-model, testing within a life cycle model)
- test levels (component testing, integration testing, system and acceptance)
- test types (functional and non-functional testing, structural, confirmation, regression testing)
- test techniques (black box technique: equivalence partitioning, boundary value decision table testing, state transition; white box techniques: statement testing and coverage, decision testing and coverage; exploratory testing)
- test planning and estimation (test planning, exit criteria, test estimation, test strategies) and test progress monitoring and control
- determinng the project risks, product risks
- test tools and which is the best choice for specific application areas
- support information (recommended books, standards, courses)
- software testing tips & tricks
- glossary of terms
- and more
So please add your comments in this post and specify what areas of software testing and quality assurance you want to discuss here.
This book constitutes the refereed proceedings of the 16th IFIP TC6/WG6.1 International Conference on Testing of Communicating Systems, TestCom 2004, held in Oxford, UK in March 2004. The 14 revised full papers presented were carefully reviewed and selected for inclusion in the book. All Current issues in testing communications system are addressed, ranging from classical telecommunications issues to the testing of reactive systems and testing from UML.