Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

How to Write UI Automated Tests

Report lightens up the starting points and the basics of what you need to know in order to get going with writing automated UI tests. Here Elena is touching upon the common automation stack of tools, the possible architecture of the test project and share the tips based on her personal experience.
You can watch the practical example of a test creation and the talk could help you gain understanding of the main principles of tests writing and PageObject pattern usage.

  • Inicia sesión para ver los comentarios

How to Write UI Automated Tests

  1. 1. HOW to write UI automated tests
  2. 2. SHALL TALK ABOUT: Stages of test development Reviewing the Tools: basic stack and setting up the environment How to build your tests project architecture How to write your first test Using PageObject design pattern Let’s summarize
  3. 3. STAGES OF TEST DEVELOPMENT: Creating Debugging Failure analysis Stabilization Modification
  4. 4. Continuous Integration Server Jenkins, TeamCity, CruiseControl, Bamboo Repository: Git Builder Maven, Gradle, Ant, NAnt, Rake, MSBuild Programming language: Java, Python, Ruby, JavaScript... Framework Protractor, Jasmine for JS; JUnit, TestNG for Java; NUnit, Gallio for .Net; RSpec, Cucumber for Ruby IDE: Webstorm, PhpStorm, Intellij IDEA, PyCharm, Notepad++ (: Tests (code) Driver of the testing system WebDriver, TestComplete, QuickTest Pro Browser FF, Chrome, IE… Application AUTOMATION STACK
  5. 5. Continuous Integration Server Jenkins Repository: Git Builder Programming language: JavaScript Framework Protractor, Jasmine IDE: Webstorm Tests (code) Driver of the testing system WebDriver Browser FF, Chrome, IE… Application TOOLS THAT I USE
  6. 6. CODE ARCHITECTURE helpers (your improved methods) MY_TESTS (this is root) pages (your pageObjects) spec (your tests) target (folder for storing generated reports) package.json config.js
  7. 7. FINALLY Fragments reuse Separation of aspects (architecture) Design patterns usage Make clear titles Comments and other documentation Refactoring tests ➔ Data separated from logic ➔ Configuration separated from logic ➔ Code divided into layers: initialisation allocated / exposure and checks allocated If you have WebDriver APIs in your test methods, You're Doing It Wrong. Simon Stewart