We are excited with the new release of SpiraTeam v5.3 (also including SpiraTest and SpiraPlan in case you were asking!). In this article we are going to highlight some of the enhancements in the latest version. The full list of enhancements, bug fixes and new features can be found in the release notes.(Read More)
We are busy bees this summer, and one of the most exciting new features of SpiraTest (and SpiraTeam of course) is the fact that we're adding support in SpiraTest for exploratory/session-based testing. This article outlines how this new functionality will work and explains what will be possible in SpiraTest, and what additional features will be in SpiraTeam (hint integration with Task Management!)(Read More)
Our development teams are going to be avoiding the sweltering summer heat here in Washington, DC by staying inside and cooking up some amazing new features for our products. In this blog, I thought it would be good to highlight some of the key new features coming to our product families this summer.(Read More)
In the first article in this two-part series we discussed some of the reasons why it might not be desirable to spent the time to write formal test cases. Now this might seem like heresy for a company that sells a test management system to even say this! However to recap from last time, there are some good reasons:
Please read last week's post if you want to get more backrgound on these!
Now in this week's article we're going to describing the Session-based Testing approach we took when testing SpiraTeam 5.0.(Read More)
Sometimes we get the question from prospective or actual customers - how do I use SpiraTest when I don't have time to create test cases? How do I best use my experienced testers who don't want to be treated like automatons? This is a great question and one that we struggled with internally!
During our conversations with customers we have found that a common need when using Rapise to test web applications is to be able to easily and quickly match a specific item in a grid/table of results without worrying about the order or position of the item. This article provides a neat new feature added in Rapise 4.0 to make this common task easier.
Some people think in fully-formed and eloquent prose (like Supreme Court Justices). The rest of us either think in shorter-form lists and phrases, or visually with pictures. We want to know if our users would benefit from richer integration and use of visual tools and diagrams in SpiraTeam.
We've shared two sets of mockups for revisions to test execution. This has generated great ideas from many of our customers. We want to share a concept from a customer on how one of the views for test execution could look in SpiraTest 5.(Read More)
Last week we published mockups for a revised test execution page in SpiraTest. We asked for your feedback and got lots of insightful and useful suggestions. Based on what we heard we have published a second round of mockups for you to look at.
Our designers have come up with a set of prototypes for the test execution page in the next version of SpiraTest 5 to address feedback and usability issues we have identified over the past 5 years. We need your feedback to make sure we're on the right track...
In accordance with the theme this month of user interface updates and user experience in general, we'd like to talk about some of the UI changes being made to our Rapise test automation product. These changes are based on the results of user testing and feedback from our customers. It's an interesting topic because it shows the dramatic impact the UI can have on an application.
One of the new features in the latest version of Rapise, is an integrated Web Spy, also known as a DOM Browser. It's similar to the tools already in the web browsers such as IE, Firefox and Chrome (e.g. Firebug), but unlike using those tools it has lots of nifty features for making web testing easier and also integrates directly into Rapise testing IDE so that you can code against any of the elements visible in the Spy. This article describes how to use the Spy.(Read More)
Are you looking to improve your software testing? Are you tired of writing test cases 'the old fashioned way'. This article summarizes some of the key points from our recent Webinar on Manual & Exploratory Testing. (Read More)
In this conclusion we shall see that migration to a test management or requirements management tool can be easier than it might seem initially. (Read More)
With all the Agile methods out there, how does someone with traditional waterfall or v-model experience begin to understand each? Which methods are truly Agile and which are not? What are the defining characteristics of each Agile method, as well as those not quite so Agile? What are the benefits of using each Agile method and what are some of the drawbacks? (Read More)
Extreme Programming (XP) is one of the more popular Agile Development methodologies, and for very good reason. It advocates short, rapid iterations, constant customer contribution and frequent testing. But let us consider the foundation of Extreme Programming, which is to identify all the positive aspects of software programming techniques and take them to their extreme; the idea being that you can’t have too much of a good thing. For example, if tests help find defects, why not test all the time?
If we consider Agile methods generally, (not XP specifically) to also be a combination of good ideas, XP would tell us to take those ideas to their extreme; could we do that and create “Extreme Agile Programming (EAP)”? Or would we be trying to swallow our own tail? Let’s consider some Agile principles and find out.(Read More)