Use cases

Here are some examples of customers’ frequent use cases for requesting QA/Test services through the Test Urbis platform.

Execute periodical regression testing

Scenario

The customer plans to release the next version of an existing application in a few months. Development is ongoing and it is very important that all the changes made in the new version do not impact the existing features. In order to ensure that, on a periodical basis (every Monday to Tuesday), the entire suite of the test cases available the current version must be executed, and the test results are analyzed to detect any anomalies. Any issues detected by the internal test team are directly reported to the development team to be further triaged internally and eventually bugs/issues will be created by the project team.
It is also expected that close to the release milestone, the regression testing period will be reduced, from weekly to at least bi-weekly execution.

The internal test team does not have the resources to execute the entire regression test suite in one day, a suite that consists of hundreds of manual test cases, covering both functional and non-functional test cases.

The investigation and research directed the product team to the Test Urbis platform, where their requirements can be addressed in a simple way, with no worries regarding the external resources allocation and management, and with an efficient way to monitor the test activities executed on-demand.

Preparation

The customer contacts us, providing information about their needs and requirements. A legal agreement is completed and we hand-off the customer a subscription key, covering “Manual test cases execution” services. The subscription does not specify a fixed number of hours contracted by the customer, but only a price x per hour. The platform operator – Arnia Software, will send monthly invoices for the services executed. Daily progress and effort spent is tracked by the customer in the online platform anytime needed.

Next, the customer registers its organisation and creates user accounts for the organisation.
In the last preparation step, the customer registers the subscription online, using the provided key, and now the customer is ready to use it to create requests for the Test Urbis QA/Test team.

Implementation and execution

The next steps that are done in the platform are:

The customer creates a Test project, specifying details about the application that will be tested and other relevant information for the QA/Test team: where the app is accessible for testing, test accounts, where and how to report the anomalies discovered, what combinations of operating systems and browsers will be used for testing, where is the list of the regression test cases that must be executed and how to escalate any blocking situation (such as when the application website is down etc.). The subscription field will contain the subscription previously registered.
The customer sends for validation the Test project to the QA/Test team. After examining the data entered by the customer, the QA/Test team confirms that the information specified in the Test project is complete and sets the status of the Test project to Active.
The customer creates a Test run for the project. It adds all the information needed by the QA/Test team to run the regression tests and report the results as expected. Not the least, the customer will specify the requirements for when to run the tests – Monday to Tuesday. The same validation workflow as for the Test project activation is done also for the Test run. As part of validating the data entered by the customer, the QA/Test team also confirms its availability to execute and finish this activity on Monday. When all is done, The Test run becomes Active.
On Monday, the QA/Test team executes the test cases regression suite. The results and the time spent by the team is registered on the platform. The customer is automatically notified when the activity is marked as Complete; the execution progress information was available all the time ever since the work started.
To repeat this activity whenever needed again, all the customer has to do is to use the “Duplicate Test run” feature. At a click of a button a copy of the existing Test run will be created, and the customer will need to update just a few fields – execution requested start and end date.

As you can see, most of the work had to be done just once, by preparing the organisation platform account and setting up the initial activity details. After that, by re-using the existing data, new similar test runs can be prepared in a matter of minutes.

Execute exploratory testing

Scenario

The customer is close to releasing a new software product – a web application which was tested regularly in house during the development, has a test automation suite which is executed every night and also for each important code checkin. Overall, the customer is satisfied with the quality of the application and is confident that no major issues will be encountered after the public release.
However, as the risk of a failure or a late discovery of a flaw would be hard to mitigate after the public release, the customer wants to do some more thorough testing, this time using external QA/Test specialists and not using predefined test cases scenarios.

The internal investigation and research done directed the customer to the Test Urbis platform, where this requirement for performing exploratory, out-of-the-box testing can be fully satisfied by our highly skilled and experienced QA/Test team.

Preparation

The customer contacts us, providing information about its needs and requirements. A legal agreement is completed and we hand-off the customer a subscription key, covering “Exploratory manual testing” services. The subscription does not specify a fixed number of hours contracted by the customer, but only a price x per hour. The platform operator – Arnia Software, will send an invoice at the end of the month for the services executed. Daily progress and the effort spent is tracked by the customer in the online platform anytime needed.
Next, the customer registers its organisation and creates user accounts for the organisation.

In the last preparation step, the customer registers the subscription online, using the provided key, and now the customer is ready to use Test Urbis to create activity execution requests for the platform QA/Test team.

Implementation and execution

The next steps that are done in the platform are:

The customer creates a Test project, specifying details about the application that will be tested and other relevant information for the QA/Test team: where the app is accessible for testing, the test accounts, where and how to report the anomalies discovered, what combinations of operating systems and browsers will be used for testing and how to escalate any blocking situation (such as when the application website is down etc.). The subscription field will contain the subscription previously registered.
The customer sends for validation the Test project to the QA/Test team. After examining the data entered by the customer, the QA/Test team confirms that the information specified in the Test project is complete and sets the status of the Test project to Active.
The customer creates a QA Activity, of type “Exploratory manual testing”, for the project. It adds all the information needed by the QA/Test team to run the exploratory testing and report the results. The customer will also specify the time window requirements – when to execute this activity – requested start and end dates. The same validation workflow as for the Test project activation is done also for the QA Activity. As part of validating the data entered by the customer, the QA/Test team also confirms its availability to execute and finish this activity on the requested time period. When all is done, the QA Activity becomes Active.
The QA/Test team performs the requested exploratory testing, covering many more functional and non-functional scenarios than the ones executed in-house. It includes accessibility testing, security testing, internationalization and localization testing and other special types of testing. The results and the time spent by the team is registered on the platform. The customer is automatically notified when the activity is marked as Complete; during all the time since the QA Activity execution started the customer was able to check the progress status online.

The same type of testing can be re-executed later if the customer needs it. The data stays in the platform and it can be used also to ask for other QA/Test services to be performed by our QA/Test team.

Design and create test cases

Scenario

The customer is developing a new web application. The planning and design phase is complete, and also the first few months of development are done. So far, testing was done in the house, mostly ad-hoc, without following predefined scenarios and focusing less on regression testing and more on testing the new functionalities added in each Sprint.

As the product is getting more and more complex every Sprint iteration, the current approach for testing it is no longer scalable and satisfactory. The customer wants to be able to:

Do proper regression testing.
Create the premises to develop a test automation suite.
Complete the few available internal testing resources with external specialized resources, by outsourcing some of the QA/Test activities.

While searching online for QA/Testing services providers, the customer discovered the Test Urbis platform. It decided to test it, even with the limitations coming from the trial setup, for 30-days. The customer registered its organisation and created the user accounts. It also created some Test projects, some Test runs and QA Activities, to understand how the platform works and if it is the best solution for the job.

Before the trial period expired (which would lead to automatic all trial data erasure from the platform), the customer decided that it will use Test Urbis to outsource some of the testing activities that needs to be performed for the new product.

Preparation

The customer contacts us, providing information about its needs and requirements. It also told us about the trial data already entered in the platform and asked if that data must be re-entered again after buying a subscription. A legal agreement is completed and we hand-off the customer a subscription key, covering “Test cases design” services. The subscription specifies a fixed number of hours contracted by the customer – 80 hours, with a fixed price x per hour. The platform operator – Arnia Software, will send an invoice at the end of the month for the services executed. Daily progress and the effort spent can be tracked by the customer on the online platform all the time.

Very important for the customer, the already entered trial data is not wasted. After registering a valid subscription in the system, the trial data is no longer erased automatically, and the test organisation becomes a standard organisation type. This is done automatically by the platform.

Implementation and execution

The next steps that are done in the platform are:

The first thing the customer does is to do some data cleanup. The Test projects, the Test runs and the QA activities which were created during the trial period are no longer needed and relevant, so the customer proceeds to delete them, one by one, to have a clean setup in place. Also, the customer performs some data updates on the organisation information and on the user accounts. The inquiries and the notifications originating from the trial data are also deleted manually.
The customer creates a Test project, specifying details about the application for which the test cases will be created, providing relevant information for the QA/Test team: application design documentation, where the app is available for testing, the test accounts, where and how to setup the newly created test cases and how to escalate any blocking situation. The subscription field will contain the subscription previously registered.
The customer sends for validation the Test project to the QA/Test team. After examining the data entered by the customer, the QA/Test team confirms that the information specified in the Test project is complete and sets the status of the Test project to Active.
The customer creates a QA Activity, of type “Test cases design”, for the above Test project. In the QA Activity the customer adds all the information needed by the QA/Test team to create the test cases and report the deliverables. The customer will also specify the requirements for when to execute this activity – requested start and end dates. The same validation workflow as for the Test project activation is done also for the QA Activity. As part of validating the data entered by the customer, the QA/Test team also confirms its availability to execute and finish this activity on the requested time period. When all is done, the QA Activity becomes Active.
The QA/Test team creates the test cases for the product, covering the types of functional and non-functional testing types requested by the customer. The deliverables and the time spent by the team is registered in the platform. The customer is automatically notified when the activity is marked as Complete; during all the time since the QA Activity execution started the customer is able to track the progress online.

If the customer decides to add later more test cases or to update the existing ones, it will create a new QA Activity of the same type for the same Test project; a new subscription will be required. The existing data stored in the platform does not expire unless the customer explicitly decides to be removed.

Do you need new or updated functionality to address your specific requirements? Do you have any questions or want to get in touch with our team?

If you do, please don’t hesitate to contact us.