In this video we'll be covering a lot of different

types of tests that you can use to give your company a high quality product.

This video will mostly be a list of different techniques that you can

explore without getting too in-depth.

So I encourage you to look into some of the resources we provided below for

further reading.

We should really talk about the biggest area of expansion in quality assurance,

which is automated testing.

We've gone over this topic previously, but it's important to note again

that this is where a lot of the industry is heading currently.

Automated tests are basically automated checks to see that the software

performs correctly and that new additions don't break old features.

Instead of manually running the test we created earlier for

the RSVP app that enters some text and checks that the card has the same text.

Why not automate that in a browser testing tool like Selenium?

Now with the push of a button, we can run this test over and over again.

This is the idea behind automated testing.

If an engineer makes a change that breaks the test,

we know about it right away and can fix it.

Many automated tests every time a developer pushes some new code, and

some systems will even report bugs automatically.

[SOUND] These tests that are basically run by robots free us up to do

more important tasks, like writing more automated tests.

Another type of testing that you should start looking into,

especially when writing new tests, is to explore negative tests.

These are tests that deliberately try to break the software and look for

appropriate errors.

Think of it this way.

When you do something wrong in the software,

do you want the error to happen in the background and not tell you hwo tofix it,

or do you want to see a helpful message telling you what to do?

You'll probably remember this from our bug report example.

In our RSVP app, when we hit the Submit button without typing anything,

the app simply creates an empty card.

What it should do is put a nice red outline around the box and

tell us that we need to fill in that box before we can hit Submit.

That would be much more helpful.

Some other examples of negative tests are looking for bad URL pages in your website.

Simply type in a phony address in the browser to your site to see what happens.

I'm on the team Treehouse site right now and

I'm just gonna type in badurl up at the top.

I got a nice 404 page, page not found.

What happens on your application though?

Does it give you just a white page?

Does it give you a large error stack trace that isn't very helpful to the user?

Or does it return a helpful 404 page that

lets the user know that this page does not exist?

Security testing is a huge aspect in the QA world, especially in web applications.

Many huge, high profile security breaches have been in the news in the last few

years, such as those at Yahoo, Target and Equifax.

There are many threats to the security of your server.

So being proactive and at least keeping ahead of most common attacks will help

prevent your server from being compromised or your users' data stolen.

If you're pretty new to security testing,

it's important to pay attention to tech news and listen for issues as they happen.

OWASP, or the Open Web Application Security Project,

maintains a top 10 vulnerabilities list that you can check against to make sure

that you're always keeping these issues in mind during regression testing.

I also recommend taking a look at Burp Suite,

which includes a suite of tools that you can use to test for vulnerabilities.

But I'll admit the learning curve is a little steep here.

A newer practice that's worth looking into is Crowd Source Testing.

This is giving a handful of test cases to a crowd sourcing service

that will pay a number of users to execute those tests against your app.

This is both a good way to simulate load on a server, which we'll talk about more

in the next video, and it's also a great way to get more realistic user testing.

You'll more easily find common user problems and

identify workflow issues with this approach.

Getting people who have probably never seen this software before to use it is

a great way to take a completely unbiased approach to testing.

Since it's a pretty broad subject, I've save one more topic for

a separate video, which is low testing.

The next video will cover it in depth.