Projects Overview

Projects allow you to organize your test suites 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 mark a project as a favorite by clicking on the star icon while hovering over the left side of the project title in the list view and on the right side of the title on the card view. Marking a project as a favorite changes the order of appearance of the project. All projects marked as favorites appear above the other projects.

List view:

Card view:

Additionally, in either of the views, 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

blobid5.png

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.

    blobid0.png


  • Project Code: a short name for your project, consisting of 2-6 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.

    blobid1.png


  • Description: use this field to provide extra context and additional details to anyone involved in your new project.

    blobid2.png


  • 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.

      blobid11.png

    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.

      blobid12.png

    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.

      blobid13.png


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.

N/B: Owners of a workspace can view all projects including private projects created by other users of the workspace.

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 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, Description, and Project access type.

  • Repository: Here, you'll find options pertaining to the Repository itself.

  • 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.

  • Test Run: here, you can customize various requirements and automation for Test Runs


    Also, you can choose which Test Case settings you want to have enabled and which ones are not necessary. To view a detailed list of all the fields available to you, you can click on the “All Fields” hyperlink which will redirect you to the “Fields” section of your project:



    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 obstruct 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:

Did this answer your question?