Test Run

Test Run allows you to change the state of any test case assigned to a test plan to one of four values. They are:

• passed - This is to indicate that the test case's requirements has successfully and satisfactorily been met.

• failed - This is to indicate that a test case was executed but did not pass. When a test case fails, Test Run will prompt the test engineer for a bug ID so that Test Run can more easily track what issues are related to which test cases.

• blocked - Often one test case will depend upon another. Meaning if one test case fails, then another test case couldn't possible be executed. In other words, the test case is "blocked" while some condition within the system is lifted. That being said, Test Run is not explicit about the meaning of blocked. For example, "blocked" could also mean that the test engineer assigned to the test case is on vacation, and until they return the test case cannot be run.

• not run - Just as the name implies, this test case has never been executed. Presumably though, contract to "blocked" there is nothing preventing it from being executed.

A common feature request from customers is to have Test Run support an additional field that allows them to associate a functional test ID with a test case. Understandable considering so many other tools support that field - any a million others. But supporting additional fields goes against the design philosophy of Test Run.

Test Run was design to have a much more adaptable schema by using "tags" - which provide a more free form way for each individual user to structure and organize their test cases.

Therefore, within Test Run the base way is develop a naming and tagging convention for requirements. For example, I could easily associate one more test cases with the same functional requirement identified by the string "UI-4522.2" by adding the tag "req-ui-4522.2" to each of the related cases. Because it exists as a tag, I can now easily filter and search by that tag to pull up all relevant cases.

This guide will help you migrate your test cases from Test Link to Test Run.

Step 1: Export your cases from Test Link

To export your cases from Test Link follow the following steps:

1. Click "Edit Test Case(s)"
2. Select the folder that contains the test cases you want to export
3. Click "Export All Test Suites" or "Export Test Suite"

Step 2: Upload the File

1. From the Test Cases menu in Test Run, click "Import/Export".
2. Upload the file exported in the steps above.
3. Click "Import from Test Link"

Step 3: Preview changes

Test Run will preview for you all the test cases it will import. This is your last chance to make any changes. Unselect test cases you don't want to import and then click "Import from Test Link."

Your test cases will then be in Test Run and you can add them to test plans you create.

Many users ask us "what is Markdown?" It is a question that sometimes surprises us because it is something we have simply learned to take for granted around here. There is a reason that many wikis, and many web 2.0 products all support markdown... you see Markdown makes writing HTML almost brain dead.

The 'm' in HTML stands for "mark up." Mark up refers to the practices of encapsulating text in a set of "tags" that looks a lot like XML. These tags indicate to web browsers how the text should appear - allowing users to style their text like they would in a word processor. However, HTML is far more difficult than a word processor.

Markdown is the opposite of mark up. Markdown utilizes a very logical and intuitive formatting technique that makes as much sense when viewed simply as plain text as it does when it is converted to HTML. Markdown makes writing HTML easy, and we promise, there is not a lot of geeky, hard to remember rules or syntax to follow.

For example, let's say you want to create a bulleted list. In HTML, it would look like this:

<ul>
   <li>Foo</li>
   <li>Bar</li>
   <li>Baz</li>
</ul>

But in markdown the same list is written like this:

* Foo
* Bar
* Baz

And here's the kicker... they are both rendered by your web browser to look exactly the same. Just like this:

• Foo
• Bar
• Baz

Test Run allows users to use Markdown when writing their test cases so that their test cases are both easy and quick to write, but all also easy and quick to read. Both in Excel and online.

To learn more about Markdown, visit its homepage.

In order to use the markdown syntax for your test cases you must enable the syntax for your account. To do this:

1. Click the "Test Cases" tab
2. Click the "Edit Options" button at the top of the screen (if you do not see this button it is because you do not have permission to edit your account's settings - contact your Test Run system administrator)
3. Selecting "Markdown" as your preferred syntax

And markdown should now work.

The list of product names in Test Run is derived by creating a list of all the unique product names in any given account.

Therefore, to delete a product from the database, simply remove all references to that Product Name. When no test case in the system is assigned to Product "X", then product "X" will automatically disappear from the Product pull-down menu.