NB: The plans are paid in Ubertesters on an organization basis, one plan include one organization. We recommend you to create the projects under one organization to avoid extra payment.
You will be given two options there:
NB: the option is only available for the organization’s owner and admins.
To start working on a project you need to invite your team. The number of members that can be added depends on your plan.
You would be required to add the following details:
If you would like the organization member to join your project, please do the following:
Note: ‘Manager’ option is available starting from ‘Start Up’ plan.
When the member is added to organization, you can manage his role in your projects.
Owner is the person who created the organization. He has an access to all the Ubertesters functionality.
The owner has the right to:
Admin is an organization member who has the same rights as the account owner. The only exception is that the admin cannot remove an account owner from the account.
Member is an organization user who has no access to billing and do not have right to delete the organization or its members.
On the project level, admins and members can be granted the following roles:
Manager – has the same rights as Admin, but on the project level. He has the right to:
QA, Developer – do not have access to Administration section. They cannot delete project, start builds, add new members or check the member’s list.
Beta tester – is project member whose access to the project is limited to the reported feedback only. On the mobile device, he can only report feedback.
Usually this role is granted to the external testers, beta testers or other members who should not have access to project details or resources.
Now it is possible to notify the members of your project about the additions made in the issues. You can select one of the following ways of notifications: watching, non-watching and ignoring.
You can change your notification type set in your account by clicking on the notification icon at the right upper corner of the page. Select one of the provided variants and it will be saved automatically.
An organization is a set of projects on different platforms united by a common business-goal.
NB: The plans are paid in Ubertesters on the organization basis, one plan includes one organization.
You can add the organization’s logo, title and description in the organization profile. Please do the following to access it:
Note: this option is available for organization owner and admins only.
To start working with Ubertesters platform, it is required to add the members to your organization.
You would be required to add the following details:
Please note that you would be required to add the organization members to each project separately.
NB: This option is available for organization owner and admin only.
When the member is added, you can manage his role in organization and your projects.
Owner is the person who created the organization. He has an access to all the Ubertesters functionality.
The owner has the right to:
Admin is an organization member who has the same rights as the account owner. The only exception is that the admin cannot remove an account owner from the account.
Member is an organization user who has no access to billing and do not have right to delete the organization or its members.
On the project level both, the admins and members can be granted the following roles:
Project Manager – has the same rights as Admin, but on the project level. He has the right to:
QA, Developer – do not have access to Administration section. They cannot delete project, start builds, add new members or check the member’s list.
Beta tester – is project member whose access to the project is limited to the reported feedback only. On the mobile device, he can only report feedback.
Usually this role is granted to the external testers, beta testers or other members who should not have access to project details or resources.
If you decide to leave an organization or pass the billing management to another person, you can transfer the ownership to one of your organization members.
To start the testing process, you are required to upload the build to Ubertesters so it becomes available for the download on mobile devices.
Once the build is confirmed, it will be shown as Pending. Start the build to make it active.
When the build is outdated or you have released a new one, it is possible to close it. To close the build:
The closed builds are kept in your account as ‘Closed’. You can easily re-start the build in the following way:
The permissions to access the build are granted when the build is started, but can be edited any time you like. You can give access to the new members and revoke it from others.
To grant access, please do the following:
In the first case the members who were granted an access to the build will get an email notification that the new build is available for testing.
It is possible to modify the build title and notes even when the build is uploaded to Ubertesters. For this purpose, please do the following:
When the build is outdated and closed, you can delete it from the account to get the free space for new builds.
Note: this option is available for managers only.
Ubertesters allows you to connect third-party bug tracker to your account and push the reported issues there. If you are using Jira to manage bugs and issues, you can integrate it with Ubertesters system in the following way:
Ubertesters allows you to connect a third-party bug tracker to your account and push the reported issues there. If you are using Youtrack to manage bugs and issues, you can integrate it with Ubertesters system in the following way:
Ubertesters allows you to connect a third-party bug tracker to your account and push the reported issues there. If you are using Mantis to manage bugs and issues, you can integrate it with Ubertesters system in the following way:
Ubertesters allows you to connect third-party bug tracker to your account and push the reported issues there. If you are using Redmine to manage bugs and issues, you can integrate it with Ubertesters system in the following way:
To integrate Redmine with Ubertesters, please do the following:
Ubertesters allows you to connect a third-party bug tracker to your account and push the reported issues there. If you are using HP Quality Center to manage bugs and issues, you can integrate it with Ubertesters system in the following way:
Ubertesters allows you to connect a third-party bug tracker to your account and push the reported issues there. If you are using Unfuddle to manage bugs and issues, you can integrate it with Ubertesters system in the following way:
When the Unfuddle is connected, the following page will be displayed.
To integrate your project with Anasa, please do the following:
To generate Personal Access Token in Asana account, please do the following:
Make sure you’ve copied the token to secure place as you won’t see it again.
To integrate your Trello account you’ll need to do the following steps:
To get Trello key and API token please do the following:
The screen with Asana details will appear and you’ll be able to push the bugs from the ‘Issues’ section.
Once you’ve connected your bug tracker to Ubertesters, you can push the issues reported by the testers to it. The issues can be pushed in the following way:
Ubertesters bug tracker allows you to do the following:
Read more about it in the ‘Bug submission and management’ section.
Ubertesters allows to create the issues directly from the web-interface. The following fields are available:
To create the issue, please proceed with the following steps:
You can edit the reported issues depending on your needs. For this purpose, please do the following steps:
If you would like to add the additional info or leave some notes to the developers, you can comment on the issue.For this purpose, please do the following:
When clicking on the ‘Issues’ tab in your Project menu, you will get the full statistics of the reported issues. We have made the selections: by severity, by status, and by issue type. There is also information about the number of all reported issues, opened&closed issues, issues reported by you and assigned to you, not assigned, etc.
If you would like to check the issues with the particular status, type, reporter etc, you can use Advanced search. When you are on the ‘Issues’ page, please click on the ‘Advanced search’ option.
You will be redirected to the screen where you can select the parameters you need and click on ‘Apply’ to see the results. If you would like to use a search query for multiple times, you can save it by clicking ‘Save query’. Click on ‘Reset’ if you would like to change the search parameters.
The reason for the error message you get is because every time there is a new build uploaded, you must change the build number.
Otherwise it recognizes the build as one that already exists.
Please change the new build number.
Yes, the build size restriction is 1 G.
When issues are pushed to JIRA, the system looks up the emails of the members in JIRA and Ubertesters with aim of connecting the appropriate ones. So if you have a reporter registered in Ubertesters with the same email that he registered in JIRA, it should set him as a reporter. If such an email was not found, our system uses the default email and reporter – the one that was used to connect JIRA.
With Ubertesters you can track all the reported issues with the help of notification system. The email notifications can be configured in a convenient for users way.
There are three notification statuses
Watching – the user with such a status gets the email notification each time somebody reported an issue or edited it in Ubertesters account. The admins and managers get this status by default
Non-watching – the user will gets the email notifications about the updates in the issues he’s involved in. (the issues he created, edited or commented on).
Ignoring – the user is not getting the email notifications about the updates in any issues of the project. The notification status is set on the project level. You can set different statuses for different projects.
Build devices
These devices belong to team members who have been granted access to install this build.
Project devices
The list shows all devices that belong to team members that haven’t been granted the permissions for testing this build. Set the permissions to ‘On’ if you would like them to install the build.
Known devices
This list shows provisioned devices that belong to Ubertesters members who are not in the project team. You can add these members to the project team and grant them permission for testing this build.
Unknown devices
This list shows provisioned devices UDIDs that aren’t connected with any Ubertesters member. Please ask the member to register in Ubertesters system.
Get in touch, fill out the form below, and an Ubertesters representative will contact you shortly to find out how we can help you.
Want to see the Ubertesters platform at work? Please fill out the form below and we'll get in touch with you as quickly as possible.
Fill out a quick 20 sec form to get your free quote.
Please try again later.