What are fixtures? How can I create one? How can I use it? I will answer all this questions with a small but explanatory live code example.
This talk has been presented at TestJS Summit 2023, check out the latest edition of this JavaScript Conference.
A fixture in Playwright is a small environment containing methods and settings that are defined by the user. It can be compared to small balls inside a ball pit, where Playwright is the ball pit and the fixtures are the balls.
Fixtures are used in Playwright to control and manage the testing environment. They allow users to define reusable methods and settings, making the tests more readable and maintainable.
Examples of fixtures in Playwright include the page fixture and the context browser fixture. These fixtures are predefined, but users can also create their own custom fixtures.
To create a custom fixture in Playwright, you need to define a function that tells Playwright to add your fixture. This function should include a before block, the test itself, and an after block.
The before block in a Playwright fixture is used to set up the necessary environment and conditions before the test runs. It ensures that everything is in place for the test to execute correctly.
Custom fixtures improve test reusability by allowing you to define reusable methods and settings. This means you can use the same fixture for multiple tests without having to rewrite the setup each time.
Using page objects in Playwright tests makes the tests more readable and maintainable. Page objects encapsulate the methods and actions that can be performed on a page, making the test code cleaner and easier to understand.
To integrate custom methods into a Playwright fixture, you need to define these methods in a page object and then create a fixture that includes these methods. This fixture can then be imported and used in your tests.
The after block in a Playwright fixture is used to perform any cleanup actions needed after the test has run. This can include logging information or resetting the environment.
Control is important because it allows you to decide which methods and settings are used in your tests. This leads to a more manageable and predictable testing environment, enhancing both test reliability and reusability.
Hello, everyone. I am Lia, the gatekeeper of the application's quality. My goal is to help you understand fixtures and how to create your own. Fixtures are like small environments in Playwright, where you define methods and stuff. Playwright gives us the opportunity to create our own fixtures, providing control over the testing process.
Hello, everyone. I am Lia. I hope you are having fun today. My job description at Bleep is quality assurance engineer, but I like to describe myself as the gatekeeper of the application's quality. My goal here is, at the end of this seven minutes more or less, you get a better understanding of what is a fixture and how you can create your own.
So let's start from the beginning. What is a fixture? Well, I like to describe fixtures in Playwright just like a little small environment where exists methods and stuff that I defined. I use these analogies like, imagine a ball pit where Playwright is the ball pit and fixtures are the small balls that are inside of the ball pit.
And why? Why do you use fixtures? So Playwright is fixture based. Everything that we use in Playwright is a fixture. Page is a fixture. Context browser is a fixture. And as I said previous, Playwright gives us the opportunity to create our own. And you can ask, okay, if Playwright gives us the opportunity, sorry, if Playwright gives us the fixture already, why do I need to create my own? Well, the answer is control. But okay, this is not working. Of course we need to have problems. Okay, control. Okay. Control of what? Well, let's see a little example.
To make the test more readable and reusable, I pass it to a page object with my own methods. By creating a fixture, I can make these methods available for use. The fixture structure consists of a before block, the test, and an after block. Instead of importing test and using page, I import and use my fixture on the test. This allows me to access the methods I created in the page object, making the code more readable and reusable. Playwright fixtures provide control over the methods used in the fixture, creating a small and controllable environment.
So this is a test that I created, and you can see that it's using the page fixture. I'm importing test from Playwright. I have a before it. I am checking for some titles and filling some forms. But this is not really reusable and you cannot really understand if you don't have the context of the application, what is being done here.
So how can I create this more easy to read and more reusable for everyone that needs to add tests to use it? So the answer is, I'm going to pass this to a page object that has my own methods. And you can see here that I have getTitle, clickButtons, fillForms. So this is my methods, my page objects, but this only by itself does not make them available on the page fixture.
So what I need to do to make them available to use is, well, create a fixture. So the structure here is, I need to have a function that is going to say to Playwright, add my fixture to the land of the feature. So test is the land of the features and I'm going to extend my own features. And in my fixture definition, there is going to be my test. You can use other fixtures like a fixture section to do stuff, but the main stuff here is the structure. So the structure for the fixture is going to be the before block, the test, and then the after block. So what I'm doing here is, if you look at the previous, the initial test, I have a before hook and comparing to my fixture, the same before hook is there. Then I'm going to use my methods in the initial page and after the run, I'm going to console.log something.
So how can I use this in my test? So instead of importing test, instead of using page, now what I'm going to do is import my fixture and use my fixture on the test and import my test that is the actual fixture. And as you can see there, it has access to my methods that I created in the page object. It's a little more readable and it's very reusable because if I want to have, let's say, another 10 tests that go through this, you can just reuse it instead of just having to recode everything. So the control that PlayWrite Fixtures gives us is I can decide what methods do I need to use or what I want to use in my fixture. I have a really small environment that is very controllable and very reusable. So, I hope that this gives you a little bit more of insight on fixtures and how you can use it in your tests. And that's it guys.
We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career
DevOps.js Conf 2024
TestJS Summit 2021
TestJS Summit 2022
TestJS Summit 2021
TestJS Summit 2022
DevOps.js Conf 2022
TestJS Summit 2021TestJS Summit 2022TestJS Summit 2021
GraphQL Galaxy 2021
Comments