The following section contains initial instructions and describes steps allowing to simplify Zebrunner adoption by your organization.
Before you begin onboarding your organization, make sure you've performed the following:
- You have a Zebrunner subscription (or a trial). You can verify your subscription in the Billing section of the workspace (Settings → Billing). If you haven’t subscribed to Zebrunner yet, check the available options.
- You are familiar with Zebrunner’s core concepts. If you discover any unfamiliar term, please refer to the documentation.
Step 1: User seats allocation#
To start, you should identify what users will need access to your organization workspace. Identifying the users will help you allocate the proper amount of seats and proceed with access management.
Please note that some subscriptions imply a certain limit of seats. If you need more seats than the limit allows, please consider upgrading your subscription.
Step 2: Providing access to users#
Now that you identified users and allocated seats for them, you can proceed with granting access to the workspace.
There are 3 ways of granting access to the workspace:
- Send invitations using users’ email addresses. In this case, users complete the account creation process themselves by following the instructions received via email.
- Create a user(s) and share with them their credentials (in a secure manner).
- Set up SSO for your organization (recommended). In this case, user credentials will not be stored on Zebrunner’s end at all, while from the user’s perspective, this access option is typically the easiest one.
By default, users belong to the Users group, lacking access to administrative actions within the workspace, but having sufficient privileges to use core Zebrunner capabilities. If required, you can define who should be promoted to the Admins group at this step. Please see the documentation on groups and permissions management to learn more on the subject.
Step 3: Define projects and members#
You’re almost ready to start using Zebrunner at full scale. The only remaining activity is defining projects. Every workspace comes with a project called Default. You can decide if you want to keep it, but alter its name and other attributes, or delete it and create a brand new one.
You may need to create multiple projects for your organization — projects in Zebrunner imply independent, standalone real-life projects that you complete.
Note that workspace users granted access to the workspace in the previous step do not automatically get access to workspace projects. Projects have their own sets of members and roles, so once you define all the projects needed, make sure to add workspace users to them.
Congratulations! You are now ready to go! In addition to the base administrative steps completed so far, it may be useful to study short orientation guidelines for working with Test Case Management and Automation Reporting.
Starting with test suites and cases#
If you are starting your test documentation from scratch, it’s a good idea to decide how it's going to be structured. Are you planning to group test cases by functionality, testing level, or type, or would you like to use any other structuring approach? Once you’ve answered these questions, you are ready to create a first test suite. After that, you will be able to start creating test cases.
If you are migrating from another test case management solution, you may simplify the process and save time by importing cases from one of the supported sources.
Once you have your test documentation in place, you are ready to proceed with actual testing using test runs.
Configuring automation reporting#
You can plug in your existing or new automation projects by configuring a reporting agent for the corresponding test framework. Once configured and executed, you’ll be able to access the results via the automation launches grid. Note that executions appear in Zebrunner in real time.
Automation executions can be simplified for less technical team members by creating a set of user-friendly launchers and performing test executions as part of your CI/CD process if needed. Traceability improvements can be achieved by linking cases and defects to executions.