wisdom is the bug killer
TRANSCRIPT
I will talk about: • First: be the user
• … second: be the QA
• The “hot” parts of the app
• Manual or and automated testing
• Behat speaks Human!
First: be the user
• forget about ISTQB glossary and software testing theory and start being an user;
• see if you are able to understand the app (not thinking from the QA’s point of view);
• recognize some patterns or not (e.g. the red color used for delete).
… second: be the QA• start testing “by the book”;
• create a test plan for the app working on different environments (e.g. operating systems, browsers, devices);
• prioritize the test cases and, first, deal with the most important features;
• you’re not just the “QA” or “software tester”, you are the person who can come with new suggestions and improvements.
– David Tzemach
“Every assumption should be tested and approved before you can put the “Approval”
signature.”
The “hot” parts of the app
• the one of the most important things: the users have no time for navigating on Websites or apps;
• the app needs to be intuitive and have elements easy to access;
• the whole app needs to be centered on the user’s needs.
Manual or and automated testing
• don’t blame manual testing and, of course, don’t blame automated testing;
• an equilibrium is needed;
• manual testing is for understanding the user;
• automated testing is for keeping an eye on the software product.
Behat speaks Human!• Omnia: “Because I don't speak Human you can't
understand a word I'm saying…” - a lot of frameworks work like this.
• Behat: Open Source behaviour-driven framework for PHP 5.3 and 5.4.
• You write human-readable sentences that describe a feature of your application and how it should work.
Basic human Behat structure:
• define your feature (e.g. the API method name);
• define a background (e.g. the log in details for an user, if the user need to be logged in for all feature scenarios);
Resources
• http://docs.behat.org/en/v2.5/
• http://simply-the-test.blogspot.ro