Even with just one branch, if the team adds ten minutes of new automation per sprint, that phone is going to be bogged down within a couple of months. Most modern engineering processes want to run tests on every new commit pushed to the branch, and possibly on every branch. That takes a single machine and allows it to run tests on one phone. The challenge is which tools to use where.Ī single machine to perform builds is certainly a way to start it was how Extreme Programming started. In other words, there may be a time and a place for simulators, emulators, and physical devices. Managing that many actual devices in the cloud is no picnic either. This sort of work isn't exactly a great fit for physical devices plugged into a cable and running to a laptop. The teams I work with today tend to have a stronger focus on the pipeline of delivery work, along with eight, sixteen, or perhaps thirty-two tests at the same time. Around that time, a lot of people began using phrases like " End to end is further than you think." Simulators and emulators, after all, could not simulate heat, poor memory management, low power, and other problems. I was not capable of clicking on it myself. Ten years ago I saw a Selenium test that could click on a capital "I" that was one pixel wide.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |