Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Wisdom is the bug killer

1.390 Aufrufe

Veröffentlicht am

My presentation for CodeCamp, Iasi, 7 November 2015

Veröffentlicht in: Software
  • Loggen Sie sich ein, um Kommentare anzuzeigen.

Wisdom is the bug killer

  1. 1. Wisdom is the bug killer
  2. 2. About me: • @andreea_popescu on Twitter • full-time QA Engineer at • photography lover
  3. 3. 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!
  4. 4. 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).
  5. 5. … 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.
  6. 6. – David Tzemach “Every assumption should be tested and approved before you can put the “Approval” signature.”
  7. 7. 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.
  8. 8. 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.
  9. 9. 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.
  10. 10. 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);
  11. 11. • define a scenario (or multiple scenarios)
  12. 12. All steps used on scenarios need to be written on features/bootstrap/FeatureContext.php
  13. 13. Q & A?
  14. 14. Resources • http://docs.behat.org/en/v2.5/ • http://simply-the-test.blogspot.ro