It also needs to know a little bit about your app. For example, Appium needs to know what platform you want to run on and what device you want to use, and it needs these things so that it can pick the right driver to run your session. So, there are a few keys, in other words, a few capabilities that are required for every Appium session. So, it's basically just a way of creating a key value pair that Appium needs in Java. And one of the arguments for this constructor is something called a DesiredCapabilities object. In Appium, it's either Android driver or iOS driver. So, when we create an instance of an Appium session, we use a special class for that, which we'll look at. In Java, so when we're using the Appium, Java client, which we are in this workshop, they are a desired capabilities object that's passed to the driver class constructor. Basically, at the end of the day, they're a JSON object, a key value pair that is sent as part of the payload for session initialization. So that is, again, what capabilities are. So, you'll recall capabilities from our Appium overview session, or our session on the Appium architecture, where we discussed how the parameters to the new session command are a JSON object with keys and values. ![]() ![]() In this module, we are going to examine the concept of capabilities and using capabilities to start and stop Appium sessions on platforms and devices that we care about. Hello everyone, and welcome back to the Appium Pro intro workshop.
0 Comments
Leave a Reply. |