ExpeccoNET Online Documentation en

Aus ExpeccoWiki

Inhaltsverzeichnis 1 Introduction 2 First steps 3 Navigation bar 3.1 Dashboard 3.1.1 Personal Area 3.1.2 Calendar 3.1.3 Status reports 3.1.4 Deleted artefacts (not implemented) 3.2 Requirements 3.3 Risks 3.4 Defects 3.5 Action Items 3.6 Test Cases 3.7 Meetings 3.8 Projects 3.8.1 Releases 3.8.2 Components 3.8.3 Repositories 3.8.4 State Machine 3.9 Organisation 3.9.1 People 3.9.2 Groups 3.9.3 Roles 3.9.4 Organisation (not implemented) 3.9.5 Customers 3.9.6 Locations 4 Interaction with expecco 5 Examples

Introduction

expecco and expeccoNET are two stand-alone components. expecco is a GUI application (GUI = Graphical User Interface) for test development and execution. expeccoNET is a server based apllication and accessible via web browser on the intranet or - if implemented - on the internet. Both programs can be used independently.

In case you don't need test automation and project management, you can use expecco without expeccoNET, too, by executing the test with the help of automation mechanisms available in the system. For this, expecco can be employed by the use of command line arguments without user action.

In this case you have to execute the administration of the tests/results and the monitoring of the project progress manually or use another program (e.g. cvs, svn or other source code and project management tools).

expeccoNET can also be used without expecco for project and quality management assignments. The modules for the administration of Requirements, Defects and Action Items in the periphery of projects, mile stones and product varieties is useful and reasonable even without the automatic execution of tests and the according validation of the project progress.

Both components communicate via HTTP and/or SOAP protocols and can be easily integrated into different surroundings. Due to this attribute it has been possible to integrate successful customer test programs into expeccoNET.

First steps

General information

expeccoNET enables easy handling of all inputs via the navigation bar, diverse tabs and the menu bar, being briefly explained in the following:

Navigation bar

It is used for quick access to the different modules of expeccoNET. At first we want to show you the similarities between the different modules, followed by a detailed explanation of the modules' functions.

Similarities

The options Details, Comments, Attachments and Stakeholders (see screenshot) on the menu list can be found in almost identical form at the modules "Requirements", "Defects", "Action Items", "Meetings", "Projects" and "Organisation" and are explained in the following:

Details:
Shows the compiled data in compact form, however without edit option. To make modifications with entries please select "List" and the designated entry. The well-known input mask ("Details") will open and and you can change the entries (for further information please see here).

Comments:
Can be added below the input mask by entering data. Later on you can either add them via Details (the original input mask appears) or via the according option in the menu bar.

Attachments:
Can be added to an entry in different formats (see table Import- u. Exportdateiformate nach Modul).

History (only for the modules Requirements und Defects):
Shows the modifications that have been made to a certain time from a particular user.

Stakeholders:
All changes on the modules "Requirements", "Defects", "Action Items", "Meetings" and "Projects" can be communicated to registered stakeholders.
by selecting one or more of the following options:

• Attachment added
• Attachment removed
• Comment added
• Comment removed
• Deleted
• Modified
• State changed

Dashboard

Here you can find three respectively four (if Deleted Artefacts is enabled) tabs with the following contents:

Personal Area

• Issues in your Responsibility: list of requirements, defects and action items to be edited by you (personal to-do-list)
  
• Issues Reported by You: listing of requirements, defects and action items to be edited by other group members
  
• Defects by Release: display of defects occurring after the release of a product (a software version etc.)

In the lower area you wil find a survey of:

• Requirements by Release
• Requirements by Project
• Executions by Project (not visible on the following screenshot)
  
  

Calendar

Detailed presentation of the entries named above. By clicking the particular symbol the details appear
and the current day is marked:

Status reports

• Diagram showing artefacts in the form of bar or pie charts and different color schemes
  
• An artefact can be shown with different characteristics and constraints (for a defect e.g. Owner, Priority or Responsibility)
  
• Moreover, you can add samples and define the number of columns and thus the way the grapics are to appear.
  
  

Deleted artefacts (not implemented)

Requirements

A requirement is an expectation of a product, which is defined and fixed in advance. In the survey (Requirements → List)
you can find the requirements of all projects with the following data:

• ID (alpha-numeric identifier)
• Short description
• Degree of implementation; the applied colours have the following significance:

             = Requirement not edited yet

             = Requirement partly implemented

             = Requirement completely implemented

• Type of validation (e.g. analysis, demonstration, automatic/manual test...)
• Degree of implementation; the coloured bars significate the following:

             = Validation not implemented yet/still open
   
             = Validation open

             = Validation approved/closed/frozen

• Priority (z.B. low, medium, high, highest)
• Responsible
• Date of issue
• Due Date
  
  

With the help of the buttons on top of the list you can edit single requirements by clicking the according box in the first column (e.g. Edit, Raise/Lower Priority, Renumber):

Create:

A requirement is created in the input mask (Requirements → Create)by adding a short description in the first line (summary) which can be assigned to a project, component and a responsible and refined by the following parameters:

• Requirement Type
• State
• Priority
• Due Date

To adopt the data please click on of of the "Create" options (Create respectively Create & New).

After creating the entries they can be changed later:

Requirements → List: click the designated requirement to open it → Details: the original data appear in the well-known input mask and can be modified.
To adopt the changes please click one of the "Create" options (Create or Create & New).

You can communicate all changes as well as the adding and removal of attachments or comments to registered stakeholders
by ticking the according box:

The validation of a requirement proves that the test object meets demands in practice.

The menu item Tools (Create --> Tools) allows you to convert the requirement into a defect (see screenshot), moreover you can import respectively export already created requirements in csv or xml format (see table Import- u. Exportdateiformate nach Modul)

Risks

Potential imponderabilities which may occur during a project are gathered in the risk module.

Create: The menu bar in the risks module is very similar to the requirements module, whereas the input mask is designed very simple:

Necessary information:

• Short description of the present risk
• Specification of the severity
• Allocation to a project and a responsible respectively

The Risks module offers the possibility to import and export saved files in diverse formats (see table Import- u. Exportdateiformate nach Modul).

Defects

Defects result either from requirements being converted into defects (Requirements → Tools, see above)
or from creating them in the corresponding module by entering the following data (Defects → Create):

• Defect report
• Type of defect
• Status
• Severity
• Priority (e.g. low, middle, high, highest)
• Due date

Moreover, you can assign a defect to an owner and a responsible respectively:

The overview (Defects → List) shows defects with the following details:

• ID (alphanumeric identifier)
• Defect description
• Project name
• Responsible person
• Status (e.g. Unconfirmed, ReadyforTest, In progress)
• Date of detection
• Date of resolution
• Severity (e.g. trivial, normal, minor, critical)
• Due date

All changes as well as the adding or removal of attachments and comments can be communicated to registered stakeholders by ticking the corresponding box:

Action Items

Action items are scheduled assignments which can be notified to other project members in the form of created entries.
They can be marked "private" if they are not to be communicated to other group members.

List

Shows all action items with the following details:

• ID (alphanumeric identifier)
• Issue
• Date
• Responsible
• State (e.g. Open, closed, In progress)
• Name of the project
• Priority (low,medium, high, highest)

Create:

To create an action item you have to put in the following data:

• Issue
• up-to-date status (e.g. open, in Progress, closed)
• Priority
• Date
• Participants

If you are the "owner" of the action item you can assign the responsibility to a different group member ("Responsible")

To change an existing action item ex post click the item to be changed and the well-known input mask (--> Details) pops up.
After editing the data please press Submit.

Test Cases

Find out more about test scenarios here

Meetings

Using this function (Meetings --> Create) you can propose and fix appointments for conferences in order to invite other group members.

The following details are necessary:

• Issue of the meeting
• Status (e.g. Unspecified, Rejected, In progress, Closed)
• Date & Time
• Duration
• Place
• Participants
• Responsible person

Appointments can be marked as "private" if they're exclusively determined to you (see also Action Items)

All created appointments are clearly displayed in a List. By ticking the box in front of the entry you are able to edit or delete it:

Projects

In this place upcoming projects can be managed. To create a project (Projects --> Create) the following details are essential (for further information please see First steps):

• Project name
• Project description
• Is it about a tangible product? (if so, please tick the corresponding box)
• Status (e.g. applied, approved, in progress)
• Size of the company (small, medium, large) regarding the requirements and the defects
• Start and end Date of the project
• Is it a private project? (if so, please tick the corresponding box)
• Project group
• Responsible person
• Owner (the person who created the project)
• Customer (the initiator of the project)
• Budget

Fixed projects are characterized by the following details (Projects --> List):

• Project name incl. (alphanumeric) identifier (ID)
• Responsible project group
• Responsible person
• References, i.e. all processes connected to a particular project (e.g. Releases, Risiks, Action Items)

The Tools function in the menu bar enables you to allocate artefacts from one project to another. The assignment to another project is effected with the help of the project name and its ID:

Customizing artefacts
Beyond this, you can add supplemental arrays (Projects --> Customization) to an artefact (e.g. Action Items, Defects, Meeting). Therefor, you have to select the designated artefact (e.g. "Defect"), name the additional array (e.g. "Iteration?"), choose the type (e.g. "Boolean") and click "Add":

Subsequently, the addtional array appears above the input mask. By selecting the type "Boolean" for instance an opt-in-box appears in the column "default value":

Releases

As soon as you completed parts of a project you can release them. To keep records of them in expeccoNET, the following details are necessary (see screen shot):

• Release name
• Mile Stone
• Status (e.g. Applied, Approved, In progress)
• Release number
• Start/End date
• Name of the according project
• Responsible person
• Customer
• Budget

To inform other group members of a release you can accord them a report (Releases --> Report):

Components

List

Listing of components of a particular project with the following data:

• ID (generated automatically when you Create a project)
• Name of the component
• Name of the according project
• Responsible person
• References (e.g. Requirements, Defects)

Create

To create a component you need the following input is necessary:

• Component name
• Name of the repository
• Name of the according project
• Responsible person

Repositories

List

Display of existing repositories including related ID, name of the repository and responsible person:

Create

To create a repository please enter the following details:

• Name of the repository
• Type (e.g. CVS, ClearCase, File based)
• Responsible person
• Polling Interval

State Machine

List

Listing all state events with ID, Name and Links:

Create

Capturing all state events by entering name and type of state machine (e.g. Requirements, Defects, Action Items)

Organisation

See also First steps

By selecting Organisation you can create project groups and assign roles and responsibilities to the involved people.

People

Create

To create people, e.g. new employees or project members you need to enter the following:

• User name (necessary to access expeccoNET)
• Personal data (family name, first name)
• Password (free of choice)
• Contact details (e.g. e-Mail-adress, (cell) phone number, Fax number, Skype/ICQ/XMPP user name)

List

Here you can find a listing of created people incl. ID, user name, group membership and references (e.g. Projects, Releases, Defects etc.):

Groups

Create

A project group is being created by defing the group name and a group leader (optional). Afterward. you can add members to a group and assign roles (e.g. Customer, Project manager, Test leader etc.):

List

The overview shows the created groups including the following details:

• ID
• Group name
• Members (incl. assigned roles)
• Group leader
• Projects to be executed by a particular group

Roles

List

Clear display of the roles and related members.

Organisation (not implemented)

Customers

Via this tab originators of products can be registered with the following data:

• Customer's name
• Project(s) commissioned
• Contact person
• Contact details (e.g. e-Mail adress, (cell) phone number, fax number, Skype/ICQ/XMPP user name

Locations

A location can either be a place of events (e.g. meetings) or the depository of test equipment (e.g. measures or hosts). In order to set a location you need to enter its name which will appear in the list:

The defined locations appear in the drop-down lists of meetings and instruments. As an attachment you will find a booking schedule which is to be considered when executing a test or fixing an appointment.

Interaction with expecco

also see Test Cases

Examples