Scale up your automation testing with Test::Unit scripts on LambdaTest online selenium grid and release quality builds in no time.
Create a continuous delivery pipeline by running multiple Selenium Test::Unit scripts in parallel on LambdaTest cloud grid. You can choose from 2000+ browsers to automate your Test::Unit scripts for cross browser testing.LEARN MORE
Perform geo targeting, geo blocking and localisation tests with Test::Unit Scripts from 27+ countries using LambdaTest online Selenium grid. Automate your geolocation tests with ease using LambdaTest capability generator.START TESTING
Running Test::Unit scripts on your locally hosted Selenium grid? Use LambdaTest GitHub repo and migrate to cloud selenium grid with ease. Leverage an online selenium grid to increase your test coverage and accelerate the testing process.CHECK GITHUB REPO
Your first 100 Selenium automation testing minutes
are on us, along with a lifetime access.
Using LambdaTest automation, turn your test data into action with detailed Statistics of total tests run, minutes consumed, tests passed, tests failed and many more metrics along with timeline charts and automation logs.START TESTING
Test::Unit is based on xUnit principles, and it is available with the standard library of Ruby. It was designed by Kent Beck for the unit testing of web applications. Using this framework, you can easily create unit tests, check results, and to automate unit testing in Ruby.
The LambdaTest Selenium grid doesn’t identify if you test ‘passed’ or ‘failed’. It only identifies whether a test has executed to it’s last command or whether it has stopped/timed-out before it. The user would have to pass on these parameters to LambdaTest platform to make it possible for tracking these values at LambdaTest platform. Make use of LambdaTest API or LambdaTest Annotations, for pushing additional metadata to LambdaTest or to track the pass/fail status of a test.
Yes! One of the key features of LambdaTest Selenium grid is the ability to run your test cases in parallel. Which means you can execute numerous automation test cases altogether and enable you to cut down on test times. With LambdaTest selenium grid you can run a single test scenario across different browsers or different test scenarios with the same browser (or any other combinations). Wondering how many parallel test cases can you run? That depends entirely on the number of concurrent sessions under your opted plan.
Maximum number of test cases that can be queued = n + 150 Here, n = number of concurrent sessions. For instance, if you are opting for pricing where you can avail up to 10 concurrent sessions. Then the maximum number of test cases that can be queued will be equal to 10 + 150 i.e. 160 queued test cases. LambdaTest would automatically schedule and execute test cases for you. We have added a capacity constraint on the number of tests that can be queued to prevent over-exploitation of the platform. Refer LambdaTest Queuing Policy to know more.
LambdaTest Concurrency Calculator is here to help you calculate the number of parallel sessions you need for your test coverage. Feed the information to our Concurrency Calculator, and it would suggest to you the appropriate number of parallel sessions.