How to write UI tests from A to Z

Please download to get full document.

View again

of 14
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Similar Documents
Information Report
Category:

Software

Published:

Views: 0 | Pages: 14

Extension: PDF | Download: 0

Share
Description
I am gonna show how to write UI tests from scratch, from A to Z. It’s gonna be a live demo, no slides, just hardcode. I would like to cover all aspects writing UI tests, including: infrastructure set up, test data management, complex code coverage, testing strategy, role of UI tests in automation, etc. Technologies: Java, Spring Boot, React, Selenide, Docker, Docker Compose, TestContainers, Jenkins. In overall, it would be just another story. Everyone will be able to take the code away. If you need to get an example how to start writing UI tests this talk would be way useful.
Transcript
  • 1. HOW TO WRITE UI TESTS FROM A TO Z EXPECTED JOURNEY BY IGOR DMITRIEV
  • 2. AABOUT ME • Igor Dmitriev • 6+ years experience • Engineering Manager at SPD- Ukraine • Took part as a speaker at JUG.UA, Rockstar Night, Java Day, JEE Conf conferences Contacts: igor-dmitriev-3a29b15 Id=100012270886051 ihor_dmitriiev
  • 3. IDEA • Let’s test Wikipedia? • Full aspects of writing UI tests • How to write UI tests from the beginning • Show me the code • Take away example project
  • 4. MOTIVATION • No QA engineers • Acceptance testing • Continuous Delivery • Regression • Better Quality Gate – less stressful environment
  • 5. AGENDA • How to start • Frameworks • First UI test • Continuous Integration • Code coverage • Reporting • UI tests enhancements
  • 6. TESTING PYRAMID • Unit > Integration > UI • Acceptance testing • UI tests to cover the most important part of an application
  • 7. TOOLS • Selenium • JDI • Cypress • Selenoid • Serenity • Geb • Selenide • Cucumber • Nightwatch
  • 8. CI INFRASTRUCTURE • Run UI tests on CI server • Ability to run tests locally from IDEA
  • 9. CODE COVERAGE • Complex test coverage • Additional coverage of Facade services, mappers, code without business logic
  • 10. TO BE CONTINUED
  • 11. TEST DATA MANAGEMENT • Each test should have its own isolated test data • UI vs API vs DB Николай Алименков. How to mange your test data for successful test automation. QA Fest 2018 - https://www.youtube.com/watch?v=E21AxgHX 2B0&index=65&list=PLNOubBZDFnvaRtUS- aGCep6yXfwSGu6RL
  • 12. ADVICE • Prefer unit/integration tests to UI tests • New bug – new UI unit test • Demo your UI first • Cover only the most important parts, from business perspective, of your app (“happy path”) • Tests must be independent
  • 13. https://github.com/igor-dmitriev/spring- petclinic-reactjs-ui-tests
  • 14. THANK YOU QUESTIONS?
  • Recommended
    View more...
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks
    SAVE OUR EARTH

    We need your sign to support Project to invent "SMART AND CONTROLLABLE REFLECTIVE BALLOONS" to cover the Sun and Save Our Earth.

    More details...

    Sign Now!

    We are very appreciated for your Prompt Action!

    x