Projects

Projects Overview

Projects allow you to organize your test suits and test cases by putting them into separate spaces in Qase, thus preventing mixing up test cases related to different areas of development. For example, if you manage and maintain a web application or website and accompanying mobile applications on iOS and Android, you can create three separate projects for the web application, iOS app, and Android app, respectively. In essence, a project is a container for all test cases pertaining to a specific app, website, etc.

To navigate to the list of your Projects, click "Projects" in the top-left corner of the workspace:

Once in the Projects view, you can choose between two layouts with the controller located in the top-right corner:

• List view:
  
• Card view:
  

In either List or Card view, you can also find the summary of each project:

• Unresolved defects that were filed during test runs in a project
• Number of test runs performed for the test cases belonging to a project
• Milestones related to a project
• Number of team members who have access to a project

List view features Menu icon where you can:

• edit Project settings (which can also be filled in when you create a new project)
• set up integrations with 3rd party tools for a project
• delete a project

New Project

Once you are ready to start a new project, hit the "Create New Project" button:

Next, you will be prompted to fill out Project settings (which can also be edited later):

• Project Name: a descriptive name for your new project.
  
• Project Code: a short name for your project, consisting of 2-10 symbols (only Latin characters and digits are allowed). Use this for nomenclature, and keep in mind that Project Code will be later added to any test cases created within that project.
  
• Description: use this field to provide extra context and additional details to anyone involved in your new project.
  
• Project Access: Projects can be made Public and Private. A Public project will be accessible to any users of the account, current, and anyone who will be joining later.
  A Private Project can follow one of the three sharing rules:
  
  1. "Add all members to this project": every current account user you've invited will gain access to the project. Every new user who will join the account later will need to be granted access to this project manually.
     
  2. "Add members from specific group": with this option selected, you'll need to choose a user group you have created before - every user that belongs to a selected user group will then gain access to your new project.
     
     
     
  3. "Don't add members": with this option, you can keep your project private for the time being and share it with others once you're ready.
     

The final step is to confirm creating a new project by hitting the "Create Project" button below - once created, you are ready to build your project up with test cases.

Project Access and Project Settings

Once a Project is created, you can still manage who can access and see it and have more control over your project in Settings.

Project Settings: when you have opened the Project, navigate to the Settings, where you will find several sections:

• General: here, you can find and edit the same properties that you defined in the creation stage - Project Name, Project Code, and Description.
• Project Access: this section allows you to see all Qase users that have access to your Project right now, their names, emails, roles, and role titles. NB: Project Access tab is only visible if your Project has been created as a Private one.
  You can also grant access to a user who hadn't had access to a project before with the "Add User" button. 
  
  Alternatively, you can revoke access from a user who currently has access to the Project:
  
• Integrations: this section lists all available integrations that you can enable for your project, with brief instructions and description for each integration provided upon clicking the "Install" button:
  
  
  
  
• Webhooks: in this section, you will find the webhooks that have been configured for this Project so far, or create a new webhook to connect Qase with another third-party solution you use.
• Environments: define the environments that will be used for future test runs; when creating a new environment, add title and slug (mandatory), as well as description and host (optional):
  
  
• Configurations: this section allows you to set up config groups for future test runs 
• Settings: here, you can customize various requirements and automation for Test Runs and Test Case Review (i.e., make a Test Case review mandatory, or automatically assign a Test Case to a user that performed a Test Run containing such Test Case). Every option has a brief description of what kind of behavior switching it on will lead to:
  
  Also, you can choose which of the default Test Case Fields you want to have available and which ones are not necessary:
  
  
  Once new settings have been selected, don't forget to hit "Update Settings" to apply changes:
  

Archiving a Project

Once a project has been completed, you might want to hide it from plain view - it should still be accessible for reference, but shouldn't be obstructing the view of the currently active projects.

For that, you can Archive your Project from the Project Settings:

And now, while in the Projects area, you can switch between viewing Active or Archived projects or view them all at once simultaneously: