Test Manager at a government with 10,001+ employees
Real User
2022-01-13T13:50:00Z
Jan 13, 2022
When you are considering buying something, you have to see the user interface. If you buy something that is complex, people won't work with it. Qualibrate is so easy to work with. I would probably rate the solution higher than eight out of 10 if we weren't using the on-premises version. With the cloud version, Qualibrate can look at things with you, but with the on-premises version they can't. That makes some things a little bit difficult, but because we work with defense material, it's not possible. The on-premises version is more difficult than the cloud version.
I would advise making sure that you understand the tool. You don't have to understand every aspect of it, but you need a pretty thorough understanding of its components, the playbacks, the designs, and the technical pieces that make up the solution. Our pain point was the very first phase. We were brand new to the solution. We went through some knowledge-sharing sessions with their support staff, but we really felt like we were struggling at first. Most of that was probably because we simply did not understand Qualibrate to the depth that we did in subsequent phases. So, it would be good if you could really spend a little bit of time upfront, maybe just from a sandbox perspective, and you test it, mess around with it, and get familiar with it. After that, you can start to decide and design how your solution and how your scripting should look within Qualibrate. This way, you'll avoid some of the pitfalls that we ran into. We found ourselves having to do rework over and over again, and that was simply because we learned a better way of doing it than we did initially. You can maybe test it on a smaller scale. We were so motivated to get started that we tried to run before we could crawl. We should have kind of spent a little bit more time doing that initial build-out testing. We should have made sure we were happy with the results and that we were taking the right approach. We did all this work and then went, "Oh, that's not really going to work." We then had to go back and do some redesigning. So, some upfront commitment would help there. It is fairly advanced. It has only been around for three or four years, but it does seem like a pretty mature solution. Most of it is pretty user-friendly. There are some components that I have found to be a little bit more technical and a little bit more daunting to use, but overall, it is quite easy to use as far as this kind of scripting software goes. I'm quite happy with it. I'm not overly technical, and I can understand it fairly easily. That must make it pretty good. We're not using it on a daily basis. We're still kind of in a project phase where we're still ramping up and getting all of our scripting and recording done. So, right now, everything is more in kind of a batched process or phased process. We do hope to get to the point of being able to use it for daily or near-daily testing, but we're still a little away from that. Since we've only had it in-house for seven or eight months, we're just not using it on that frequency just yet, but that is our long-term plan. There are a couple of components that we are not really using at this time. That's because they are still immature, and they have not been around very long as part of the Qualibrate solution. We'll get to those perhaps another day. We're focused on our primary use case right now. We are quite happy with the flows and scenarios and those building blocks that really represent the core of the solution for scripting and playbacks. So, we're overall quite happy with this solution at this point. Based on how it operates today, I would give it a nine out of 10.
Manager Application Delivery Management at a pharma/biotech company with 10,001+ employees
Real User
2021-03-16T00:18:00Z
Mar 16, 2021
My advice is that if you know how an application is working then reduce it on a weekly or perhaps daily basis. If you are doing this then you will very quickly understand how the system is working. The first time you record a regression test, I would advise doing it in a classroom session. In this scenario, people are doing the regression test manually and you ask them to execute the same script, but this time, start the Qualibrate recording function. People can make use of the backspace functionality and with it being recorded, it can be used the next time a regression test is needed. I suggest that you not only look at the price but also the quality. This vendor listens to you and if you have requirements or need help, they are always available and not only by phone. If required, they will visit the customer from time to time. The application is user-friendly and there is documentation available. Overall, we are really happy with it. I would rate this solution a nine out of ten.
Qualibrate Solution Expert Test Engineer Provincie Noord-Holland at Provincie Noord-Holland
Real User
2021-01-25T16:08:00Z
Jan 25, 2021
I would advise using Qualibrate as a testing tool in a DevOps organization. It's a fine product. Other solutions are also okay. Tosca is also a great solution, but in the end, Qualibrate makes us better. We don't use Qualibrate's Test Planning and test Execution Scheduling features yet, but we plan to do so this year. We are now growing from three to five licenses and management wants to know what the options are for test management and test planning so that we can schedule things for when the business wants to run the scripts. It can be every day or once a week. That's the way we plan to use Test Planning. We don't use defects at the moment because we are now organizing API management to get JIRA onboard. Our process is still growing in production. We are totally satisfied with what we now have in our possession with Qualibrate. We are very happy with the solution as it stands now.
Just try it. The only advice would be to think differently about testing and how you organize testing. It comes with an easy setup to use that business users can do. When you look at test automation and the progression testing that is ready, testing is not really an issue anymore. You can just test everything all the time, because time is not an issue. It puts a different perspective on software development. However, that is not specifically for Qualibrate, but for test automation in general. With Qualibrate, it is just so easy. Biggest lesson learnt: It can be easy to automate testing. I never expected that. Typically, automating was almost always very technical. Qualibrate made it easy to automate testing. One of the things that we were really looking for is test planning, but that is a new feature that is now there. So, that is good. Its Test Planning & Execution Scheduling features are definitely something that we want to look into using in the future. I would rate it an eight (out of 10).
Undertaking a software transformation journey is a high risk. We offer a simple yet powerful solution to minimize the risk and reduce the implementation resources up to 80%.Qualibrate is the cloud solution for SAP & web apps test automation, like Salesforce: it has the power of simplicity, customization, and integration with the most CI/CD tools. Test cases are highly reusable and easily maintainable.All you need to do is to record a Business Process: user actions, test data, and...
When you are considering buying something, you have to see the user interface. If you buy something that is complex, people won't work with it. Qualibrate is so easy to work with. I would probably rate the solution higher than eight out of 10 if we weren't using the on-premises version. With the cloud version, Qualibrate can look at things with you, but with the on-premises version they can't. That makes some things a little bit difficult, but because we work with defense material, it's not possible. The on-premises version is more difficult than the cloud version.
I would advise making sure that you understand the tool. You don't have to understand every aspect of it, but you need a pretty thorough understanding of its components, the playbacks, the designs, and the technical pieces that make up the solution. Our pain point was the very first phase. We were brand new to the solution. We went through some knowledge-sharing sessions with their support staff, but we really felt like we were struggling at first. Most of that was probably because we simply did not understand Qualibrate to the depth that we did in subsequent phases. So, it would be good if you could really spend a little bit of time upfront, maybe just from a sandbox perspective, and you test it, mess around with it, and get familiar with it. After that, you can start to decide and design how your solution and how your scripting should look within Qualibrate. This way, you'll avoid some of the pitfalls that we ran into. We found ourselves having to do rework over and over again, and that was simply because we learned a better way of doing it than we did initially. You can maybe test it on a smaller scale. We were so motivated to get started that we tried to run before we could crawl. We should have kind of spent a little bit more time doing that initial build-out testing. We should have made sure we were happy with the results and that we were taking the right approach. We did all this work and then went, "Oh, that's not really going to work." We then had to go back and do some redesigning. So, some upfront commitment would help there. It is fairly advanced. It has only been around for three or four years, but it does seem like a pretty mature solution. Most of it is pretty user-friendly. There are some components that I have found to be a little bit more technical and a little bit more daunting to use, but overall, it is quite easy to use as far as this kind of scripting software goes. I'm quite happy with it. I'm not overly technical, and I can understand it fairly easily. That must make it pretty good. We're not using it on a daily basis. We're still kind of in a project phase where we're still ramping up and getting all of our scripting and recording done. So, right now, everything is more in kind of a batched process or phased process. We do hope to get to the point of being able to use it for daily or near-daily testing, but we're still a little away from that. Since we've only had it in-house for seven or eight months, we're just not using it on that frequency just yet, but that is our long-term plan. There are a couple of components that we are not really using at this time. That's because they are still immature, and they have not been around very long as part of the Qualibrate solution. We'll get to those perhaps another day. We're focused on our primary use case right now. We are quite happy with the flows and scenarios and those building blocks that really represent the core of the solution for scripting and playbacks. So, we're overall quite happy with this solution at this point. Based on how it operates today, I would give it a nine out of 10.
My advice is that if you know how an application is working then reduce it on a weekly or perhaps daily basis. If you are doing this then you will very quickly understand how the system is working. The first time you record a regression test, I would advise doing it in a classroom session. In this scenario, people are doing the regression test manually and you ask them to execute the same script, but this time, start the Qualibrate recording function. People can make use of the backspace functionality and with it being recorded, it can be used the next time a regression test is needed. I suggest that you not only look at the price but also the quality. This vendor listens to you and if you have requirements or need help, they are always available and not only by phone. If required, they will visit the customer from time to time. The application is user-friendly and there is documentation available. Overall, we are really happy with it. I would rate this solution a nine out of ten.
I would advise using Qualibrate as a testing tool in a DevOps organization. It's a fine product. Other solutions are also okay. Tosca is also a great solution, but in the end, Qualibrate makes us better. We don't use Qualibrate's Test Planning and test Execution Scheduling features yet, but we plan to do so this year. We are now growing from three to five licenses and management wants to know what the options are for test management and test planning so that we can schedule things for when the business wants to run the scripts. It can be every day or once a week. That's the way we plan to use Test Planning. We don't use defects at the moment because we are now organizing API management to get JIRA onboard. Our process is still growing in production. We are totally satisfied with what we now have in our possession with Qualibrate. We are very happy with the solution as it stands now.
Just try it. The only advice would be to think differently about testing and how you organize testing. It comes with an easy setup to use that business users can do. When you look at test automation and the progression testing that is ready, testing is not really an issue anymore. You can just test everything all the time, because time is not an issue. It puts a different perspective on software development. However, that is not specifically for Qualibrate, but for test automation in general. With Qualibrate, it is just so easy. Biggest lesson learnt: It can be easy to automate testing. I never expected that. Typically, automating was almost always very technical. Qualibrate made it easy to automate testing. One of the things that we were really looking for is test planning, but that is a new feature that is now there. So, that is good. Its Test Planning & Execution Scheduling features are definitely something that we want to look into using in the future. I would rate it an eight (out of 10).