Allow for customization of the BrowserContext

[edeandrea]

This would also open up a pattern to be able to further customize the BrowserContext, or other things within Playwright.

I initially tried to do it via properties (i.e. quarkus.playwright.*), but unfortunately a QuarkusTestResourceConfigurableLifecycleManager doesn't have access to @ConfigMappings (I checked with Georgios).

[melloware]

nice!

[edeandrea]

@melloware this doesn't actually fix #60. It has something in common, but doesn't solve that problem.

See #60 (comment)

[melloware]

OK I removed the tag. I love this PR though when you get it working.

[edeandrea]

This PR is working and complete. I only provided a couple of options for now. I didn't want to have to mirror the entire Playwright API.

A QuarkusTestResourceConfigurableLifecycleManager doesn't have access to a ConfigMapping class (because the QuarkusTestResourceConfigurableLifecycleManager is not a bean itself).

Even trying to unwrap it with ConfigProvider.getConfig().unwrap(SmallryeConfig.class).getConfigMapping() doesn't work. It has something to do with the ordering in which things happen. The config classes aren't yet available when a QuarkusTestResourceConfigurableLifecycleManager is instantiated and its start method is called.

If we want to move to a properties-based configuration model then we will have to move away from having the implementation using a QuarkusTestResourceConfigurableLifecycleManager.

[melloware]

want me to publish a release?

[melloware]

@all-contributors add @edeandrea for code

[allcontributors]

@melloware

I've put up a pull request to add @edeandrea! 🎉

[edeandrea]

want me to publish a release?

That's up to you. Would be nice to have this feature! I was implementing it myself with JUnit on the BrowserContext and figured having it on the framework would be a better place.

[melloware]

publishing 2.1.0 now!

[melloware]

2.1.0 is in Maven Central