Gain insights into effective test strategies using Postman and WebdriverIO. Explore test planning, execute test cases, and master automated testing for web and mobile applications.

Testing react applications with Postman and WebdriverIO-01.png

nodeEnv.tar.gz

testing-units palindrome

testing-inputs application RTL tests

testing-api-endpoints

testing-e2e

testing-e2e UAT

testing-units vowels exercise intro

testing-units vowels exercise solution

postman

next-example-app

testing-e2e-webdriver-sample

testing-e2e-webdriver-selectors-app

testing-e2e-webdriver-testing-library & POM

Login Application

WorkOrderManager Challenge - WDIO

Login Application Manual Exercise

In today’s digital world, test engineers must have effective and efficient strategies and skills to test software in fast-paced agile environments. The Postman tool for API testing is a well-known tool to build, test, and publish APIs, as it allows you to execute ad hoc testing and fully automated test suites. WebdriverIO is a modern JavaScript testing framework for browser and mobile automated testing. 

You will begin with the basics of old and new approaches to building and testing software. Then, you will learn about test planning and design strategies that help a test engineer to select the best approaches to executing test cases for any application. Next, you’ll cover how to test an application using Postman from the end user’s perspective. You’ll finish the course by testing a work order manager with Postman and WebdriverIO.

By the end of this course, you’ll gain essential skills to succeed and advance in a career in test engineering or other roles applying testing activities.

Testing React Applications with Postman and WebdriverIO

# What is E2E testing?
**End-to-end (E2E) testing**, also known as UI testing, tests system workflows from the end user’s perspective. We test all the system components to see if they are working correctly. The primary aim of E2E testing is to ensure that the entire system is functioning correctly. Typically, testers who are familiar with the system write E2E tests. E2E tests generally are slower than unit and API tests because they test the entire system. They are also more prone to flakiness. Flaky tests randomly fail even though there was no code change.


In a real-life situation, let’s say we want to test the E2E workflow of completing a feedback form for a health-care application. The user would navigate to the home page, click the link to the feedback page, fill out the form, and submit it. After submitting the form, they should see a message thanking them for their feedback. We can view the workflow in the browser.


Execute the application below and click the provided Educative URL to view it in a browser.


Learn about the details of end-to-end testing.


End-To-End Testing

Learn about the details of end-to-end testing.

Course Overview

Understanding Modern Testing Practices

Understanding the Test Pyramid

Next.js and the Example Application

Testing Endpoints with Postman

Testing the UI Workflow with WebdriverIO

Test a Work Order Manager with Postman

Test a Work Order Manager with WebdriverIO

Conclusion

Appendix

End-To-End Testing

What is E2E testing?