Table of Contents

Custom fields

Theory: Reading the User Guide

What are custom fields?, Custom fields

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Custom fields create two custom fields with the following parameters:

Custom field #1 (for test object)

• Label: [firstname]_serial number

• Identifier: [firstname]_serial number

• Data type: String

• Data field: off

Custom field #2 (for issue)

• Label: [firstname]_issue

• Identifier: [firstname]_issue

• Data type: String

• Data field: off

Question and thoughts

Are additional custom fields needed?

→ Think about the structure and additional information required. If known, create additional fields at the same time.

Test object types

Preparation

Basic 2 (Management) | Custom fields must already be completed for this module.

Theory: Reading the User Guide

What is a Test object type?, Test object types

Practice: Testify

Step 1: Create test object type

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Test object types, create a test object type with the following parameters:

• Title: [firstname] Type XY

• Description: [Year]

• Save

Step 2: Assign custom fields to test object types

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Test object types, open the test object type [firstname] Type XY.

In edit mode, add and save the custom fields you created earlier:

• Test objects: [firstname]_serial number

• Issue: [firstname]_issue

Question and thoughts

Which test object types are required?

→ Think about the structure and the required test object types. If known, create additional ones at the same time.

Test objects

Preparation

Basic 2 (Management) | Custom fields must already be completed for this module.

Theory: Reading the User Guide

What is a Test object?, View test objects, Test objects

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Test object types, select the test object type [First name] Type XY and click on Test objects. There are no test objects yet, so create new test object with following parameters:

• Identifier: [desirednumber]

• Title: [firstname] Machine XY

• Description: Year of manufacture [Year]

• Details

  • Custom field [firstname]_serial number: [desirednumber]

• Icon: Add photo (top right)

• Save

Question and thoughts

Which test objects are required?

→ Think about the structure and the required test objects. If known, create additional objects at the same time.

Issue categories

Theory: Reading the User Guide

What is an Issue categorie?, Issue categories

More about issues: What is an Issue?, Issue overview, Add issue, Issue search

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Issue Categories create two issue categories with the following parameters:

Material Issue

• Title: [firstname] Material issue

Assembly Issue

• Title: [firstname] Assembly issue

• Assigned by default to: [firstname] issue engineer

Question and thoughts

Which issue categories are needed?

→ Think about the structure and the required issue categories. If known, create additional ones at the same time.

Issue sub categories

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Issue Categories, open the Issue Category [firstname] Material issue and create a subcategory with the following parameters:

• Title: [firstname] Cracks

• Assigned by default to: [firstname] issue engineer

Question and thoughts

Which issue categories are needed?

→ Think about the structure and the required issue categories. If known, create additional ones at the same time.

Issue severities

Theory: Reading the User Guide

https://testify.atlassian.net/wiki/spaces/TWN/pages/2452783191

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Issue Severities, open Severity A and rename it to "Severe".

Question and thoughts

Which severities are needed? Edit default severities if needed and add more if necessary.

Equipment types

Theory: Reading the User Guide

https://testify.atlassian.net/wiki/spaces/TWN/pages/1507360884, https://testify.atlassian.net/wiki/spaces/TWN/pages/1507164325

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Equipment types create two Equipment types with the following parameters:

Temperature probe

• Title: [firstname] Temperature probe

• Description: Temperature sensor for measuring temperature

• Active: Yes

• Custom fields: empty

Imager

• Title: [firstname] Image generator

• Description: Image giver

• Active: Yes

• Custom fields: empty

Question and thoughts

Are further Equipment types required?

→ If yes: Create further Equipment types

Equipment

Theory: Reading the User Guide

https://testify.atlassian.net/wiki/spaces/TWN/pages/1507360884, https://testify.atlassian.net/wiki/spaces/TWN/pages/1564114969

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Create the following equipment under Administration - Equipment types:

Equipment type Temperature sensor:

• Active: Yes

• Identifier: [desirednumber]

• Vendor: [anyname]

• Valid until: Today + 6 months

• Title: Temperature sensor

• Description: empty

Equipment type Image sensor:

• Active: Yes

• Identifier: [desirednumber]

• Vendor: [anyname]

• Valid until: Today + 6 months

• Title: Image generator XY

• Description: empty

Question and thoughts

Is further equipment required?

→ If yes: Create further equipment

PDF protocol profiles

Theory: Reading the User Guide

https://testify.atlassian.net/wiki/spaces/TWN/pages/1987346481

Practice: Testify

Start Testify with the following user: Key-User [firstname].admin@training.demo

Under Administration - Open PDF protocol profiles. Review the checklist and issue protocol profiles. Each Key-User should now create his own protocol with different type and with the following parameters:

• Title: e.g. Checklist protocol compact

• Type: e.g. Checklist protocol compact

• Apply time zone and settings

• Save

Create another protocol per person with the following parameters:

• Title: [firstname] Checklist protocol default

• Type: [firstname] Checklist protocol default

• Customize settings as desired

• Add different header and footer for First Page and other pages

• Add different background images for First Page and other pages

• Save

Question and thoughts

Are the standard PDF protocols sufficient?

• Review the different settings and options of all types

• If sufficient: Continue with standard PDF protocol profiles

• If no: Think concretely about the desired content and, if necessary, create additional PDF protocol profiles