Join 34,000+ subscribers and receive articles from our blog about software quality, testing, QA and security.
 

When can we expect faster TestRail release cycles?


#1

Back in June 2016 when you were acquired by IDERA, you stated in your blog post that one of your goals:

is to further accelerate TestRail’s product development for even faster release cycles

Since then, the release velocity has slowed down so much that I wonder if it’s worth continuing with our support plan renewal.

TestRail 4.2: May 2015
TestRail 5.0: September 2015 (4 months)
TestRail 5.1: December 2015 (3 months)
TestRail 5.2: February 2016 (2 months)
TestRail 5.3: September 2016 (7 months)
TestRail 5.4: July 2017 (10 months)

TestRail 5.4 added very little aside from new server platform support - with that in mind, practically no new features have been added for 1.5 years.

Are you able to share what you’re working on so that we can make an informed decision as to whether or not to renew our support plans in the future?


#2

Troublesome that there also seems to be a tendency of Gurock not responding to messagews like this


#3

I emailed support and asked things like this. Here were the responses that I was given:

Thanks for your email! Like many software companies (e.g. such as Atlassian/JIRA), we don’t publish our roadmap publicly, as we prefer not to overpromise and underdeliver. Our team at Gurock has actually more than doubled now in the last 12 months, and we only have plans to grow and add more features and functionality to TestRail. Business itself has grown tremendously over the past year and we’re working hard to staff up in all phases of the company (product management, development, marketing, and support), and we’re working to meet the demands of our customers. I can assure you that we are actively developing new features and making changes based on customer feedback, and we’ve actually been more actively engaged in reaching out to customers to receive feedback and make actionable decisions on how to best improve TestRail (someone on your team may have even received several emails regarding surveys recently).

I pressed a bit further on the lack of much in the last release and the slow cycles and I was given a bit more:

Thanks for your email! Yes, in the last year we’ve been focused on improving our TestRail Cloud infrastructure as well as adding more platform support for TestRail Server customers, with some smaller bug fixes and usability fixes. We’ve also been working to onboard our new team members and developers to adhere to the same quality and efficiency standards that our customers have come to expect. We’ll be posting a formal update soon regarding the new TestRail Cloud infrastructure changes that we’ve been working on in that regard. In regards to new features, while I can’t provide any specifics, you will start to see some new feature/changes to TestRail very early in the new year, and then a steady flow of getting back to full feature releases with multiple releases each year. Keep an eye on our blog, as that’s the fastest way to get updates when we post about this!

Not sure if that helps, but that is the update I got when I emailed.


#4

The second response (and actually the first sentence of the initial response) is pretty much literally what they have posted in the forums… Not sure what to make of that considering the lack of responses in the forums and lack of releases.


#5

I agree. Numerous features have been requested by customers - some several years ago. Many of the requests are simple to implement - for example being able to set a testcase status back to “Untested”.

While we are happy with Testrail for now, we do expect improvement on the numerous weaknesses of the product. There’s great potential, but at this very slow release cycle rate it will take years to get even simple improvements.


#6

Yes, yes, yes, and yes. There is a difference between not wanting to “overpromise and underdeliver” and “not promising anything and also not delivering anything”.


#7

Contrary to their promise it seems after the acquisition they become slow to release new feature. Contrary to other software they are becoming a software company who release less frequently with less feature. My team started to complain that we may have made a wrong decision (I was the one who recommended) on choosing a company who does not update often and in the process ignore customer requests. We should have a plan B. Wished someone from the team at least responded in this thread. Seems they are just ignoring this. Hope my concern will prove wrong by them.


#8

Hey folks - I’ve wanted to respond to this thread for some time, but since I only started working as the Product Manager back in November 2017, it took a little while to get to grips with the backlog and develop a release cadence.

So, to answer what I interpret the question to be…

In 2018 we have already released TestRail 5.4.1 (Jan) and 5.5 (May).

We also have 2-3 more planned releases in 2018. One of which will be a major version - focusing on Enterprise features like Single Sign-on.

We may do a minor release, 5.5.1 or something like that, focusing on some bug fixes and UI enhancements.

We are also starting to think about an entirely new testing product. I’ll share more information about that when we have a more definite idea of what the initial release looks like.

I hope that satisfies some of your curiosity, and puts to bed the ideas that a) we don’t respond to messages like this and b) that we’re not delivering.

On that note however, I’m very happy to receive and where possible respond to whatever feedback you have. So please do keep posting it here and I’ll do my best to answer your questions! :slight_smile:

Cheers,
Simon


#9

Thanks Simon.

Perhaps it helps to explain the client perspective. We have been using TestRail for 6 years, and we were told “We’ve been bought out and it’s going to be great because we will have the capacity to deliver tons of new features, faster”, followed by silence for a very long time.

We were used to a particular release frequency with the previous ownership, and that had dropped off significantly since the announcement that there was a takeover.

In addition, Tobias and Dennis had been very active in these forums, and very responsive to queries raised by others. Marco (a newer member of the team who we assume was taking over from Tobias and Dennis from their forum support role) was also quite responsive, up until the end of December.

Meanwhile, we see a status update from Dennis about him and Tobias no longer being part of the company, with no formal announcement.

From this point, there has been a distinct lack of responses from Gurock staff on these forums, and there’s a ton of questions here that have gone unanswered. Perhaps it’s not scalable for the Gurock team to do so, and you’d like the community to chip in more, but that’s the behaviour we have been used to over the years.

Assumptions can easily be made without adequate communication.

With your above post in mind, we look forward to 2018 picking up where 2015 to early 2016 left off.

With regard to upcoming features, are you also planning PHP > 7.0 support? That version has been EOL’d - the last security patch is going to be released on the 3rd December (in 6 months time).

http://php.net/supported-versions.php


#10

Graham - thanks, that certainly does help explain the client perspective. Please be assured that improving our communications with the TestRail (and wider testing) community is a strong focus for the team.

PHP 7.0 support is definitely on the radar. In fact, we were just discussing that yesterday.