WEBVTT 00:00:00.000 --> 00:00:02.890 Upload your app first. You'll be using this curl command essentially to do that and to this endpoint. 00:00:03.550 --> 00:00:05.190 This would be for both your Android as well as iOS apps. 00:00:05.190 --> 00:00:07.120 Once you've done uploading the app, you'll of course get your app URL ID. 00:00:07.860 --> 00:08.900 Then you upload your test suite. 00:09.110 --> 00:11.120 We basically require customers to zip their test suite and upload it to us. 00:11.120 --> 00:14.930 Again, there'll be a hash added for the same. To run it, similar to frameworks, you just have to mention your app ID as well as your test suite IDs that you've got from the above two steps. 00:15.420 --> 00:19.490 Only this kind of endpoint changes for Android as well as iOS, so we have different endpoints for both. 00:19.490 --> 00:22.390 Just make sure you are uploading the right app, like an Android app here when you have the Android endpoint and the test suite. 00:22.390 --> 00:24.080 The test suite can be common, so that's not really a problem. 00:24.080 --> 00:26.110 You can mention the devices that you want to run it on. 00:26.330 --> 00:30.310 You can mention a single device, of course, but if you mention two devices, we will run it in parallel. 00:30.310 --> 00:35.380 That is the default behavior; we'll just run on these devices in parallel. 00:35.380 --> 00:39.750 Running it this way is going to run the whole test suite, which is all the YAML files, regardless of whether they are nested inside different directories or not on this particular app. 00:39.750 --> 00:43.120 If you don't want to run your entire test suite and only want to run a particular file or a particular folder, you can add in this particular key called execute. 00:43.640 --> 00:47.380 You can give a relative path. This relative path is basically with respect to the test suite that you have zipped. 00:47.380 --> 00:49.610 You'll have to give that relative path to either the flow file or the folder. 00:49.610 --> 00:53.110 You can give both as well, in cases where you want to run a particular subfolder and a single file from some other folder. 00:53.110 --> 00:57.250 This is essentially an array, so you can give as many files as possible or as many paths as possible, and it's going to run these tests sequentially. 00:57.250 --> 00:59.260 That's all you need to do to run it on BrowserStack. 01:00.070 --> 01:01.810 I'll just quickly show you guys how the dashboard looks like. 01:01.810 --> 01:02.830 This is an example of an Android test. 01:03.280 --> 01:05.190 Essentially, what you have here as commands is pretty human-readable. 01:05.700 --> 01:09.680 If you notice, whenever we are calling a subflow, we have put an indent here so that you can notice that all these following steps are within a subflow. 01:09.680 --> 01:11.230 Once the indent is done, the subflow is over. 01:11.230 --> 01:12.190 That's how we're treating it. 01:12.190 --> 01:14.920 Within this particular flow, there was another subflow, and it would be indented under this. 01:14.920 --> 01:18.990 That's how we've handled the nesting because there is no limit to the nesting, like I said before. 01:18.990 --> 01:21.820 A directory kind of structure for viewing text logs was not really making sense. 01:21.820 --> 01:23.110 Let me just go back one step. 01:23.110 --> 01:24.490 This is how my build would look like. 01:24.900 --> 01:27.420 Within this build, I can see that it was run in parallel on both these devices. 01:27.850 --> 01:32.400 These are all the flows that were done. Basis what I had mentioned, there can be any number of nested flows. 01:32.400 --> 01:35.480 We've decided to go with a flat structure because in the UI, it was not possible for us to keep indenting flows here. 01:35.480 --> 01:37.330 You can see the logs for individual flows as well. 01:37.330 --> 01:42.500 Let's say master is actually calling subflows like the Wikipedia app test; then you will be able to see the corresponding test commands within master as well, like I just showed you within a subflow. 01:42.840 --> 01:44.200 The other features on the dashboard are pretty much the same. 01:44.750 --> 01:48.330 You have your metadata here with respect to your app, test suite, parameters, and whatnot, with your caps and everything. 01:48.330 --> 01:50.850 You can click on any of these commands, and it will automatically seek to that point. 01:50.850 --> 01:55.770 Post this, a couple of other advantages that we are offering over Maestro: Maestro does offer text logs today and it offers other logs, which is a combination of device instrumentation logs and a couple of other information as well. 01:56.240 --> 01:58.200 However, it's a bit difficult to read and understand. 01:58.200 --> 01:59.390 We are providing this under other logs. 01:59.390 --> 02:01.370 There are a couple of other logs from our side, which are network logs. 02:01.370 --> 02:02.510 We're providing network logs and devicelogs. 02:02.510 --> 02:04.990 It's not enabled here, so it's not showing up, but device logs are also available. 02:04.990 --> 02:07.720 We also provide app profiling capability. And we also do provide app profiling capability for the tests that you run.