<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
   <title>Test Run Blog</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/" />
   <link rel="self" type="application/atom+xml" href="http://www.runtestrun.com/blog/atom.xml" />
   <id>tag:www.runtestrun.com,2011:/blog//1</id>
   <updated>2010-05-18T21:02:04Z</updated>
   
   <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.24-en</generator>


<entry>
   <title>&quot;Dreaming about Test Run&quot;</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/testimonials/dreaming_about_test_run/" />
   <id>tag:www.runtestrun.com,2010:/blog//1.75</id>
   
   <published>2010-05-18T20:59:18Z</published>
   <updated>2010-05-18T21:02:04Z</updated>
   
   <summary>We have been floored by the customer response to the new Test Run. We have been working hard every day to make it better and better and the support we have been receiving makes this process so much fun. One...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="Testimonials" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      We have been floored by the customer response to the new Test Run. We have been working hard every day to make it better and better and the support we have been receiving makes this process so much fun. One email sent to us caught our eye especially and we just had to share it with the rest of the world:

&gt; Test Run is a product that I&apos;ve been literally dreaming about so much to the point that I almost built something like it myself. I was really stoked to see that someone shared the same vision for a quality test case execution product that is easy to use. Keep up the great work!

Seriously, kudos like this is what keeps us going. Thank you for your support and thank you everyone for choosing Test Run!
      
   </content>
</entry>

<entry>
   <title>A preview of our new web site...</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/design/a_preview_of_our_new_web_site/" />
   <id>tag:www.runtestrun.com,2010:/blog//1.74</id>
   
   <published>2010-04-12T18:09:39Z</published>
   <updated>2010-04-12T18:18:00Z</updated>
   
   <summary>We have been hard at work gearing up for our upcoming launch of Test Run 1.2. An important piece of this relaunch is to take a fresh look at everything and figure out if there is a way we could...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="Design" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[We have been hard at work gearing up for our upcoming launch of Test Run 1.2. An important piece of this relaunch is to take a fresh look at everything and figure out if there is a way we could do it better. 

This weekend was time for us to look at our homepage in a new light. We love, love, love the work our partners <a href="http://www.muledesign.com/">Mule</a> did when we launched, but we felt we could do a much better job of communicating Test Run's value, as well as help them to choose the plan that is right for them. So we took a swag at the homepage and the pricing page and want to hear what you think.

**Homepage**

<span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.runtestrun.com/blog/2010/04/12/Screen%20shot%202010-04-12%20at%2011.09.11%20AM.png"><img alt="Homepage v2" src="http://www.runtestrun.com/blog/assets_c/2010/04/Screen shot 2010-04-12 at 11.09.11 AM-thumb-455x272-21.png" width="455" height="272" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></span>

**Pricing Page**

<span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.runtestrun.com/blog/2010/04/12/Screen%20shot%202010-04-12%20at%2011.09.01%20AM.png"><img alt="Screen shot 2010-04-12 at 11.09.01 AM.png" src="http://www.runtestrun.com/blog/assets_c/2010/04/Screen shot 2010-04-12 at 11.09.01 AM-thumb-455x295-23.png" width="455" height="295" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></span>

We drew our inspiration from products we love and products we feel do an excellent job with their homepage, including:

* [Basecamp](http://basecamphq.com/) from 37signals
* [Tender](http://www.tenderapp.com/) and [Lighthouse](http://www.lighthouseapp.com/) from entp
* [Toggl](http://www.toggl.com/)]]>
      
   </content>
</entry>

<entry>
   <title>Upcoming Changes to Account Plans</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/upcoming_changes_to_account_pl/" />
   <id>tag:www.runtestrun.com,2010:/blog//1.73</id>
   
   <published>2010-03-30T06:13:32Z</published>
   <updated>2010-03-30T07:07:24Z</updated>
   
   <summary>We are very excited about the upcoming enhancements to Test Run, the test planning solution quality assurance professionals love. There are tons of new features, and we have been working hard to dramatically improve the performance, stability and overall quality...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[We are very excited about the [upcoming enhancements to Test Run](http://www.runtestrun.com/blog/news/working_on_test_run_12_-_whats/), the test planning solution quality assurance professionals love. There are tons of new features, and we have been working hard to dramatically improve the performance, stability and overall quality of the application. Lastly, to better serve the needs of our wide spectrum of customers we are making the following changes to the account plans available to our users and customers:

## New Account Level

One of the things numerous users have asked for is a subscription level that was less expensive, and geared towards smaller teams. We are happy to oblige. When Test Run 1.2 is finally released, we will be introducing "Test Run for Small Teams" for the low cost of $20 per month, an account level perfect for QA teams with 3 or fewer team members.

## Storage Limits

To account for the costs associated with storing data uploaded by our users, we have come to a point where we need to institute fair and reasonable limits on storage. When Test Run 1.2 is released we will begin monitoring and enforcing<sup>1</sup> the following storage limits:

* Free Trials will be limited to 1MB of storage.
* Test Run for Small Teams accounts will be limited to 1GB of storage.
* Test Run Pro accounts will be limited to 10GB of storage.

All existing users will be able to see how much storage their account is utilizing by visiting "Your Subscription" found under the Account tab.

## 15-day Trials

Over time our ability to reasonably support a perpetual one-user free trial has become unsustainable. Therefore, we have made the difficult decision to discontinue this free *perpetual* trial once Test Run 1.2 is released.

We recognize however that in order to evaluate our product, every user must have the freedom to go beyond screenshots and screencasts and have the ability to actually use it. So while a free *perpetual* trial will be no more, we are happy to offer a **free 15 day trial**. These free trials will be limited in the following ways:

* 1 user maximum.
* 1MB storage capacity maximum.

Furthermore, users wishing to trial Test Run with multiple users can upgrade their free trial to any of the available subscription levels. No matter what however, the full 15 day free trial period will be honored and you will not be billed for the subscription level you selected until the end of your trial period. If you are not happy with Test Run during your trial, you can cancel at any time at no charge.

## Frequently Asked Questions

* Paying customers should have zero disruption to their service, and the terms of their existing subscriptions will be honored for as long as they remain active and in good standing.

* Starting with the release of Test Run 1.2, all users of the free perpetual one user trial account level will be required to upgrade their account to a paid subscription. Accommodations can be made to users wishing to export their data and cancel their accounts if they wish.

* Users who meet the requirements of Test Run for Small Teams are welcome to downgrade their accounts if they so desire.

* If you have any questions or concerns about these changes, please don't hesitate to [contact us](http://runtestrun.tenderapp.com/). We are reasonable people and will do our best to accomodate your needs.

<sup>1</sup> - To help customers with the transition of these limits we will not begin enforcing storage limits immediately. Instead, customers are encouraged to view their account details and bring their accounts into compliance with the terms of their elected service level on their own.]]>
      
   </content>
</entry>

<entry>
   <title>Follow Test Run on Twitter</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/company/follow_test_run_on_twitter_1/" />
   <id>tag:www.runtestrun.com,2010:/blog//1.72</id>
   
   <published>2010-03-20T05:07:02Z</published>
   <updated>2010-03-20T05:13:10Z</updated>
   
   <summary>Test Run has been undergoing some serious development as of late, which has given us a lot of reasons to communicate with our customers. Of course, some folks may just want to hear the &quot;big news&quot; when it is available...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="Company" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[Test Run has been undergoing <a href="http://www.runtestrun.com/blog/news/working_on_test_run_12_-_whats/">some serious development as of late</a>, which has given us a lot of reasons to communicate with our customers. Of course, some folks may just want to hear the "big news" when it is available - for those of you in that camp, this blog is perfect. But I have also found a number of people are also interested in following along with the details of the development process as well. If you are the kind of person who likes more communication from Test Run (of the 140 character variety) then <a href="http://twitter.com/runtestrun/">follow us on Twitter</a> - the perfect place to get small doses of news from the test planning product you know and love!]]>
      
   </content>
</entry>

<entry>
   <title>Working on Test Run 1.2 - what&apos;s in store</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/working_on_test_run_12_-_whats/" />
   <id>tag:www.runtestrun.com,2010:/blog//1.71</id>
   
   <published>2010-03-16T05:45:23Z</published>
   <updated>2010-03-16T06:28:18Z</updated>
   
   <summary>For the past two years I have been Test Run has been hosted under what might have seemed like a perpetual beta. Over the course of those two years, bugs were fixed here and there, but by and large no...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
      <category term="Test Run Beta" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      For the past two years I have been Test Run has been hosted under what might have seemed like a perpetual beta. Over the course of those two years, bugs were fixed here and there, but by and large no major enhancements were made. This left customers wondering:

&gt; What is going on with Test Run? And has this product completely stalled out?

A completely fair question under the circumstances. You see, Test Run was started as a side project of mine and, and to be perfectly candid, tended to play second fiddle to my day job. Loyal customers have always understood this, and for that, I will be eternally grateful. 

But my loyal customers, and indeed *all of my customers* deserve much, much more from an application that they depend on. So I have rededicated myself to this labor of love to bring an added level of quality, performance and feature enhancement to the platform. 

For the past four weeks I have been working tirelessly on improving Test Run and here are just some of the enhancements I have made:

* **Performance Boost** - As a modern web application Test Run relies upon javascript for a great deal of its functionality, therefore I have re-written and optimized all of Test Run&apos;s javascript to be slimmer, less error prone, and best of all *faster*. Navigation is snappier, dialogs open and close more smoothly, AJAX is faster, all Javascript is more lean and faster than ever before.

* **Bug Drivers** - Customers have been asking for Jira support for as long as I can remember and I am happy to report that Jira support is finally coming. Now when a test case fails you will be able to create a bug in Jira from directly within Test Run. This initial implementation may have some limitations with regards to reporting, but with customer feedback I hope to resolve those issues quickly.

* **Style Enhancements** - All dialogs are now rendered in native Javascript and share a consistent styling, and every form in the application has been redesigned with a consistent styling in order to provide the polish Test Run customers deserve.

* **Improved Support** - Sometimes, God forbid, Test Run customers have questions, and when they do, they should have the best experience possible in asking them, and having them answered. Therefore I have ditched the janky support application I have been using in favor of the best-in-class [Tender App](http://tenderapp.com/) support system. Now users will have access to a world class knowledge base and ticketing system so that in the event that things go wrong, customers have the most favorable experience possible under the circumstances.

* **Enhanced Registration** - New users will have live and inline form validation during registration to create a smooth pathway into a the free trial period.

* **Better Browser Support** - While redesigning the forms and porting the entire application to jQuery we paid special attention to ensure consistent styling among all popular browsers, including the most recent versions of Internet Explorer, Chrome, Firefox and Safari.

* **New Pricing Option for Small Teams** - Many customers have asked for a less expensive subscription offering for small teams, a request I am happy to oblige. When Test Run 1.2 is officially released, there will be three options available to customers:

  * Free 15-day trial
  * Small Team Subscription, limiting accounts to three users for just $20 per month.
  * Large Team Subscription, with unlimited users for just $50 per month.

We love all of these new enhancements and features and look forward to a steady stream of improvements to come!

## Skip to the Chase: When?

Test Run 1.2 is currently in the final stages of development, which we expect to take two to three more weeks. Once complete, customers will be invited to participate in a free and final beta testing period for several weeks. Then, Test Run will officially come out of its two year beta - a milestone I am anxiously looking forward to!
      
   </content>
</entry>

<entry>
   <title>Making use of &quot;Products&quot; in Test Run: Hierarchies anyone?</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/design/making_use_of_products_in_test/" />
   <id>tag:www.runtestrun.com,2009:/blog//1.63</id>
   
   <published>2009-02-18T18:15:40Z</published>
   <updated>2009-02-18T18:23:52Z</updated>
   
   <summary>Customers frequently ask if Test Run could one day in the future support hierarchical test cases. It is a feature that is definitely on the roadmap, but its implementation would be pretty hairy, so I have honestly been putting it...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="Design" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="67" label="feedback" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="68" label="ideas" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="70" label="testcase hierarchies" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      Customers frequently ask if Test Run could one day in the future support hierarchical test cases. It is a feature that is definitely on the roadmap, but its implementation would be pretty hairy, so I have honestly been putting it off. But it occurred to me that the feature may already exist in a latent form.

If you have used Test Run than you are familiar with a &quot;Product&quot; property associated with test cases. It is a property I added, but I never developed any *features* around because it was clear that some form of test case segmentation was needed, but it was unclear how it might be used. So this feature exists, but does not provide any benefit to users.

It occurs to me however, that this feature could easily be used to segment test cases into *test suites*. Then a slight UI change could easily be introduced to group and display test cases by test suite as opposed to in a strict reverse chronological order.

I would love to hear from users what they think of this idea and whether they currently use the Product field for anything. Let me know! 
      
   </content>
</entry>

<entry>
   <title>Follow Test Run on Twitter!</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/follow_test_run_on_twitter/" />
   <id>tag:www.runtestrun.com,2009:/blog//1.62</id>
   
   <published>2009-02-12T22:49:56Z</published>
   <updated>2009-02-12T22:51:38Z</updated>
   
   <summary>Test Run now has a Twitter account. If you want to stay up with the latest development news, follow us there!...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[Test Run now has a <a href="http://twitter.com/runtestrun">Twitter account</a>. If you want to stay up with the latest development news, follow us there!

<span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.runtestrun.com/blog/2009/02/12/twitter-logo.jpg"><img alt="twitter-logo.jpg" src="http://www.runtestrun.com/blog/assets_c/2009/02/twitter-logo-thumb-455x167.jpg" width="455" height="167" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></span>]]>
      
   </content>
</entry>

<entry>
   <title>A New Manage Test Plans Design</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/a_new_manage_test_plans_design/" />
   <id>tag:www.runtestrun.com,2009:/blog//1.61</id>
   
   <published>2009-01-07T17:27:13Z</published>
   <updated>2009-01-07T17:33:49Z</updated>
   
   <summary>I have been receiving a lot of feedback in the New Year from new customers, perhaps because people out there are looking for ways to cut costs and keep things simple. Their feedback as usual has been invaluable, and most...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="64" label="beta" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="20" label="design" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="51" label="screenshots" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="66" label="test plans" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[I have been receiving a lot of feedback in the New Year from new customers, perhaps because people out there are looking for ways to cut costs and keep things simple. Their feedback as usual has been invaluable, and most recently led me to revisit the design of the Manage Test Plans screen. The impetus for the change was to create a framework that allowed for me to surface more management functionality on the screen and to offer a more compressed layout that allows admins to take more information in more quickly and efficiently. I am not finished yet, so feedback is still welcome. Here is a before and after of the Manage Test Plans screen:

**Before**

<span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.runtestrun.com/blog/2009/01/07/Picture%205.png"><img alt="Active Test Plans: Before" src="http://www.runtestrun.com/blog/assets_c/2009/01/Picture 5-thumb-455x331.png" width="455" height="331" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></span>

**After**

<span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.runtestrun.com/blog/2009/01/07/Picture%203.png"><img alt="Active Test Plans: After" src="http://www.runtestrun.com/blog/assets_c/2009/01/Picture 3-thumb-455x251.png" width="455" height="251" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></span>

What do you think?]]>
      
   </content>
</entry>

<entry>
   <title>Redesigning Test Run Forms...</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/test_run_beta/redesigning_test_run_forms/" />
   <id>tag:www.runtestrun.com,2008:/blog//1.60</id>
   
   <published>2008-12-13T21:56:16Z</published>
   <updated>2008-12-13T22:04:41Z</updated>
   
   <summary>I have been looking and admiring a lot of other web applications recently and have paid special attention to form design. Test Run&apos;s forms have gone through multiple iterations, but none of them are as simple as I would like...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="Test Run Beta" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[I have been looking and admiring a lot of other web applications recently and have paid special attention to form design. Test Run's forms have gone through multiple iterations, but none of them are as simple as I would like them to be. I feel they require too much scrolling and they don't put the right emphasis on the right things. So I am in the process of redesigning Test Run's forms and would love to hear from customers what they think.

## Before

<span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.runtestrun.com/blog/2008/12/13/Picture%202.png"><img alt="Test Run Form (before)" src="http://www.runtestrun.com/blog/assets_c/2008/12/Picture 2-thumb-455x360.png" width="455" height="360" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></span>

## After

<span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.runtestrun.com/blog/2008/12/13/Picture%201.png"><img alt="Test Run Form (after)" src="http://www.runtestrun.com/blog/assets_c/2008/12/Picture 1-thumb-455x351.png" width="455" height="351" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></span>

Here is what I have done:

* I have place summary and description up front because those are arguably the most important fields on the page. 
* I have devoted less space to the text format radio buttons and kept them closer to the textarea box that they control.
* I have widened the summary and description fields so you can see more of what you are typing.
]]>
      
   </content>
</entry>

<entry>
   <title>Performance Tuning and Enhancements</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/performance_tuning_and_enhance/" />
   <id>tag:www.runtestrun.com,2008:/blog//1.59</id>
   
   <published>2008-09-30T17:31:29Z</published>
   <updated>2008-09-30T18:08:00Z</updated>
   
   <summary>With the slow and steady increase of customer usage of Test Run Online, the product has begun to feel a little sluggish and a number of you, my customers, had expressed their concern. On the up side, I guess that...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="59" label="features" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="60" label="optimization" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="8" label="performance" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="61" label="test run" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="63" label="text formatting" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      With the slow and steady increase of customer usage of Test Run Online, the product has begun to feel a little sluggish and a number of you, my customers, had expressed their concern. On the up side, I guess that is bound to happen when you have over a hundred thousand test cases, and five thousand test plans - surely a sign of success by some measure. But the success of Test Run should never come at the expense of paying customers, so I have turned my attention towards performance and database optimization.  

Having just completed a thorough analysis of Test Run&apos;s database architecture I will, over the course of the next several days, be rolling out a number of recommended improvements to the system. Several have already been deployed and the results are enjoyable - and difference is remarkable.

Of course, I am also working on other improvements to make Test Run more usable, and flexible. A number of users have been having difficulty with text formatting, and in working with them I realized that text formatting doesn&apos;t always make sense as a global setting. So, I just finished making text formatting, like the use of markdown and a rich text editor, a test case level setting. Now each and every test case can set its own preference for how it should be formatted. 

Other improvements are also coming, so stay tuned.
      
   </content>
</entry>

<entry>
   <title>Test Run 1.1 Beta Finally Begins</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/test_run_beta/test_run_11_beta_finally_begin/" />
   <id>tag:www.runtestrun.com,2008:/blog//1.56</id>
   
   <published>2008-04-28T06:58:57Z</published>
   <updated>2008-04-28T07:11:49Z</updated>
   
   <summary>Welcome the new version of Test Run: 1.1. Behind the scenes the product has undergone a great deal of change in the last twelve months and I am finally pleased enough with what has accumulated to release the first public...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
      <category term="Test Run Beta" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[Welcome the new version of Test Run: 1.1. Behind the scenes the product has undergone a great deal of change in the last twelve months and I am finally pleased enough with what has accumulated to release the first public beta.

## More Information about this release:

* <a href="http://www.runtestrun.com/blog/news/preparing_for_the_test_run_11/">Detailed change log</a>

## Finding Help and Reporting Bugs

* <a href="http://www.runtestrun.com/help/ttx.cgi?style=corp2">Report a bug</a>
* <a href="http://forums.runtestrun.com/">Find help from the community in our forums</a>

## Frequently Asked Questions

**I am not sure what I found is a bug, should I still report it?**

We want to hear any thoughts you may have about the application. Perhaps what you have found is not a bug, but if it doesn't work the way you want it to then something could be improved. So please, be sure to inform us if:

* an error occurs
* if the application appears slow
* you receive a javascript error
* you have a feature request

**Do you have special support for Jira and other bug tracking systems?**

Support for Bugzilla is almost complete. However before it is released, we wanted to finalize the developer interfaces between Test Run and the bug system driver with more thorough and public testing. 

Next on the list to support is Jira because of the overwhelming number of requests we have received for it.

**How long will the beta last?**

Our hope is to wrap up the beta as soon as possible.

**Can I subscribe to Test Run during the beta?**

Absolutely!]]>
      
   </content>
</entry>

<entry>
   <title>Preparing for the Test Run 1.1 Beta</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/preparing_for_the_test_run_11/" />
   <id>tag:www.runtestrun.com,2008:/blog//1.55</id>
   
   <published>2008-04-17T05:22:16Z</published>
   <updated>2008-04-17T06:14:23Z</updated>
   
   <summary>Test Run 1.1 has been in development for a very, very long time. I admit. But the pay off will be worth it as there is a lot in this release to look forward to, and virtually all of it...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
      <category term="Test Run Beta" scheme="http://www.sixapart.com/ns/types#category" />
   
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      Test Run 1.1 has been in development for a very, very long time. I admit. But the pay off will be worth it as there is a lot in this release to look forward to, and virtually all of it is the result of direct feedback from you - my users.

So, some time next week or two I hope to launch a beta of the next version of Test Run. I would like to first extend the opportunity to users of the downloadable version of Test Run to try it out and after an initial round of feedback and testing, roll it out to everyone using the online version.

If you would like to get a preview of this upcoming version of Test Run, [drop me a line](http://www.runtestrun.com/help/ttx.cgi?style=corp2), and I will happily provide you with a copy.

For a complete list of enhancements that have been made in Test Run 1.1 to date, keep reading.
      #### Test Run 1.1 Enhancements and Bug Fixes

* An import feature for Test Link which will allow people to easily migrate to Test Run from the Test Link case tracking tool.
* Test Plan printing - many users asked for the ability to print a test plan to make it easy to review plans offline.
* Rich Text Editing - several users have asked for me to integrate a WYSIWYG editor into Test Run
* Upgraded to latest version of YUI
* Updated almost all buttons and dialogs to be more consistently styled
* Redesigned the test plan header to be more condensed and generally useful
* Refactored primary navigation through out the application to use pull down menus to make easier to move from one place in the app to another.
* Added a Manage Products area
* Added tag search to &quot;Add Test Cases&quot; dialog
* Converted &quot;Add Product&quot; to javascript dialog
* Eliminated some PHP errors about undefined indexes
* Made product selection sticky
* Added ability to track when a test plan was archived - now records the date and displays the archive date in the table listing
* Fixed alignment of &quot;Forgot password?&quot; text
* Anonymous users now see proper text formatting on a test case
* Updated feedback link in footer to point to a generic end point that redirects to the proper location allowing us to more easily point installed customer base to a new location easily.
* Status of test cases in detail view now get updated when test is run
* Fixed bug where the summary field was not in focus when create/edit test case form is displayed
* Fixed bug whereby the scroll bar on the add cases dialog would not disappear reliably when dialog was closed
* Finish implementing Test Link import routine
* Made it more intuitive on how to archive a test plan
* Create test case buttons use old style
* Adding a bug that already exists does nothing
* Adding a bug that is already resolves, sets bug to proper state
* Test Run will now resolve all bugs within an account of the same Bug ID when that bug id is marked as resolved.
* Remove &quot;Your Profile&quot; - should just take user to edit profile screen
* Edit profile form is kinda borked - fixed
* Edit permissions form could use better alignment
* Bug ID is linked when it shouldn&apos;t be (when a bug url pattern is absent) in report
* Create/Edit Test Plan button in old style
* Backend logic for resolving all logged bugs with the same ID implemented

There are of course many other smaller tweaks, a number of other fixes behind the scenes to trim down the application, improve its overall design, and so forth. But I imagine most people don&apos;t really care about that stuff.

Remember, if you are interesting in testing out Test Run 1.1 Beta 1, [please let me know](http://www.runtestrun.com/help/ttx.cgi?style=corp2)!
   </content>
</entry>

<entry>
   <title>Sneak Peak of Test Run 1.1</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/sneak_peak_of_test_run_11/" />
   <id>tag:www.runtestrun.com,2007:/blog//1.54</id>
   
   <published>2007-11-16T19:40:28Z</published>
   <updated>2007-11-16T19:48:14Z</updated>
   
   <summary>I wanted to give a quick development update as we near a release of Test Run 1.1 Beta. I have nearly completed Bugzilla integration with FogBugz, but there are still a lot of kinks to work out in regards to...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="48" label="bugzilla" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="39" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="49" label="news" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="50" label="preview" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="51" label="screenshots" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[I wanted to give a quick development update as we near a release of Test Run 1.1 Beta. I have nearly completed Bugzilla integration with FogBugz, but there are still a lot of kinks to work out in regards to allowing users of our hosted product to access their private instance of Bugzilla. 

I have also been working on a number of UI tweaks to make Test Run easier to navigate and use. Without going into too much detail yet, here are a few screenshots to whet your appetite:

<span class="mt-enclosure mt-enclosure-image"><img alt="testrun-1_1b.jpg" src="http://www.runtestrun.com/blog/images/screenshots/testrun-1_1b.jpg" width="450" height="109" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;"/></span>

<span class="mt-enclosure mt-enclosure-image"><img alt="Test Run 1.1 Sneak Peak" src="http://www.runtestrun.com/blog/images/screenshots/testrun-1_1.jpg" width="450" height="192" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;"/></span>]]>
      
   </content>
</entry>

<entry>
   <title>Test Run 1.1 Development Begins</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/test_run_development/" />
   <id>tag:www.runtestrun.com,2007:/blog//1.53</id>
   
   <published>2007-09-28T18:35:57Z</published>
   <updated>2007-09-28T18:51:02Z</updated>
   
   <summary>Summer is over, the traditional slow time of the year in the software industry, and I have been getting a lot of renewed interest in Test Run. Customers have been submitting bug reports and a lot of feature requests, and...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="39" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="40" label="forums" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="41" label="import" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="43" label="new features" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="45" label="rich text editing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="47" label="test link" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[Summer is over, the traditional slow time of the year in the software industry, and I have been getting a lot of renewed interest in Test Run. Customers have been submitting bug reports and a lot of feature requests, and many of them have in all honesty gone relatively unanswered in the last several months. 

Well, that is about to change. I feel there is a critical mass of feature requests to begin working on Test Run 1.1. So last night work officially began. I have started to assess a lot of different things about the product in an effort to improve customer support and the experience around finding help. I upgraded the <a href="http://www.runtestrun.com/blog/">Test Run Blog</a> and <a href="http://www.runtestrun.com/kb/">Knowledge Base</a> to use <a href="http://www.movabletype.com/">Movable Type 4.0</a>, and I have migrated <a href="http://forums.runtestrun.com/">Test Run's forums</a> off of my <a href="http://www.majordojo.com/">personal web server</a> onto the production Test Run machines. This has the added benefit of dedicating Test Run's forums exclusively to Test Run. Users will no longer find content related to my other software projects. This is a <em>good thing</em>.

As for what features I am planning for this release:

* At the top of the list is the need to <strong>integrate with popular bug tracking systems</strong>. This feature will allow users to submit bug reports directly into <a href="http://www.bugzilla.org">Bugzilla</a> and <a href="http://www.fogcreek.com/fogbugz">FogBugz</a> from within Test Run. 
* An <strong>import feature</strong> for <a href="http://testlink.org/">Test Link</a> which will allow people to easily migrate to Test Run from that case tracking tool.
* <strong>Test Plan printing</strong> - many users asked for the ability to print a test plan to make it easy to review plans offline.
* <strong>Rich Text Editing</strong> - several users have asked for me to integrate a WYSIWYG editor into Test Run, and I will see what I can do to accommodate. 
* Naturally there will be lots of bug fixes as well.


I encourage users to submit feature requests to me (as a comment to this post if you wish) and let me know what you would like to see out of the next version of Test Run.]]>
      
   </content>
</entry>

<entry>
   <title>New features: Tag Management and Time Estimates</title>
   <link rel="alternate" type="text/html" href="http://www.runtestrun.com/blog/news/new_features_tag_management_an/" />
   <id>tag:www.runtestrun.com,2007:/blog//1.52</id>
   
   <published>2007-05-24T06:18:15Z</published>
   <updated>2007-05-24T06:32:14Z</updated>
   
   <summary>Development on Test Run continues at a fast and furious pace as we rush to keep up with all the wonderful feedback we get from customers. Most of the feedback is about a feature or two that people would really...</summary>
   <author>
      <name></name>
      
   </author>
   
      <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1" label="announcement" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="38" label="customer feedback" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="32" label="dashboard" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="26" label="new feature" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="33" label="reporting" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="34" label="tags" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="11" label="testrun" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="36" label="time estimates" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://www.runtestrun.com/blog/">
      <![CDATA[Development on Test Run continues at a fast and furious pace as we rush to keep up with all the wonderful feedback we get from customers. Most of the feedback is about a feature or two that people would really like to see. Sometimes the feedback is in regards to a bug that a user finds. And then occasionally a user will tell me something like this:

<blockquote>"I have worked at a lot of companies and have been responsible for reviewing and recommending countless test management tools. Test Run is far and away the best and simplest tool I have ever encountered."</blockquote>

God, I can't tell you how wonderful it is to get feedback like that. When it sometimes becomes really hard to create awesome software while continuing to work full time at <a href="http://www.sixapart.com/">another job</a> you also love, feedback like that picks you up and keeps you going.

And what better way to reward a growing and increasingly involved and engaged user base then with a new release of Test Run?

Tonight I am happy to announce the latest version of Test Run which contains features implemented exclusively from customer feedback. Most notably, Test Run 1.09 has the the following new features.]]>
      * *Time Estimates* - The test case property known as &quot;Difficulty&quot; has been removed and replaced with a far more useful field for collecting a time estimate from the test case creator. Time estimates will allow for a number of cool new project management features down the road, but in the short term the Resource Balancing Report has become much more useful because now an administrator can quickly see more specifically how much work is assigned to each member on their team.

* *Better Tag Management* - A number of users mentioned that they have tags that continue to lie about their installation that they have a lot of difficulty purging and cleaning up. Now Test Run allows administrators to delete and manage tags within their account from the convenience of a single console.

* *New User Tour* - Now new users of Test Run are greeted by a redesigned welcome page and dashboard designed to help them get up and running using Test Run quickly and more easily.

In addition to the above features, numerous bug fixes have been made, and a few small features have been added here and there.

Thank you again to all the users who continue to send feedback, without you Test Run would not be nearly as useful.
   </content>
</entry>

</feed>

