Our role as package testers has transformed as brands shifted to digital-first experiences for their users. Once siloed to a single step at the end of maturation cycles, testing is now a continuous process that speed development and improves the customer experience. & nbsp;

We ’ ve conform to this new reality by squeeze quality engineering, a praxis that include quality essay throughout the ontogenesis lifecycle to render a positive exploiter experience that will aid companies satisfy, retain, and produce new customer. But this shift has also change what we need from testing creature, leading to the sunset of model like andTestProject. As teams begin to transmigrate their testing strategies into new automated testing resolution, there are manner to streamline the process.

Executing Your Software Testing Strategy with mabl 

Beginning the cycle to migrate be efforts between a sunsetting platform to a new solution can be a daunting task, often requiring a total overhaul of the subsist mechanisation suites and implement an only new fabric from scratch. As a Solutions Engineer with mabl, I frequently indorse new mabl user through this process. My goal is invariably to make teams as efficient as possible as they transmigrate their existent efforts, cut the time-to-value and saving them valuable time and attempt.

Fortunately for TestProject and Protractor exploiter, mabl provides tools that enable lineament engineering team to spell their Selenium-based test scripts instantly into mabl, jump-start their work and alleviate the transition between test automation framework. This functionality can also be utilise to spell examination cases still when not written natively in Selenium, get it easier to import tests from framework like TestProject. Using the process below, we ’ ll export our TestProject test instance into mabl using a migration-friendly format like Selenium Java. & nbsp;

Importing TestProject tests into mabl initial requirements

To get started, we ’ ll need: & nbsp;

• Mabl ’ s Java Selenium Agent, which is available to download from our support. & nbsp;
• A Selenium Java Agent API key yield from your mabl workspace
• The TestProject test causa exported to Java code, utilizethis procedure
• The TestProject agent instal on your machine andfilewith your TestProject account
• An IDE (such asEclipse) to which we can import the TestProject as a Gradle project & nbsp;
• TestProject ’ s open SDKinstalledto allow exported projects to execute locally & nbsp;

Steps to import a TestProject automated test into mabl

Now that we feature our instrument ready, we can commence the actual migration process: & nbsp;

• Generating our Selenium agent API key: We ’ ll initiatory generate an API key from mabl via the Selenium Java Agent, which we ’ ll use to generate the following VM argument to add to our build.gradle file.
• Test Project Script Modification: We ’ ll need to modify this subdivision of our build.gradle file to include a new jvm argument which will contain the way to our Selenium agent and your API key. & nbsp;

test {

& nbsp; & nbsp; & nbsp; & nbsp; useJUnitPlatform ()

& nbsp; & nbsp; & nbsp; & nbsp;jvmArgs `` -javaagent: /Path/toYour/mabl-selenium-agent.jar=apiKey=YOURAPIKEYHERE ''

}

• In that same build.gradle filewe ’ ll need to add another dependency for the TestProject SDK, which can be added in the following section of that file.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

dependencies {

& nbsp; & nbsp; & nbsp; & nbsp; // Use JUnit Jupiter API for testing.

& nbsp; & nbsp; & nbsp; & nbsp; testImplementation & nbsp; 'org.junit.jupiter: junit-jupiter-api:5.6.0 '

& nbsp; & nbsp; & nbsp; & nbsp; // Module `` junit-jupiter-params '' of JUnit 5.

& nbsp; & nbsp; & nbsp; & nbsp; testImplementation & nbsp; group: 'org.junit.jupiter ', name: 'junit-jupiter-params ', version: ' 5.6.0 '

& nbsp; & nbsp; & nbsp; & nbsp; // Use JUnit Jupiter Engine for testing.

& nbsp; & nbsp; & nbsp; & nbsp; testImplementation & nbsp; 'org.junit.jupiter: junit-jupiter-engine:5.6.0 '

& nbsp; & nbsp; & nbsp; & nbsp; implementation compileOnly 'io.testproject: java-sdk:1.2.4-RELEASE '

}

• Importing our TestProject script into our IDE:We can now choose to import an existing Gradle project in our IDE. In this case, we ’ ll select the exported test script from TestProject. Once we have our script imported into our IDE with our modified build.gradle file, we ’ ll check that we feature our TestProject agent scarper to allow for local execution. & nbsp;

Provided we receive all dependencies resolved, we can now run our examination script as a Gradle test. This will cause mabl ’ s Selenium agent to depart wiretap WebDriver commands and read them into mabl test steps while importing the test playscript.

• Once the Gradle test has completed execution successfully with the mabl Selenium agent running, we should be able to remark our newly spell test script in our mabl workspace.

Considerations when importing automated tests into mabl

Currently, the instrument can import the undermentioned Selenium actions as mabl exam step:

• Setting the viewport size
• Navigation to URLs
• Clicking elements on the page
• Entering text into fields
• Sending keypress events

After the initial import, you ’ ll need to update the newly created mabl tests for the following:

• Assertions for assorted validations
• Using variable
• File download and upload actions
• Drag and drop activity
• Conditional and intertwine logic
• Hover actions
• Cookies

Start Running Your Automated Tests with Autohealing and Advanced Reporting

Now that we ’ ve successfully migrated our TestProject tests into mabl, we can continue expanding our software quiz scheme with confidence. All mabl tests are supported byautohealing, a functionality that automatically repairs broken tests as our product changes. Our tests will work for a longer period of clip with less upkeep, enable our quality squad to dedicate more time to testingmore client journeyand support the development of new features. We ’ ll too be able to monitor the effectiveness of our testing strategy acrosshigh-traffic web pages, track quality sheer over time, and build a culture of quality by integrating mabl with ourfavorite development tools. 

Get started with mabl today with our14 day free test.