Context-Driven Testing | Glossary

Definition:

Context-driven testing is a model for developing, debugging a software in a specific context where the programs will be used or expected to be used in the real world. Developers identify the intended market and evaluate the environments in which people are likely to employ the product. It is fact that users are humans with preferences, needs, abilities and limitations and programs that works well for a person may not be same for other as the context may be different.

Context-driven testing enhances user-friendliness of the end product, where functionalities are optimised for intended users as well as looking at adaptability of the product based on changing markets and social values. Context-driven school of software testing advocates continuous and creative evaluation of testing opportunities in the light of the potential information revealed and the value of that information in that particular context. It advocates testing in a way that conforms to the context of the project, as opposed to testing as opposed to testing in a way that follows some fixed notion of “best practice”. Context-driven testing could arguably be called agile testing because the principles it recommends are analogous to those suggested in the Agile Manifesto.

Further Reading:

Book: AGILE TESTING A Practical Guide for Testers and Agile Teams
http://wiki.c2.com/?ContextDrivenTesting

Process Miniature | Glossary

Definition:

Process Miniature is a technique where new development process proposed is experienced by the team by running the entire process in a very short period of time. Alistair Cockburn uses this term as one of his favorite way of conveying the methodology where the participants play-act one or two releases of the process in a very short period of time.

Peter Merel invented a one-hour process miniature “Extreme Hour” where Extreme Programming(XP) is demonstrated using a sample project and involving the audience. Here audience gets one hour to completely develop and test a product using XP principles such as Pair Programming.

Few more examples for Process miniature are ExtremeTeaching, Code Sprint.

Further Reading:

Book: Agile Software Development  by Alistair Cockburn
http://wiki.c2.com/?ProcessMiniature
http://wiki.c2.com/?ExtremeHour
http://wiki.c2.com/?ExtremeTeaching
http://wiki.c2.com/?CodeSprint