TDriven Frequently Asked Questions

Why should someone use this site?

It is the cheapest, easiest, and fastest way to GET STARTED testing a website. Unlike the more complete (and complex) ways to test, we help you get to know the basics.
Quality, quality, quality. It can mean the difference between users staying with your site or leaving. It can mean getting good results and not bad ones, and can really help reduce customer service requests.

Discovering problems early can also make a big difference in how much effort it takes to fix them. Here is a table from Code Complete by Steve McConnell reproduced from Wikipedia :
Cost to fix a defect Time detected
Requirements Architecture Construction System test Post-release
Time introduced Requirements 5–10× 10× 10–100×
Architecture 10× 15× 25–100×
Construction 10× 10–25×

Fixing bugs doesn't just bring more quality, it makes the development process cheaper and faster too.
Hold your horses, Tex! With those "free" frameworks you will still need to learn them, right? That might take hours, days, or weeks. That is one of the main reasons that some people don't do any testing: it takes so long to learn, write, and update scripts that it is just not cost-effective. With TDriven, you can literally be testing your website in minutes and get the benefits from testing you may be missing.
All you need to do is enter your domain name, some users, and crawl your site. You will have test scripts instantly written for you in Selenium and JMeter. Just run those scripts and get the results. You won't even have to write one line of a test script.
Learning testing frameworks can take a while. Once learned, it takes time to write the tests. Once the tests are written, it takes time to update them whenever the code changes.

TDriven just asks you to type in your domain URL, save, and then Crawl your site. You can even add user names and passwords so that your site is crawled as each user. It then helps you gather all kinds of information about your site without manually writing any tests. See the section below about the kinds of tests you can run for more information.

Who is it for?

Glad you asked! Several types of people can use TDriven. First, there are developers that may not write test scripts because they think it takes too much time. Then there are non-developers (like product managers and bloggers) that don't know how to make sure that their websites basically work before and after every publish.
Developers fall into a few categories. Maybe you test religiously already. You don't always get to start a project from scratch and may get a new project that has no tests. TDriven is a great way to start testing with no scripts.

Maybe you have a small team and think that you can't afford the resources to test. TDriven will help you get started.

You also may be thinking about a new project and want a quick overview of where it stands. TDriven will given you some simple scripts to see how stable the site is.
There are many types of non-developers. Product managers may need to have a quick way to generate tests that they can give to their developers before and after each publish so ensure there are no major problems.

Entrepreneurs and startups may have outsourced technical teams that can be given tests to run each time a milestone is hit to make sure everthing works.

Bloggers and content creators may want to verify that their numerous posts are all still ok and without problems. Small things sometimes pop-up and it's not always easy to find them.

What about the tests?

The tests below are examples to get you started with simple versions to find out where you may want to focus your efforts. They are in no way intended to be comprehensive and are in NO WAY GUARANTEED to FIND EVERY BUG on your site. It is a great way to get started and become familiar with testing though. And we really do give useful information to improve your website.
Generally an acceptance test is something you run to find out if you accept work someone else has done. It can be as simple as making sure all of the pages are present or as complex as verifying every use case, user interface, feature, etc. is certified to work properly.
It is important to make sure that a user can see their information and not any other user's information. This is not always tested and can be a big security flaw if users expect their information to be private. Add at least two users with the same role and verify that each user can only get to their own data and not the other user's data.
Sometimes two users with the same user name logged in at the same time on the same website can cause issues. Running tests concurrently with the same user name is one way to ferret out these issues.
This involves adding code to a continuous integration process so that whenever a publish is performed a series of tests are automatically run to verify that the published build is correct. Both Selenium and JMeter can be integrated into continuous integration environments. You can use TDriven to provide you with the initial scripts to use and then update them as needed.
These tests are run by developers during the development process. Sometimes they are run on the domain "localhost" with a special port number. The localhost domain, ports, and even self-signed SSL certificates are all supported by TDriven.
A website can be a very complicated application. It may involve many separate parts that all need to work together seamlessly to have the best user experience. Testing your website as a result of how its pieces are integrated can give you an insight into how users see it.
During development there are very few, if any, users on your website. But what if you launch and want to know that the site will still perform well with 10 simultaneous users? Using the JMeter script, you can change the threads to 10 and run the test. Then open another browser and see how snappy your site is. Does it perform as expected? This is similar to Performance and Stress testing, except this is meant to test your website under normal operating load conditions.
How long does it take to load a given web page. JMeter gives you a page by page report of how long each page takes to load. This is similar to Load and Stress testing, except it tests when no one else is on to bog it down. If a site doesn't perform well with no load, then that is definitely a problem.
When you get a new version of your website, how can you be sure that old bugs that were found and fixed haven't crept back in? Has you site regressed to a prior state that is buggy? You can keep old versions of your tests and, depending on what has been updated, run them again to see that everything that used to work still does.
Responsive design is a very popular technique to create a website that looks good on desktops, tablets, phones, and other devices. One way to verify that your site looks good on a given device is to make your desktop browser window the same width as the device you want to test and then run your Selenium script. Watch as each page of your site is automatically shown to you and pause the script if you see an issue. This can be a really fast method for visually verifying your site without taking the time to click on everything.
Basic testing to make sure that your website is up a running. It is named after the process of plugging in an appliance to see if any smoke comes out. It is generally a short test that will quickly uncover problems like your site is down.
What is your website's breaking point? That is the question Stress testing is meant to address. Does it break at 50 simultaneous users? 1,000? Or only 5? Stress testing can also be used in cloud deployment scenarios to ensure that if your configuration is meant to expand on demand you can make sure it actually does. This is similar to Performance and Load testing, except this is meant to test your website under severe or maximum conditions.

What about some other info that I should know?

The Test Types are authorized, unauthorized, and skip. Authorized means this user SHOULD be able to see this Site Path. Unauthorized means this user SHOULD NOT be able to see this Site Path. Skip means that NO TEST should be run with this Test User and this Site Path.
These are used for Anonymous users to your site. These are the vast majority of web traffic that have not logged in. This is created for you and cannot be deleted. They can be Unauthorized or Skipped though.
Some other testing sites run tests for you so they have limits based on what package you sign up for. TDriven tests are exported as Selenium or JMeter files that you run on your own computer. Since you can run them on your own computer as often as you like they are considered "unlimited".