- Create a form and publish it.
- Navigate to the configure tab and click on Access control card.
- Select the option
Secure with password
and enter a password. - Open the form in a new window without the user session related cookies of the logged in user and verify the form is password protected.
- Submit the form and verify the response.
As we have completed the book, it is now time to gain hands-on experience with a real-world application. For this, we can use neetoForm.
Apart from just automating the tests, ensure that you adhere to all the best practices and concepts mentioned in this book. Additionally, you can refer to the official Playwright documentation for advanced topics. Also, do not forget to perform a proper cleanup after performing each test to maintain a clean and consistent test environment, which is shared by everyone performing this task.
- Click on add new form.
- Create a form from scratch.
- Add full name, phone numer fields to the form.
Though Playwright offers a variety of built-in reporters for test result visualization, sometimes you may need a custom solution tailored to your specific project requirements. Thankfully, Playwright allows you to build your own custom test reporter from scratch. In this blog post, we'll dive into the process of creating a custom reporter that perfectly suits your needs.
Before diving deep into how to build custom reporters, we need to first understand the hierarchy in which the test cases are arranged. The diagram below gives a pictorial reresentation of the hierearchy of the suites.
- Root Suite: The top-level suite in the hierarchy represents the entire test suite for the projects. It serves as the root node from which all other suites branch.
- Project Suites: Under the root suite, there is a project suite for each TestProject. A TestProject is a logical gr