Summary




Objectives

This document will introduce users with XStudio’s Data Model as well as provide the basic information on how to use XStudio.


General overview

Access to XStudio is restricted to users who have suitable credentials. A login process is used to authenticate the user before he can use the system. Each user is then granted with a list of permissions.





By default, an admin account is created (at installation time).The admin has (among some others) the permission to create users. If you do not know your credentials, contact your XStudio Administrator.



XQual Studio manages all entities implied in the process of testing. This includes:
  • Users,
  • SUT (Systems Under Test),
  • Agents
  • Requirements,
  • Specifications,
  • Test,
  • Test campaigns,
  • Defect.
Each of these entities can be smoothly and conveniently organized in separate trees.



Basics

Here are the main entities managed in XStudio’s Data Model:

Entity Function
 Company Several companies will be involved in the testing process:
  • The company who deliver the product to test
  • The company who is in charge of writing the testplan
  • The company who is in charge of implementing and executing the tests
Of course, all these companies can be the same.
 User Each company have users that will be involved in the testing process as:
  • Author of the testplan
  • Test developer
  • Test operator
  • Test performer
 SUT (System Under Test)What we want to test. This can be a software or a Hardware target.
 Agent Tests can be run all locally or on any host having XAgent installed and running. All hosts with XStudio or XAgent MUST be referenced in the Agent tree.
 Requirement Features required for the SUT.
 Specification Deduced from the requirements, the specifications precisely detail each function of the SUT.
 Project A generic project.
 Task A project is made of tasks that will be spread in different sprints.
 Sprint Some tasks are associated to a sprint. An intermediate deliverable will come out of each sprint.
 Category Generally, there will be different category of tests for one single product. A Category is characterized by a unique way to run all the tests under this category.
 Test Tests are developed based on the specifications. Each test must verify one particular item of the specifications. Tests can includes different testcases.
 Campaign A campaign is a selection of tests. A campaign can be executed several time on different version of the product: these executions are called Campaign Session.
 Campaign Session A campaign session is an execution instance of a campaign. This includes results from the execution associated with specific configuration of execution.
 Defect Campaign session will highlight presence of defect in the SUT. Several failures in a Campaign Session may be due to the same defect. Analyzing of the test report allows to create this defects.



As you will see, XStudio is using a lot trees. Trees are flexible and allow managing entities a very flexible way. Each tree will be associate with a few icons:

Tree Button Action
Refresh
Expand all
Expand all exept for leaves
Collapse all
Show closed items (available for sprints, tasks and defects)
Display the previous/next page



All these icons will be used along all XStudio’s GUI. They may be associated with additional overlay icon which meaning is the following:

Overlay Represents
Create
Delete
Move
Copy
Edit
View
Initialized
Playing
Paused
Stopped
Open
Add
Remove
Search
Select
Special item (read-only)
Move to the right
Move to the left
Move up
Move down
Show items (available for closable items such as sprints, tasks or defects)



XStudio’s GUI is based on a simple and clean design:
  • A left panel including a tree
  • A right panel:
    • showing information concerning the element selected in the tree
    • proposing a toolbar allowing the user to execute some specific actions on the element selected in the tree.