Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Testing for the Thinking Tester
Transcript of Testing for the Thinking Tester
Testing for the thinking tester.
The principles of Context Driven Testing are...
The value of any practice depends on its context.
There are good practices in context, but there are no best practices.
People, working together, are the most important part of any project’s context.
Projects unfold over time in ways that are often not predictable.
The product is a solution. If the problem isn’t solved, the product doesn’t work.
Good software testing is a challenging intellectual process.
Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.
Heuristic Test Strategy Model
What exploratory testing is:
An approach to software testing (applicable to any testing technique)...
...that emphasises the personal freedom and responsibility of each tester to continually optimise the value of their work...
...by treating LEARNING, TEST DESIGN and TEST EXECUTION as mutually supportive activities that run in parallel throughout the project
What exploratory testing isn't:
Unstructured, random clicking, "playing around"
Is one way that we can approach testing
A way of thinking about what and how you're testing
Providing a new set of information
Hopefully we've gotten you thinking...
More in depth training coming up
Yammer group with resources and discussion
We're always keen to discuss and support.
Context Driven Testing is a mindset, a way of approaching the way that we test, which is different from traditional or "factory method" testing. We believe it is a way in which Assurity can provide better testing and differentiate ourselves from our competitors by testing smarter, faster and cheaper.
What is CDT?
Taking testing to the next level...
Most testing in New Zealand is "factory-method"
Has created the perception that testing is "easy" or that anyone can do it
We believe that testing is more specialised than many clients and even testers realise
Our mission is to encourage specialist testing within Assurity
Context Driven Testing
So what is testing?
That's open for discussion...
ISTQB says testing is:
The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
A practical definition
Context-driven testing is an approach to testing that has been growing rapidly in the past few years. The context-driven tester is an active thinker, one who values personal skill development and rapid testing over producing boilerplate documents that nobody ever reads, or follows. In short, context-driven testing is about finding the best possible solution for each unique testing problem, and then implementing that solution in an effective and cost-efficient manner, with minimum waste. The context-driven challenge is to continuously re-evaluate and re-optimize testing to best fit the needs of the business and to get testing done as quickly as possible while still assuring that everything gets done that needs to be.
Context-driven testing aims to give testers the tools they need to solve testing problems in any situation.
"Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test."
- Cem Kaner
“Testing is ‘questioning’ a product in order to ‘evaluate’ it”
- James Bach
Software testing is the process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs) and to evaluate the features of the software item "
Testing is a process of gathering information by making observations and comparing them to expectations.
- Dale Emery and
There are others though...