# Cyntegrity ALM training

Link: https://almbiomarin155.saas.microfocus.com/qcbin/?idpId=alm

Click on ALM desktop client

Domain = `RBMS`

Project = `Test_Scripts`

To reach the system, click connect.

My role is tester (not requirements author)

# Modules (in dashboard)

'MY WORK' is overview of testing statistics (defects assigned to me, active defects, runs assigned to me, tests assigned to me)

## Under Testing

- Test Resource (automation)
- Test Plan (repo of all manuals and automated tests)
- Test Lab (from where we start the test script execution)
- Test run
- Shows a list of test runs (during different executions)

## Defects

- opening defects
- closing with review

## Test plan


Test scripts


OQ = Operational Qualifications


PQ = Performance Qualifications

IQ = Installation Qualifications

Create new folder


Create new test


No one does it this way, it's done in Excel.


Refresh gets used a lot. People developing in parallel


Modify approval for approval status.


Batch approval.


Screen recorder (use this to record process)


Training videos (to replace manuals, which are sent in email)

## Example test script



Chech approval, can't be executed in '*draft*' status. The next step from '*draft*' is '*approved for routing*'


Approved


All approved test scripts have signatures


### Design steps


Three steps: *Step Name*, *Description*, *Expected*


## Test Lab

In the test lab, the test scripts are listed from the test plan module:


These tests have been routed for execution:


Check Details tab for approval


Manual Runner opens:


**Never cancel or exit!**


Only click 'End Run'. Database already created a RUNID, but will be created in database. This creates a gap in the system (missing run), and auditors will wonder what happened to the missing RUNID.

### Manual Runner


Execution date and time tells me when I executed the run. Don't have executions run over the weekend. Automated test scripts are ok overnight, but not over weekend.

Must enter text into *Actual*


This should contain the expected result. Copy + paste expected and change tense. Don't use one-word ("done", "completed", etc.)


Failed test:


## Evidence

Attach with paperclip icon:


Attachments can be for a single step, or for the entire run:


All test runs need evidence (screenshot)


## Defects


Linked defect (existing defect) or new defect

### New defect


Summary of defect (include CR, other information from Test Lab), Workflow (Type 1: typo, minor, etc., Type 2, **Type 3:** use this one because validation will check this)

This creates a new defect ID.

END RUN, and enter BioMarin ID


If we pause execution, do not resume from Test Lab. Only resume from Test Run.