I began Boa Constrictor back in 2018 since I hated page items. On a previous job, I saw page items swell to a number of thousand lines long with duplicative techniques. Establishing brand-new tests ended up being a problem, and about 10% of tests stopped working daily since they didn’t manage waiting effectively.

So, while preparing a test method at a brand-new business, I invested time in discovering the Movie script Pattern. To be sincere, the pattern appeared a bit complicated in the beginning, however I wanted to attempt anything besides page items once again. Ultimately, it clicked for me: Stars usage Capabilities to carry out Interactions Boom! It was a tidy separation of issues.

Regrettably, the only significant executions I might discover for the Movie script Pattern at the time were Tranquility BDD in Java and JavaScript. My business was a.NET store. I tried to find C# executions, however I didn’t discover anything that I relied on. So, I took matters into my own hands and executed the Movie script Pattern myself in.NET. At first, I executed Selenium WebDriver interactions. Later on, my group and I included RestSharp interactions. We ultimately launched Boa Constrictor as an open source job in October 2020 as part of Hacktoberfest.

With Boa Constrictor, I personally looked for to renew interest in the Movie script Pattern By bringing the Movie script Pattern to.NET, we made it possible for folks beyond the Java and JavaScript neighborhoods to provide it a shot. With our abundant docs, examples, and videos, we made it simple to onboard brand-new users. And through conference talks and webinars, we promoted the principles behind Movie script, even for non-C # developers. It’s been remarkable to see many other folks in the screening neighborhood start speaking about the Movie script Pattern in the previous couple of years.

I likewise wished to offer a standalone application of the Movie script Pattern Considering That the Movie script Pattern is a style for automating interactions, it might and ought to incorporate with any NET test structure: SpecFlow, MsTest, NUnit, xUnit.net, and any others. With Boa Constrictor, we focused singularly on making interactions as exceptional as possible, and we let other tasks manage different issues. I did not desire Boa Constrictor to be locked into any specific tool or system. In this sense, Boa Constrictor diverged from Tranquility BDD– it was not suggested to be a.NET variation of Tranquility, regardless of taking much motivation from Tranquility.

In Addition, in the style and all the messaging for Boa Constrictor, I aimed to make the Movie script Pattern simple to comprehend A lot of folks I understood quit on Movie script in the past since they believed it was too made complex. I wished to break things down so that any automation designer might select it up rapidly. For this reason, I formed the soundbite, “Stars utilize Capabilities to carry out Interactions,” to explain the pattern in one line. I likewise created the job’s motto, “Better Interactions for Better Automation,” to plainly interact why Movie script needs to be utilized over options like raw calls or page items.

Up until now, Boa Constrictor has actually been successful decently well in these objectives. Now, the job is pursuing another objective: equalizing the Movie script Pattern

At its heart, the Movie script Pattern is a generic pattern for any type of interactions. The core pattern ought to not prefer any specific tool or bundle. Anybody needs to have the ability to execute interaction libraries utilizing the tools (or “Capabilities”) they desire, and each of those libraries ought to be dealt with similarly without choice. Just recently, in our prepare for Boa Constrictor 3, we revealed that we wish to develop different plans for the “core” pattern and for each library of interactions. We likewise revealed strategies to include brand-new libraries for Playwright and Applitools. The existing libraries– Selenium WebDriver and RestSharp– need not be the only libraries. Boa Constrictor was never ever suggested to be simply a WebDriver wrapper or a remarkable page item. It was suggested to offer much better interactions for any type of test automation.

In variation 3.0.0, we effectively separated the Boa.Constrictor job into 3 new.NET tasks and launched a NuGet bundle for each:

This separation makes it possible for folks to select the parts they require. If they just require Selenium WebDriver interactions, then they can utilize simply the Boa.Constrictor.Selenium bundle. If they wish to execute their own interactions and do not require Selenium or RestSharp, then they can utilize the Boa.Constrictor.Screenplay bundle without being required to handle those additional dependences.

Additionally, we continued to keep the “timeless” Boa.Constrictor bundle. Now, this bundle merely declares dependences on the other 3 plans in order to maintain in reverse compatibility for folks who utilized previous variation of Boa Constrictor. As part of the upgrade from 2.0.x to 3.0.x, we did alter some namespaces (which are recorded in the job changelog), however the remainder of the code stayed the very same. We desired the upgrade to be as simple as possible.

The core factors and I will continue to execute our prepare for Boa Constrictor 3 over the coming weeks. There’s a lot to do, and we will do our finest to execute brand-new code with consideration and quality. We will likewise aim to keep whatever recorded. Please be client with us as advancement advances. We likewise invite your contributions, concepts, and feedback. Let’s make Boa Constrictor exceptional together.