STEVE KOSANOVICH: I am, in the space of five minutes time,
going to create a script, introduce myself, show you how
it works, and not get pelted by balls.
OK.
So, my name is Steve Kosanovich.
MALE SPEAKER: We can't see the slides.
STEVE KOSANOVICH: Oh, that's not good.
Is that counting?
MALE SPEAKER: Configuration counts.
[LAUGHTER]
STEVE KOSANOVICH: You know, I'm going to juggle.
MALE SPEAKER: Go.
Go.
STEVE KOSANOVICH: OK, this is really what it's all about.
QA automated testing, OK?
AUDIENCE: Stand near the mic.
STEVE KOSANOVICH: It is the last thing, the phase before
we go live.
And it's probably the most under-resourced part of this
whole testing process.
So there's new [INAUDIBLE].
We've got code-free, self-healing testing.
We're going to allow you to do testing faster and more
accurately.
And hopefully I can get through my slides.
So the fundamental aspect is record and playback, capture,
compare, and analyze.
The idea is that the lower complexity of the testing
skills will allow us to create reusable test scripts.
We're going to power QA and developers to work together.
So, with that said, Here I go.
I need a drum roll.
[HANDS DRUMMING]
STEVE KOSANOVICH: Thank you.
OK, we've loaded up the application.
I have started recording.
Obviously, we see the importance of how quickly it
takes to build the pages.
AUDIENCE: What are you buying?
Vitamins?
STEVE KOSANOVICH: I'm buying vitamins.
AUDIENCE: Sure, vitamins.
[LAUGHTER]
STEVE KOSANOVICH: OK.
So at this point, my page reloads, I've made a purchase,
now I'm going to check out.
Here we go.
The moment of truth.
I'm going to associate with where my start and end points
always got to match up.
Now, as you can see, nothing.
Wait, hold on.
AUDIENCE: Should I juggle while I'm doing this?
STEVE KOSANOVICH: What's that red thing?
AUDIENCE: [INAUDIBLE]
[LAUGHTER]
STEVE KOSANOVICH: I am juggling.
Whether you know it or not, I am still juggling.
Time?
Three minutes.
OK.
AUDIENCE: What's the topic?
[LAUGHTER]
STEVE KOSANOVICH: Juggling and automation.
It's code-free automation.
It's a way to take the burden off of your
QA and testing group.
OK, so I'm going to show you how we did.
We've created a script.
Very simple, but it's a lot of things you're going to see in
e-commerce web applications.
A simple thing such as a purchase.
There's a lot of things that go on in your webpage that,
you know, bargains, things that pop-up.
They can really disrupt your testing efforts.
So the whole purpose is that we're going to be able to
functionally test your website.
And focus on the real nuts and bolts of the application, and
ignore the things that--
screens, little pop-ups changing, things that will
disrupt your testing activities.
And I'm done.
So I created the script, I replayed it, and a couple of
the neat things that you're going to be able to see are
the differences.
And our software allows you to--
when you work at the thing that changed, if I had time,
and I wasn't sure about getting pelted--
was that you're going to see that the actual cart changed.
And so we're going to show you that little part of the aspect
of the application change, but it was an expected change.
It's empowering the QA to test the application how's it's
fundamentally going to work, and I am done.