Making the Most of Your Tech Stack: Tips & Tricks for Better Mobile Testing

Video Transcript

0:00:19.437,0:00:24.000

Hey Folks, if you are just joining Billy Cabrera here

0:00:24.000,0:00:32.156

we are going to be starting in just a few moments want to make sure everybody has a chance to join

0:00:32.156,0:00:33.816

Get this party started,

0:00:33.816,0:00:35.096

Adam. How are you doing?

0:00:35.726,0:00:37.376

Doing well, How yourself building?

0:00:37.376,0:00:42.346

Excited. Excited. I think we have good term out today across all the sessions

0:00:42.346,0:00:43.896

so and pumped on that.

0:00:43.896,0:00:48.346

Absolutely. Yeah. So sorry for being a couple seconds late. It’s what happens when you’re

0:00:48.346,0:00:51.616

jumping from one session to the next at a lyme event, but

0:00:51.616,0:00:55.986

yeah. Billy, this is your time to show the audience, some a mobile testing tip

0:00:55.986,0:01:00.656

and tricks. And if you guys have questions as he goes along, feel

0:01:00.656,0:01:04.056

free to throw them in the chats or the q and A pain, and

0:01:04.056,0:01:05.316

We’ll grab him as we go.

0:01:05.316,0:01:08.756

Awesome. Awesome. Thank you, Adam.

0:01:08.756,0:01:13.256

Folks, if you haven’t met me or Covid before,

0:01:13.256,0:01:16.446

wanna make sure that everyone has a chance to

0:01:16.446,0:01:21.116

to meet the team behind the team. So shout out to Adam for getting this one together.

0:01:21.116,0:01:24.136

On the marketing side. Am Billy Cabrera. I am your

0:01:24.136,0:01:27.846

senior solutions engineer or sales engineer. Here at Covid tong, senior

0:01:27.846,0:01:31.676

My background is in the more tech,

0:01:31.676,0:01:35.686

Saas space of the world where I also spent some time

0:01:35.686,0:01:40.476

with accessibility, which is something that we’re gonna talk about. It’s certainly near and dear to my heart

0:01:40.476,0:01:45.356

But today, this session is dedicated

0:01:45.356,0:01:49.786

to make it the most of your tech stack with respect to mobile application testing,

0:01:49.786,0:01:53.886

We’re gonna cover some tips and tricks. I’m gonna get into

0:01:53.886,0:01:57.466

our platform to show you live, what

0:01:57.466,0:02:01.356

that solution can look like. Because if you’re here,

0:02:01.356,0:02:04.406

you wanna learn how to make the most of your efforts

0:02:04.406,0:02:07.006

in mobile across your tech deck.

0:02:07.006,0:02:10.566

Right? You you may be starting out. You may be

0:02:10.566,0:02:13.736

a veteran of mobile application testing,

0:02:13.736,0:02:15.846

But everyone’s a little different. Right?

0:02:15.846,0:02:20.636

You might have marketing oriented

0:02:20.636,0:02:24.456

app or maybe even offer support through your app,

0:02:24.456,0:02:27.646

or you might make all of your revenue through your app.

0:02:27.646,0:02:32.486

Like Uber. For example, but regardless, it’s incredibly important

0:02:32.486,0:02:37.006

to ensure mobile success through testing from start to finish

0:02:37.006,0:02:42.686

across all of your releases. And today, we really are gonna get

0:02:42.686,0:02:43.866

some tips and tricks,

0:02:43.866,0:02:48.536

that’ll help you develop this mobile testing strategy. Now

0:02:48.536,0:02:52.306

At Kobiton, you’re gonna hear me, say this a little bit. But we

0:02:52.306,0:02:53.766

to refer to your journey, to

0:02:53.766,0:02:58.526

in mobile testing as the… With the the mobile maturity model.

0:02:58.526,0:03:01.786

And and really where we’re gonna start the conversation

0:03:01.786,0:03:05.526

is step one. Right? You obviously

0:03:05.526,0:03:08.126

have ambitions

0:03:08.126,0:03:11.546

to get your app out in in the best way

0:03:11.546,0:03:16.336

faster. And with as many with as minimal amounts,

0:03:16.336,0:03:19.476

of issues or maybe performance issues of

0:03:19.476,0:03:22.916

And and again, you might already have your app out in the while.

0:03:22.916,0:03:25.966

That’s great. Right? No matter where you are

0:03:25.966,0:03:29.766

you’re here talking to us because you wanna get better.

0:03:29.766,0:03:33.116

At this mobile topic. Now, since

0:03:33.116,0:03:37.906

you might have an app or your you’re building one. One of the first steps that we like

0:03:37.906,0:03:43.366

talk about is really finding a a platform that’s not gonna slow you down.

0:03:43.366,0:03:48.696

Now if you’re just starting out this mobile testing, maybe a little early on

0:03:48.696,0:03:53.666

in your journey with mobile maturity, what you really want to do

0:03:53.666,0:03:58.036

is come to one of these conclusions. You might have already come to them. Right? Whether

0:03:58.036,0:04:02.166

simulators or or a platform that that provides that

0:04:02.166,0:04:06.176

is the move for you or maybe you want real devices

0:04:06.176,0:04:11.146

with real battery or other performance metrics baked

0:04:11.146,0:04:15.906

That’s huge. Right? Because you wanna be able to mirror

0:04:15.906,0:04:20.216

what goals you have with the platform that can support that.

0:04:20.216,0:04:25.186

There’s so many in the space that I know it might be a little bit overwhelming

0:04:25.186,0:04:30.156

so one of the great ways that we talk about this growth through this journey

0:04:30.156,0:04:33.836

Kobiton is really to to to find the scope

0:04:33.836,0:04:37.966

of what you’re testing for. And that’s huge

0:04:37.966,0:04:41.686

and it’s a huge issue as well or challenge

0:04:41.686,0:04:46.296

because there are a lot of a lot of sort of pitfalls.

0:04:46.296,0:04:49.826

Right? There’s so much device fact fragmentation,

0:04:49.826,0:04:54.616

You have so many of these device vendors. All of them with different software that

0:04:54.616,0:04:58.836

comes with the devices that might cause issues down the line.

0:04:58.836,0:05:00.576

You don’t want

0:05:00.576,0:05:04.286

those types of challenges. Obviously, that’s why we’re testing for them.

0:05:04.286,0:05:05.956

And and really, again,

0:05:05.956,0:05:10.926

those Kpis full functionality across multiple operating

0:05:10.926,0:05:15.966

systems can help dictate what exactly you’re gonna be testing for.

0:05:15.966,0:05:20.046

So finding these Kpis, how do you define success

0:05:20.046,0:05:25.016

and really, is that your developers or Qa teams responsibility

0:05:25.466,0:05:28.756

finding the platform and defining that

0:05:28.756,0:05:32.376

scope or these first two major tips and tricks

0:05:32.376,0:05:37.256

for better bet better mobile testing. Now that’s often going to be

0:05:37.256,0:05:40.366

for those earlier earlier

0:05:40.366,0:05:45.336

mobile testing sort of frameworks that you might be still building out.

0:05:45.336,0:05:49.056

No. Once you have those metrics,

0:05:49.056,0:05:54.026

and you have the platform that can support that testing

0:05:54.026,0:05:58.996

let’s talk about what that can look like. And and this is where we’re gonna use

0:05:58.996,0:06:03.186

our our home brand C tom’s platform

0:06:03.186,0:06:07.076

to be able to achieve these individual types of results.

0:06:07.076,0:06:12.016

So I’m gonna start sharing my screen here and the first thing you’re going to see

0:06:12.156,0:06:14.116

is a device form.

0:06:14.116,0:06:16.146

Now at Covid,

0:06:16.146,0:06:20.816

we have real physical devices that allow us to be able

0:06:20.816,0:06:27.746

to curate, the types of devices and the scope that represents your business’s needs.

0:06:27.746,0:06:31.756

Right? You know, one thing that we’ve found, for example, in the last

0:06:31.756,0:06:33.116

Am region is that

0:06:33.116,0:06:37.806

all android. Right? You wanna be able to mirror the test scope

0:06:37.806,0:06:41.916

to the types of devices that you want to be able to test on.

0:06:41.916,0:06:46.616

Now these device farms, of course,

0:06:46.616,0:06:51.586

can shrink. They do change over time. Right? You you you know that the newest iphone just

0:06:51.586,0:06:52.276

came out.

0:06:52.276,0:06:55.956

You might wanna make sure that you’re staying on top of the latest and greatest.

0:06:55.956,0:07:00.096

But again, that’s where scope really comes into play where

0:07:00.096,0:07:04.826

maybe you have a lot of tickets in Jira from bugs that were found on

0:07:04.826,0:07:09.646

older versions of an android, for example, Maybe there are older

0:07:09.646,0:07:12.486

devices that you that you

0:07:12.486,0:07:17.456

actually have a lot of customers on. So again, that scope is going to be reflected

0:07:17.456,0:07:21.346

in that device farm for you to be able to do

0:07:21.346,0:07:23.616

that type of manual testing.

0:07:23.616,0:07:28.496

So let’s talk about manual test it. Today’s guinea pick is gonna be my

0:07:28.496,0:07:32.596

favorite little s twenty one with A5G chip in it.

0:07:32.596,0:07:34.306

We’re gonna watch this badly.

0:07:34.306,0:07:39.926

Now remember, when we’re doing manual testing, there are some creature comforts

0:07:39.926,0:07:43.246

that you want to look for and that you want

0:07:43.246,0:07:47.706

to be able to expect of the platform that you use. Now

0:07:47.946,0:07:52.016

I’m not gonna go through every single possible

0:07:52.016,0:07:55.096

test case that you could look for. But again,

0:07:55.096,0:07:58.446

you want to be able to be comprehensive in your testing.

0:07:58.446,0:08:00.996

Now that can range from

0:08:00.996,0:08:05.576

maybe just simple, touch or benches and zoom

0:08:05.576,0:08:08.566

gestures, on these devices

0:08:08.566,0:08:13.086

but you want to be comprehensive again. That also means that you wanna be a little bit more technical.

0:08:13.086,0:08:18.056

You can start getting pretty fancy by maybe updating the device

0:08:18.056,0:08:23.786

location, wanted to test this device manually to see how it behaves

0:08:23.786,0:08:27.586

in different regions, maybe in a different country for example.

0:08:27.586,0:08:31.886

That’s a great way for you to be again, comprehensive in your scope.

0:08:31.886,0:08:35.536

You also might wanna do some high things like

0:08:35.536,0:08:42.076

biometric authentication Maybe you simply just want to scan a Qr code.

0:08:42.076,0:08:47.016

And these are the types of challenges that, again, the the breadth

0:08:47.016,0:08:51.796

of devices that you’ll gonna… You’re gonna run into should all be tested

0:08:51.796,0:08:55.776

equally. And even if it’s just scanning a Qr code,

0:08:55.776,0:08:58.186

you want a platform that supports that testing.

0:08:58.186,0:09:00.276

Maybe with something like image

0:09:00.276,0:09:04.856

injection thinking about that again is going to

0:09:04.856,0:09:09.316

further you along in that mobile maturity model that we talk about

0:09:09.316,0:09:13.716

getting you closer to, you know, a really mature and

0:09:13.716,0:09:17.106

well lu testing outfit

0:09:17.526,0:09:21.086

We take a quick pause here and check four questions

0:09:21.086,0:09:24.136

in there at Adam. Are there any questions set?

0:09:24.136,0:09:26.666

We need to address before moving forward.

0:09:27.476,0:09:31.466

Nothing just yet that I’m seeing, but I’ll let you know once something comes through.

0:09:31.466,0:09:36.076

Awesome. Hey, Derek. Love you man. Good to see you on here as well.

0:09:36.076,0:09:38.856

Saw that one come through. So

0:09:39.316,0:09:43.206

moving right along. We’re we’re really in the nitty gritty of it.

0:09:43.206,0:09:45.946

Right? We know we know a little bit about the scope

0:09:45.946,0:09:47.566

We know about finding

0:09:47.566,0:09:50.626

the platform that supports that testing scope

0:09:50.626,0:09:58.556

talked about real physical devices. This guinea pig ours, this s twenty one is a real physical device. It

0:09:58.556,0:10:01.906

resides just like I do in Atlanta.

0:10:01.906,0:10:04.436

And it physically exists within our data center.

0:10:04.436,0:10:09.406

That’s cool. Now, if you’ve gotten this far in your testing out

0:10:09.406,0:10:14.136

it, you know that you might have some specific metrics that you’re using to

0:10:14.136,0:10:15.746

find success.

0:10:15.746,0:10:20.716

If we look to the right of our platform, right off the bat, we are

0:10:20.716,0:10:24.426

probably getting a lot of attention at this

0:10:24.426,0:10:28.226

scroll here, and those are the actual logs

0:10:28.226,0:10:32.716

or the exhaust pipe clearly of this S twenty one that

0:10:32.716,0:10:36.076

I have up running. Now that

0:10:36.076,0:10:41.046

log read is is a great way for you to do. A lot of

0:10:41.046,0:10:45.026

A lot of investigation as to what’s working or what isn’t working

0:10:45.026,0:10:49.996

with this specific test. You know, when we’re looking at success,

0:10:49.996,0:10:54.536

criteria, the specific Kpis, maybe your application

0:10:54.536,0:11:03.576

right to a lock that lets you know of a specific function. That’s six seated or maybe you’re looking for a specific output. Being able to find those,

0:11:03.576,0:11:07.916

whether it is in the middle of this actual session this manual session

0:11:07.916,0:11:11.146

or later down the road is super important

0:11:11.146,0:11:13.626

the exact same way that maybe

0:11:13.626,0:11:17.756

pulling in some of these metrics is also equally important.

0:11:17.756,0:11:21.526

Right? You wanna make sure that your device, your application

0:11:21.526,0:11:26.046

is also not choking your actual users

0:11:26.046,0:11:28.046

spoons. So

0:11:28.046,0:11:31.346

being able to plug into the into the exhaust pipe.

0:11:31.346,0:11:35.626

That’s huge. You know, what we’re what we’re looking to achieve is

0:11:35.626,0:11:39.386

again, comprehensive breakdown of

0:11:39.386,0:11:44.146

the success criteria in the platform. And what we’re looking at here

0:11:44.146,0:11:48.666

is a collection of those device stats that you are able to get

0:11:48.666,0:11:52.476

because it can’t real devices, simulators and

0:11:52.476,0:11:56.876

aren’t gonna give you the breaths in the depths that you may want.

0:11:56.876,0:12:01.846

From a real physical device. So just a quick breakdown, we already looking at

0:12:01.846,0:12:06.606

memory, Cpu, we have network, we have actual battery

0:12:06.606,0:12:10.776

drain and even temperatures, So

0:12:10.776,0:12:15.146

here at Overt tom, you might hear us say this a million times, but

0:12:15.146,0:12:19.856

wanna be able to recreate device in hand experiences.

0:12:19.856,0:12:23.716

Because we’re able to give me those exhaust pipe type metrics,

0:12:23.716,0:12:26.856

you’re absolutely able to see what’s going on

0:12:26.856,0:12:30.066

and what’s going on under the hood specifically

0:12:30.546,0:12:34.866

now. Just just for the folks that men not

0:12:34.866,0:12:36.536

be familiar with Covid sun.

0:12:36.536,0:12:40.006

Obviously, I’m testing on a real device.

0:12:40.006,0:12:43.896

I wanna install an app very quickly. I’m just going to do this

0:12:43.896,0:12:46.046

on the fly using our own

0:12:46.046,0:12:50.596

homemade made app called Ling. Part of the reason I’m doing this

0:12:50.596,0:12:52.456

to sort of represent

0:12:52.456,0:12:56.856

what manual test might look like and why this experience matters so much and

0:12:56.856,0:13:01.556

Again, why your platform really needs to be able to bring

0:13:01.556,0:13:05.766

bring the results that matter to your business. Where we have

0:13:05.766,0:13:10.436

We man installed as a representative for this manual test

0:13:10.436,0:13:13.276

all we’re gonna do is tap get started.

0:13:13.276,0:13:18.000

Next, next, next

0:13:18.000,0:13:22.872

and then you know what, I’m gonna type in my phone number

0:13:23.075,0:13:25.496

and that will complete the test

0:13:25.496,0:13:28.582

if this represents a good sort of manual test,

0:13:28.582,0:13:30.542

you will know because

0:13:30.542,0:13:34.852

now we’re gonna talk a little bit more about how can we expand

0:13:34.852,0:13:39.162

and and what should we consider with these manual type tests? Because

0:13:39.162,0:13:42.412

I’m gonna talk about automating

0:13:42.412,0:13:46.682

that next But first, we wanna talk a little bit about

0:13:46.682,0:13:50.542

this manual test, some other criteria.

0:13:50.542,0:13:58.652

That we’re gonna wanna look at, which is gonna be held in C within our session overview and our session explorer

0:13:58.652,0:14:02.782

or we gonna a break breakdown of everything that happened in that manual test or

0:14:02.782,0:14:06.822

we are able to check out a quick video on it. That’s great. We can

0:14:06.822,0:14:11.182

see the specific apps that were installed, maybe something about

0:14:11.182,0:14:14.422

the actual device that we were talking about or using

0:14:15.552,0:14:20.592

a lot of them mean the bones, a lips and our explorer. Now our

0:14:20.592,0:14:24.962

explorer is going to take every single gesture

0:14:24.962,0:14:29.152

test and align it to a timeline

0:14:29.152,0:14:34.122

down here at the bottom where, again, we are looking for specific moments in that

0:14:34.122,0:14:39.062

test. As you remember, I tapped get started on the actual app

0:14:39.392,0:14:42.322

that is not a real device that is again,

0:14:42.322,0:14:47.292

really just the output of that manual test that I just created.

0:14:47.292,0:14:57.232

You can see here this red dot is where I tested or where I act or where the gesture was received on the actual app,

0:14:57.232,0:15:01.352

And then very quickly We have accessibility

0:15:01.352,0:15:07.882

built in, This is huge, not only because I personally love accessibility

0:15:07.882,0:15:11.032

but because it’s an important dimension,

0:15:11.032,0:15:17.412

of that success criteria. Now if you were if you were lucky enough to actually

0:15:17.412,0:15:21.332

get into the… One of the first sessions we had, I believe it was

0:15:21.332,0:15:26.302

keynote, Adam. We had the director of accessibility for Microsoft

0:15:26.742,0:15:33.422

and that dude was absolutely brilliant in in discussing, not just the importance

0:15:33.422,0:15:36.032

but the need to sort of shift left

0:15:36.032,0:15:40.542

accessibility testing and to make sure that that’s included as well.

0:15:40.542,0:15:43.242

In your grand scope. Again,

0:15:43.242,0:15:47.732

That’s why your platform matters so much. We’re gonna talk a little bit more about

0:15:47.732,0:15:52.162

accessibility in just a moment. But what I like to talk about

0:15:52.162,0:15:55.212

at this point is to make sure that, you don’t, forget

0:15:55.212,0:15:58.892

it This is something that you want to get in.

0:15:58.892,0:16:03.142

In your sites as soon as possible.

0:16:03.142,0:16:07.812

And again, letting that sort of success criteria or metric

0:16:07.812,0:16:11.612

help dictate the type of platform that you’re gonna be using

0:16:11.612,0:16:16.042

to conduct that test. Now C again just gets to

0:16:16.042,0:16:19.182

just get to brag on home team for just a minute.

0:16:19.182,0:16:22.672

We do have the ability to be able to generate

0:16:22.672,0:16:24.862

these types of results where

0:16:24.862,0:16:29.592

that accessibility concern is fully

0:16:29.592,0:16:34.382

fully considered. So this is where color contrast

0:16:34.382,0:16:37.872

issues with issue issues with

0:16:37.872,0:16:40.392

the two colors that might be presented

0:16:40.392,0:16:44.432

on a specific element are gonna be able to be surfaced and presented

0:16:44.432,0:16:48.922

very easily for your team whether it’s developers or the actual Qa team,

0:16:48.922,0:16:51.382

touch target size. Again,

0:16:51.382,0:16:55.962

you don’t wanna come back. Right? You don’t wanna, you know, have

0:16:55.962,0:17:00.362

have a ticket dictate where accessibility fits

0:17:00.362,0:17:03.922

into your testing criteria, you want to shift left.

0:17:03.922,0:17:08.712

And test early and test often, and certainly have a platform

0:17:08.712,0:17:10.612

that can support you doing that.

0:17:11.332,0:17:15.342

I see that. We’re we’re almost out of time. That’s okay. We still have

0:17:15.342,0:17:18.542

a few more things to talk about, and it’s the big

0:17:18.542,0:17:21.842

elephant in the room about holy cow billy,

0:17:21.842,0:17:25.012

That was really cool, but it’s still very manual. How am I going?

0:17:25.012,0:17:29.982

To, you know, drive the maturity of my mobile mobile testing

0:17:29.982,0:17:34.472

So that yes, I am including accessibility,

0:17:34.472,0:17:36.482

but how do I scale that out?

0:17:36.482,0:17:40.222

You know, if we’re thinking about the perm of devices,

0:17:40.222,0:17:44.062

scope that that can dictate your testing

0:17:44.062,0:17:47.622

there’s a lot. Right? You know, if if we’re just looking at…

0:17:47.622,0:17:50.642

Ios. Right? Maybe maybe there’s folks

0:17:50.642,0:17:54.562

using ios twelve, and then we have all the newest ones. Now

0:17:54.562,0:17:57.642

four each one, maybe there’s six of those.

0:17:57.642,0:18:02.612

I am not a mathematician, but I already know that the matrix grows

0:18:02.612,0:18:05.132

with again, the scope,

0:18:05.132,0:18:07.952

of the type of testing that you wanna do of

0:18:07.952,0:18:11.342

especially with all these devices out there. So

0:18:11.342,0:18:15.742

humans have leaned on automation,

0:18:15.742,0:18:20.502

Now, again, it’s so important for your team to be able to

0:18:20.502,0:18:23.732

have a platform that supports stat because

0:18:23.732,0:18:28.482

for the folks that are further along with the maturity, you might already have something like

0:18:28.482,0:18:33.422

App. You might already be using something like Appian to

0:18:33.422,0:18:35.462

do your mobile test it.

0:18:35.812,0:18:40.782

Is awesome. We’re so familiar with it, but you also again

0:18:40.782,0:18:43.552

want to be able to leverage

0:18:43.552,0:18:48.102

platform that that that doesn’t butt it out. Right? That it’s a compete

0:18:48.102,0:18:52.742

for its attention that more complements what you might be using there

0:18:52.742,0:18:55.192

and and that’s where again

0:18:55.192,0:19:00.162

Covid is able to provide a platform for you to be able to do that

0:19:00.162,0:19:02.122

with writing a lot of coat.

0:19:02.122,0:19:05.142

Is that is another teammate.

0:19:05.142,0:19:08.762

Right? And who… And again, is that a qa teammate

0:19:08.762,0:19:12.772

or is in a developer who’s running this automation.

0:19:12.772,0:19:17.662

And and Ko is able to give yes for both answers because

0:19:17.662,0:19:21.792

these steps that we saw earlier, Right? I installed the app

0:19:21.792,0:19:24.812

I tapped, get started next next then.

0:19:24.812,0:19:27.152

And I even typed in my phone number.

0:19:27.322,0:19:32.292

All of that, if that represents something that is the baseline test,

0:19:32.292,0:19:35.492

fail, all of your devices,

0:19:35.492,0:19:40.312

That’s great. But scripting it or creating automation from it,

0:19:40.312,0:19:43.662

is not as my mom said as as easily as

0:19:43.662,0:19:48.572

blowing glass and making AAA cup out of it. It’s way harder.

0:19:48.872,0:19:52.132

Don’t know why she said that she wasn’t a glass blower, but here we are.

0:19:52.132,0:19:55.632

Covid does have the answer to that solution.

0:19:55.632,0:19:58.652

And and that brings us to one of the last things I wanna talk about.

0:19:58.652,0:20:03.342

Is driving automation throughout everything that we just saw.

0:20:03.342,0:20:07.562

Everything that we just saw is presented here where each step

0:20:07.562,0:20:14.592

is its own test step that we are now translating into an automated

0:20:14.592,0:20:17.702

script. Now there’s two ways to do it.

0:20:17.702,0:20:22.402

There is super super easy, export functionality,

0:20:23.122,0:20:27.162

of an epi script. That means that if install

0:20:27.162,0:20:28.972

Get started next next next,

0:20:28.972,0:20:33.342

is the core of what you wanna test on other devices

0:20:33.342,0:20:37.022

It’s as simple as exporting that app script.

0:20:37.022,0:20:41.212

And again, the importance of a platform that plays well with your

0:20:41.212,0:20:43.792

environment in your tech stack.

0:20:43.792,0:20:48.762

Comes to show its head again here where you obviously wanna be able

0:20:48.762,0:20:52.322

to use the script The language or the framework that

0:20:52.322,0:20:57.112

you are most familiar with. You are absolutely able to do that here.

0:20:57.112,0:21:00.522

And if you are not an household,

0:21:00.522,0:21:03.752

that’s still fine because we have

0:21:03.752,0:21:08.172

the ability to rerun this test across

0:21:08.172,0:21:16.222

any of the devices in our device four. If you remember that grid showing all of our devices,

0:21:16.222,0:21:19.342

are now available here where, you know what?

0:21:19.342,0:21:22.992

That install get started next next next needs to get slapped

0:21:22.992,0:21:24.672

across other devices,

0:21:24.672,0:21:26.972

it’s as easy as selecting

0:21:26.972,0:21:30.402

which devices you want to be able to test on,

0:21:30.722,0:21:34.162

now with one more click of the button down here, rerun

0:21:34.162,0:21:38.022

have the ability to automate those steps

0:21:38.022,0:21:41.122

without again, writing a line of coat.

0:21:41.122,0:21:46.532

Now when we’re thinking about how that fits in to your tech stack

0:21:46.532,0:21:49.912

There’s a few ways to be able to to absorb it

0:21:49.912,0:21:53.922

again, you’re gonna hear a lot about K and just just more

0:21:53.922,0:21:57.332

in one second. But again, let me take a quick pause here.

0:21:57.332,0:22:00.352

Make sure we’re not the anybody behind.

0:22:00.352,0:22:04.932

And Adam don’t any anything from the chat or anything I was… Yeah There one question

0:22:04.932,0:22:08.762

that came in, that you kinda just touched on, but I think it it didn’t

0:22:08.762,0:22:13.072

coast. You can go a little deeper as essentially is Covid based on Ab.

0:22:13.072,0:22:16.242

That’s a great question. So

0:22:16.242,0:22:25.382

I’m gonna take just two seconds to talk about this. I didn’t mean to to close that. That window. I’ll start sharing again.

0:22:25.382,0:22:29.572

When we’re talking about how Covid is built

0:22:29.572,0:22:33.762

and and really what we’re able to provide when it comes to

0:22:33.762,0:22:38.732

App or that type of testing. We actually created our own App

0:22:38.732,0:22:45.252

outfit that we call X Now X axiom is running the exact same script

0:22:45.252,0:22:49.952

that you are seeing on the left with your standard at out.

0:22:50.342,0:22:54.742

And what you’re gonna see is that X axiom is going to

0:22:54.742,0:22:56.432

plead that test

0:22:56.432,0:22:59.522

two to three times faster than amp.

0:22:59.522,0:23:02.452

Now answer your question

0:23:02.452,0:23:06.612

Ex axiom is built off of the exact

0:23:06.612,0:23:10.052

same millennium web selector

0:23:10.052,0:23:14.362

as opium. Ex axiom really is just opium

0:23:14.362,0:23:19.062

stripped of all that software blue that might make it run slower.

0:23:19.062,0:23:20.642

And as you can see here,

0:23:20.642,0:23:23.362

our X c… I’m sorry, The script

0:23:23.362,0:23:27.582

running on our X axiom server, just completed

0:23:27.582,0:23:32.042

And spoiler alert, we we still have maybe

0:23:32.042,0:23:36.572

forty, fifty more seconds before Ibm completes that same

0:23:36.572,0:23:42.552

script, So not only are you getting that functionality that familiarity with

0:23:42.552,0:23:47.062

App and and, again, the S web selector and endpoints

0:23:47.062,0:23:49.212

you’re getting to be able to run it.

0:23:49.212,0:23:53.042

Substantially faster, and ostensibly

0:23:53.042,0:23:58.012

a much easier time to resolution because you’re getting

0:23:58.012,0:24:01.122

also much faster within our platform.

0:24:01.122,0:24:04.272

I think we still have twenty more seconds

0:24:04.272,0:24:07.432

on this clock before it actually finishes

0:24:07.432,0:24:10.742

just to show you how much faster our x ex,

0:24:10.742,0:24:13.972

which again is really just stripped which

0:24:13.972,0:24:16.992

of all its b and baggage

0:24:16.992,0:24:20.672

before even it finishes here.

0:24:20.672,0:24:24.352

So hopefully, that helped answer your question

0:24:24.352,0:24:28.902

we’re gonna dive right back into it. I see that we got just about five more minutes here.

0:24:28.902,0:24:32.372

We’re gonna dive back into sort of automation

0:24:32.372,0:24:36.082

and and really where C has a platform

0:24:36.082,0:24:41.572

can provide value there So if you’re keeping track, we went from

0:24:41.572,0:24:46.392

finding the scope, letting that help dictate what kind of devices you wanna

0:24:46.392,0:24:54.982

passed on. We obviously answered the question of we want performance. I Kpis and that exhaust pipe data. So we want real devices.

0:24:54.982,0:24:58.452

We want a platform that allows us to be able to test.

0:24:58.452,0:25:02.462

For the criteria that matches our Kpis and success measures

0:25:02.462,0:25:06.632

And then how can we do that at scale with…

0:25:06.632,0:25:09.882

Automation. We’re able to export

0:25:09.882,0:25:13.742

an Appian script directly from Covid here.

0:25:13.742,0:25:16.762

You’re also able to rerun those steps

0:25:16.762,0:25:20.532

in a part of our platform that we called sc list that you just saw

0:25:20.532,0:25:23.322

and and so insofar as

0:25:23.322,0:25:25.632

test coverage, taking those steps,

0:25:25.632,0:25:30.432

hitting all of your devices. And the last thing I’m gonna show you is a part of our platform

0:25:30.432,0:25:34.622

that that surfaces those results

0:25:34.622,0:25:37.642

in a way that again blends well with your tech

0:25:37.642,0:25:40.662

stack because you might have noticed Jira tucked in

0:25:40.662,0:25:45.212

all around our platform, we play well within Azure Devops

0:25:45.212,0:25:48.502

so on and so forth. But the results, right?

0:25:48.502,0:25:52.362

Cool. We got testing at scale. We also want the results.

0:25:52.362,0:25:55.742

To be able to be to provide value

0:25:55.742,0:26:01.282

to get you to your finish line and these releases much faster.

0:26:01.282,0:26:04.397

this is where I’m going to leave you

0:26:04.397,0:26:10.472

if anybody is familiar with script base or automation base testing

0:26:10.472,0:26:16.916

it is so brittle anything can break it and a lot of things, simple things do break it, namely

0:26:16.916,0:26:20.446

Like this false positive that we’re looking at here. Right?

0:26:20.446,0:26:24.686

We were looking for this paragraph. It was rendered on this

0:26:24.686,0:26:28.906

Galaxy s twenty or twenty one, and we were hoping for that

0:26:28.906,0:26:32.356

on that pixel six that I chose to test on

0:26:32.356,0:26:35.606

you can see. This isn’t really an issue. Right?

0:26:35.606,0:26:38.626

It takes… Is found and it takes

0:26:38.626,0:26:42.466

anywhere from thirty minutes to about an hour,

0:26:42.466,0:26:46.056

just for your Qa engineers or your dev,

0:26:46.056,0:26:49.466

your dev team to be able to even identify

0:26:49.466,0:26:52.726

and surface again a result

0:26:52.726,0:26:56.396

of a failed condition, but it’s just again

0:26:56.396,0:26:58.086

it false positive

0:26:58.086,0:27:01.376

this is where the platform matters. You wanna be able to

0:27:01.376,0:27:06.346

see what was originally rendered on the right, The pixel six running during twelve.

0:27:06.346,0:27:11.316

Is throwing a false positive. The platform matters here again where

0:27:11.476,0:27:15.216

we’re able to annotate these results

0:27:15.216,0:27:20.186

directly from one platform where where you might wanna set a new baseline. You could

0:27:20.186,0:27:23.596

skip this. You also have the ability

0:27:23.596,0:27:28.706

two plug right into your Ci pipeline,

0:27:28.706,0:27:32.806

So let’s throw out a ticket with all the information possible.

0:27:32.806,0:27:37.326

To those developers, if it’s there if it’s their responsibility,

0:27:37.326,0:27:40.976

again, the platform that blends seamlessly in

0:27:40.976,0:27:45.496

your in your tech stack. That’s the real pro tip folks.

0:27:45.496,0:27:49.896

Get the tool that that not just achieves what you’re looking to do,

0:27:49.896,0:27:54.236

also helps you grow and mature within your mobile

0:27:54.236,0:27:56.846

application, testing, framework.

0:27:56.846,0:28:00.496

Who? That was a lot. I get it.

0:28:00.496,0:28:03.566

I’m here for emotional support.

0:28:03.566,0:28:06.786

And also to answer any questions,

0:28:06.786,0:28:10.976

I am not going anywhere. I’m happy to hang out here.

0:28:10.976,0:28:15.466

As well. I know that we have some more great sessions coming down the pipe for you. We

0:28:15.466,0:28:16.346

but but

0:28:16.346,0:28:19.986

Yeah. Thank you for joining. Again, I’m I’m Billy Ka cabrera.

0:28:19.986,0:28:23.666

I am here with mister Adam Kramer and

0:28:23.666,0:28:27.466

we’re here to be able to answer any questions regarding

0:28:27.466,0:28:34.746

mobile application testing, automating it, manual testing, real devices,

0:28:34.746,0:28:39.536

you know, any anything else that we can certainly help the conversation

0:28:39.536,0:28:42.386

and grow and and educate where we’re here to

0:28:42.386,0:28:45.466

We’re here. So thank you so much for

0:28:45.466,0:28:48.036

for that. Adam, anything you wanted to jump in for

0:28:48.036,0:28:51.626

No. Just thank you very much. If there are any questions that you guys have,

0:28:51.626,0:28:55.116

feel free to come to our the C virtual boost or

0:28:55.116,0:28:57.786

find billy directly in the chat pane here.

0:28:57.786,0:29:01.636

Yeah. I think there’s a lot to to think about when you look at

0:29:01.636,0:29:05.976

scaling automation and collaboration and all that fun stuff and mobile and

0:29:05.976,0:29:07.486

was very helpful. Thank, Billy.

0:29:07.486,0:29:10.316

Course. Thank you for having me.

0:29:10.316,0:29:17.266

Alright. After to the next breakout sessions for everyone, we you have a discussion with

0:29:17.266,0:29:21.596

blue beam as well as one of our customers weight watchers. So

0:29:21.596,0:29:23.866

pick one of those and then we’ll see on the other side.

0:29:23.866,0:29:27.996

Gilbert, I saw you come in just at the last minute.

0:29:27.996,0:29:32.966

With forty eight more seconds go. Is there any possibility of testing a specific to device model?

0:29:32.966,0:29:37.636

With a different Os. Absolutely. When we go about sort of picking

0:29:37.636,0:29:42.366

what to test and what exactly is within scope,

0:29:42.366,0:29:46.336

is again how easy Covid is able to make that.

0:29:46.336,0:29:50.736

If again, I have my device farm with all the devices that I want,

0:29:50.736,0:29:55.196

You could see the different Os versions in the center of the screen.

0:29:55.196,0:29:57.426

If I wanted to maybe

0:29:57.426,0:30:02.126

test those steps on Android ten devices. I can

0:30:02.126,0:30:04.566

select those. And look specifically.

0:30:04.566,0:30:09.536

Could organize that based off of the type of device or resolution

0:30:09.536,0:30:15.426

or a specific bundle. So you you absolutely have the ability

0:30:15.426,0:30:19.636

to test the specific device model with a different Os.

0:30:19.636,0:30:23.306

The only gotcha on that one, Gilbert, if you’re still with me.

0:30:23.306,0:30:27.526

Is is that, you know, ios tests for Ios

0:30:27.526,0:30:32.496

Android test for Android. So that’s the only that’s the only type testing

0:30:32.496,0:30:37.076

limits, then that’s not really c tone. That’s just how we do it altogether.

0:30:37.076,0:30:41.806

So There aren’t any more questions.

0:30:41.806,0:30:46.276

Gilbert, if you want

0:30:47.830,0:30:51.480

feel free to reach out to me. Start to chat or maybe send me an email

0:30:51.480,0:30:55.860

more than happy to have this conversation. So thanks for everyone.

0:30:55.962,0:30:59.792

Please stick around. There’s a lot of great stuff to talk about and to learn.

0:30:59.846,0:31:01.556

And have a great day.