![]() Running multiple Appium servers, and sending one session to each server.There are basically four designs for running multiple Appium sessions at a time: For now, let's just learn the mechanics of running multiple Appium sessions at a time, and leave the big-picture stuff for later. In another Appium Pro article, we'll discuss all the ins and outs of parallelization from a testsuite perspective. Also, with the availability of cloud-based test execution, adding additional test threads becomes a problem of cost rather than technical feasibility. It's probably not realistic to assume that you could afford thousands of test execution threads, but it illustrates the point that often the most effective optimization you can make to reduce overall build time is to parallelize test execution. In this case, you're running every single test simultaneously, and the build is only as long as the longest test! Let's say, on the other hand, that for each additional test you add to your build, you unlock an additional test execution thread. ![]() Think about it this way: if you have a build in which you are constantly adding tests (as you are likely to do while ensuring quality for an app), then each additional test will add directly to your build time, if you're running them one-by-one: The ultimate solution to this is to run more than one test at a time. UI-driven functional tests take time, and even when we've used all the tricks up our Appium sleeves, the tests will never be as fast as, say, unit tests. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |