I would like to know what others are using in terms of Test Management software and how they are integrating with Ontime.

I have been looking at several large software packages like Test Complete/Test Director and some small testing management packages, etc?  I havent been really happy with what I have seen.  Too much work and not really user friendly for what I am doing which is really manual functional testing.  I would like to integrate our ontime features really as requirements and have these flow right into our testing module for the project, since after all these should be the first item a tester is testing.  You can sort of see where I am going in a sense.

I would love to also hear from Axosoft as well on how you are handling your QA, etc?  There is a gap here that Axosoft could fill with a nice testing software piece.  Automated testing is not necessary for me now.  I can use Mercury quicktest pro or something else, if I need it, but a good test management software that can bridge the gap is something that is needed.

Thanks for your help

Brian 

 

---

Thanks
Brian

Guess no one is testing or no one who does testing comes here. :) 

Anyways, I would still like to hear about other's Q/A and test integration into Ontime.

---

Thanks
Brian

Hi I use OnTime Tasks to manage my test cases. For each project I have my tasks set up to describe the tests and have been building a test repository under a general project, for use in future projects. When a test is complete I mark it so and have my filters set to not show closed tasks. When I want to run a regression test I then select my tests (tasks) and reset the start date to the test project start date and reset the due date as well. If a task has an associated defect then I have a record that there was an issue at some point and this helps me in working out a risk value.

I use HP Quality Centre (QC) for manual testing and test management, soon to add Quick Test Pro for Automated regression testing.

I am using Ontime as primarily a Defect and Feature tracking tool across a small company.

I would've liked to have used the defect tracking tool that is integrated in QC but business wise it didn't have scope the company was after.

With ontime we can track Incidents from our clients, track Features that will be included in upcomming releases and keep track of Defects or Issues.

 

Testing wise Basic defect workflow is:

1. Find a defect while running our tests in QC.

2. Enter defect in Ontime.

3. Take Ontime Defect ID and enter it against the failed test in QC.

4. When defect is resolved move Defect ID in QC to history.

5. Then close defect in Ontime. 

The process is the same for Automated and Manual testing.

All,

I have an open request in with Axosoft about this very issue.  Request# 1984 in the Requested Features.  Can't miss it since that is the only one set to "Pending Future Review".  I would love to see Axosoft tackle this space since our entire userbase is growing very tired of Quality Center.  Maybe if people generate enough interest in this topic, they may take action.  The actual testing piece of QA is the only thing keeping me from getting buy-in from upper management on swapping out Quality Center for OnTime.

My advice to Axosoft: Do you homework on the competition and add the QA testing functionality to your already impressive suite.  Then sit back and clean house.

Shane

Hi,

If you are new in Test automation then I would suggest to go for Mercury test tools say QTP, Loadrunner and Quality Center. They all come out with some good tutorials which will give you a good jump start.

 

Thanks

Raj

Also visit my site for

software testing, software testing tutorial, software testing interview questions

 

Softwareqatestings.com TelecomFYI.com

always welcome!!!

Totally agree with you Shane.  I have been working with and looking at many of the socalled solutions--Mercury, Testcomplete, etc, but have liked none of them for the size of our development company-- only 5 developers including me the developer/tester.

Thanks to all that have responded to this thread.  Seems like many of you use similar processes that I/we use now.  I just put a hold on test tools because of the time it takes to get them up and running and because I think we are better to write our own tests and then integrate in our code. Takes similar amounts of time for us, but always looking for a better solution if someone has good one for small develepment shop.

Brian

 

Brian,

 We are looking at a tool called SpiraTest.  As a small shop it is affordable and it looks like it does a lot of the same things as QualityCenter.  It's made by a company called Inflectra.  Just a suggestion for you to check out.

 

-Michele

You might also want to look at WatIn for testing web apps.

I have written a wrapper application that allows us to script a test using an xml file as input (it contains "instructions"  to WatIn, telling it what URL to got to, which controls to click, type text into, check the value of etc.).

I found this much more flexible than the standard approach where the test was "pure" c# code. For example, once I had the steps written to lodge an application for membership through our web app, I just used a perl script to read the xml and duplicate it 500 times using different names, addresses, etc. Voila - a test script that creates and lodges 500  unique membership applications.

When a test or step fails, the wrapper writes information to a log file, which is a html format file with links to the actual step in the script, the page source the failure occurred in, etc.

It would be a trivial task to hook this error reporting into OnTime using the SDK, so failures were recorded in OnTime as a defect automatically.

BTW - WatIn is free and you get the source code :-)

Well, I have experience with using Zephyr 2.0, which is the only QA test management system that integrates with defect tracking tools like JIRA and Bugzilla. Hope this could help you.

Hello Sean. Thanks for the link.  Looked at it for a second, but will give it a bigger look later.  We rely heavily on Ontime, so not sure if we can use this.

What we do is use Excel for functional testing and Ontime for the rest.  It works, well, just lacking some areas.  We were thinking to build something of this nature just for internal use and plugging it into Ontime, since ontime isnt focused on this piece at the moment.  But building takes some time and we dont have time now.

Finally, we are really too small to pay for a system like this, only 4 developers total and 1 tester, but thanks again for your input.