Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Automating Pragmatically - Testival 20190604

319 vues

Publié le

# Automating Pragmatically

Testival Meetup 20190604

## Alan Richardson

- EvilTester.com
- @EvilTester
- compendiumdev.co.uk
- digitalonlinetactics.com

---

~~~~~~~~
Title: Automating Pragmatically

The online discussions of automating can leave me confused.

- Should you automate through the GUI?
- Should GUI automating be banned?
- Do all testers need to code? Is automating part of testing
or not?
- Do we need to automate to get a job?

In this short session Alan will discuss automating
from a pragmatic and contextual position and
share how he thinks about automating.

~~~~~~~~

Publié dans : Logiciels
  • Soyez le premier à commenter

Automating Pragmatically - Testival 20190604

  1. 1. Automating Pragmatically Testival Meetup 20190604 Alan Richardson EvilTester.com @EvilTester compendiumdev.co.uk digitalonlinetactics.com @EvilTester 1
  2. 2. Title: Automating Pragmatically The online discussions of automating can leave me confused. ‑ Should you automate through the GUI? ‑ Should GUI automating be banned? ‑ Do all testers need to code? Is automating part of testing   or not? ‑ Do we need to automate to get a job? In this short session Alan will discuss automating from a pragmatic and contextual position and share how he thinks about automating. We will leave time for questions, and Alan is happy to answer questions on any testing or development related topic. @EvilTester 2
  3. 3. Naming ‑ Test Automation we don't automate testing Automation in Testing Tools Support Testing vs Checking Use your own words. @EvilTester 3
  4. 4. Automation verb? noun? Automate, Automated, Automating Automatization Automator: Programmer, User of Tool Automaton: Script, Configured Tool @EvilTester 4
  5. 5. Why include "Test?" Test Strategy we identify aims Test Approach we identify things we can automate to support our aims Automating is a concept independent of testing. We Automate Stuff To Help Us Test. @EvilTester 5
  6. 6. Software Development Automation CI, CD, make, automated build dependency management code completion IDE, Static Analysis Compilers, Assemblers, Interpreters We automate throughout the Software Development process. @EvilTester 6
  7. 7. Use your own words I avoid saying "Test Automation" Automated Execution of Path X Assertions to cover acceptance criteria Choose specific phrases for the concept or point. @EvilTester 7
  8. 8. Who do you believe? Should you automate through the GUI? Should GUI automating be banned? BDD is not Testing @EvilTester 8
  9. 9. Believe no‑one look for absolutes identify "but..." evaluate approaches Build your own models. Believe your own experiences. @EvilTester 9
  10. 10. Future Skills Do all testers need to code? Is automating part of testing or not? Do we need to automate to get a job? @EvilTester 10
  11. 11. Does it matter? we work in teams what does your current environment need? what are you interested in? what are your constraints? time, money, skills, opportunities any related weak signals? AI, Security, Ops, Performance @EvilTester 11
  12. 12. Keep Learning Build the path that is appropriate for you Build on your strengths Don't ignore your weaknesses Be interested in Software Development as a whole. @EvilTester 12
  13. 13. A Model of Testing Comparing a thing to a model of a thing. Modelling Observation Reflection Interrogation Manipulation @EvilTester 13
  14. 14. Models of Automated Execution System as a Graph Paths through a System Data flows through paths Invariant Data Controls Paths Variant Data Partitions Abstracted @EvilTester 14
  15. 15. System as a Graph there are many executable models events, state, flow model based testing all testing is model based execution can be model driven @EvilTester 15
  16. 16. Paths through a System execution follows a path manually via test script exploratory objective automated code model traversal keywords declarative implementation (BDD) Flow abstraction. @EvilTester 16
  17. 17. Data Flows Through Paths Login (username, password), Create New User (username, email, role) Gives us: Data Driven Testing BDD example tables Certain paths require Invariant data (admin role) Equivalence Partitions (valid email, invalid email) @EvilTester 17
  18. 18. From Modelling, comes Coverage @EvilTester 18
  19. 19. Automate Tactically or Strategically Strategically long term, team agreed, maintained, specific tools Tactically short term, specific objective, single use/person, adhoc scripts @EvilTester 19
  20. 20. What will work for you? know your outcomes you can only automate what you know to be possible experiment tactically experience refactors to strategic implementation responsibility and ownership @EvilTester 20
  21. 21. About Alan Richardson EvilTester.com CompendiumDev.co.uk Talotics.com @EvilTester see above for books, youtube, online training, patreon, blog, etc. @EvilTester 21

×