A tasty slice of cucumber
•Télécharger en tant que PPTX, PDF•
0 j'aime•181 vues
Cucumber is a tasty and healthy snack that provides hydration and nutrients. While testing is important, the primary role of testers is not just executing tests but also improving quality. A company's culture can have a big influence on its approach to quality assurance practices.
Recommandé
Contenu connexe
Dernier
Dernier (20)
En vedette
En vedette (20)
A tasty slice of cucumber
- 1. A Tasty Slice of Cucumber Summary of Cuke-Up Australia Michele Cross – QA Manager, Sandstone Technology
- 4. THE JOB OF A TESTER IS NOT TO EXECUTE TESTS
- 11. ME
Notes de l'éditeur
- Cuke-up AU – first cucumber conference in Australia Cucumber is essentially an automated testing tool that allows you to create executable specifications from your acceptance criteria. The foundation of cucumber is behaviour driven development (BDD) and collaboration, and this was the main topic of the conference (not the tool)
- John Ferguson-Smart’s diagrammatic overview of BDD. BA + Developer + Tester = “3 Amigos” Essence of BDD - Collaboration Examples at multiple levels Common language to build a shared understanding To deliver software that matters
- Sharon Robson (day 1 Keynote) - Building Quality Into the Process, not the Product “Start with the end in mind” Part of building quality in, not bolting it on – Everyone tests. Everyone learns how to do exploratory testing. At which point someone said – I’m a tester, where does that leave me??
- The job of a tester is to think!! “The job of testers in a team is to design the tests.” “Testers are the map-makers who guide the others to find defects.”
- Matt Wynne – use example mapping as a collaborative tool to drive out rules, examples and questions in your “three amigos huddle” Keeps the focus on business goals not on acceptance criteria syntax - “on their own, Given/When/Then do not make good Acceptance Criteria” “Examples start conversations, rules close them”
- Anne-Marie Charrett – Keynote day 2 “when your testing is in a pickle” Use critical thinking skills – what are the key variables? How are we choosing test data. What are the most useful scenarios – “give me an example...” Where do we look for output – not just the GUI, how about log files, databases... What’s the business impact of a story? Is it useful to automate it – will it take a lot of effort to maintain, is it worth the effort?
- Learning mindset - “Challenge assumptions – be brave!!” Ask if you don’t know Paul’s topic in linkedin If you’re a manager - Encourage experimentation Allow testers to try new things Room to inquire, foster & nurture curiosity Encourage learning & give time for that opportunity
- Prescott Pickle Principle – “Cucumbers get more pickled than brine gets cucumbered” – ie the inertia of the status quo will tend to reassert itself and take over (be very afraid)
- Hamish Tedeschi – how to separate BDD from testing Testing Sandwich Context-driven, JavaScript has so much logic in the UI that has to be automated Exploratory testing can occur at every level – eg when writing code as you think about what you’re testing and what you need to test – “exploratory etsting as design”
- Alister Scott – Do’s and Don’ts of Automated Acceptance testing Large unwieldy test suites are like driving a containership into work – too big, too slow, too expensive. Differentiate between acceptance and end to end tests. Write the tests so they are independent Automate just enough to eliminate manual regression testing – you will still need manual/exploratory testing!
- Sharon Robson’s photo :P