Page Comparison

Username + Password (via Identy Server)
Integration via Active-Directory possible, incl. Azure AD Look-up

What is a Check? and What is a Checklist?

None. If desired, restrictions can be made directly on test object type or test object so that the checklist is not globally available after release.

The checklist settings can be used to restrict the checklist to test objects or test object types.

Via "Execute checklist" you can assign a checklist to a person.

If a checklist has been published and assigned to a test object or test object type, the checklist can be selected via "Run checklist" and after selecting the test object. Now the checklist can be started or assigned to a person.

If a checklist is released, the checklist can be changed in draft mode by selecting "Edit". If the edited checklist is then released, the next higher version is displayed in "Published". The old version is no longer displayed. Via "History", previous versions can be displayed and also brought back into edit mode via "Copy".

If a checklist is copied, no versioning is triggered. This checklist is treated as a new checklist and receives revision 1 after publication.

No. If a checklist is not assigned to a test object or test object type, this checklist is available globally, i.e. it is displayed for all test objects. A checklist is only assigned to a person when it is to be executed.

These are only displayed if the checklist has been published and a test object has been selected.

An edited checklist can be called up via the system. The data is stored in an SQL database and saved permanently. If logs are created, they are stored in the Azure Cloud and can be accessed there. It is also possible to run Testify in your own MS Azure subscription (thus in your data sovereignty) or on-premise at your premises on servers of your choice.

During a numerical check, a value is requested. When performing the checklist, the value can be entered. If a check is to be made for a setpoint, the setpoint range, consisting of upper and lower limits, can be entered in the check menu (right side). Likewise, e.g. the number of displayed decimal places can be changed here.

In the exam settings (right side, top tab) the name can be changed. Note: The changes in the exam settings are not always saved automatically. To be on the safe side, always open another tab once. The confirmation of saving is then displayed at the bottom of the screen.

User name (e-mail address), title, first name, last name, language

Used to identify and assign a user in Testify. Contact through Testify.

Depending on the selected operating variant.
A) Software as a Service (SaaS) in Testify shared Cloud (Microsoft Azure): Data is held in central Testify Cloud (MS-Azure) (Netherlands and Northern Ireland)
B) Private Cloud: Installation and hosting in a specially set up MS Azure Cloud environment (resource group), incl. possibility for backup plan
C) Client’s MS Azure Subscription: Deployment and hosting in the customer Azure infrastructure with numerous additional features, such as Azure AD connection
C) On Premise: Deployment and hosting in customer-supplied infrastructure depending on Testify System Requirements.

Yes.

Yes, geo redundancy (Amsterdam and Northern Ireland in Microsoft data centers)

Yes, see privacy policy. 

What is an Equipment type?

Equipment is a device required for testing, such as calibration equipment, voltage testers or scales.

Third-party systems are integrated via our public Rest API. In addition, there are standard connectors to the most widely used third-party systems.

Our Customer Success Team will be happy to help you and provides you with advice via office@testify.io

Yes, this is possible via "Create issue". Prerequisite: The test object was previously created via "Administration".

This can be defined individually for the area. As a rule, A is selected as high and C as low.

Issues can be reported and even processed via Testify in the integrated issue process. Within the framework of this process, various options for automation are also possible, such as the automated assignment of defined issues (issue category) to defined users or user groups, including photo documentation.

No, maintenance is defined in our general SaaS license agreements and Service Level Agreements (SLA’s) .

Notification settings can be customized via Administration -> User -> Notification settings. Here you can define for which event an (e-mail) message should be sent.

No.

The settings for the notifications can be adjusted via Administration - User - Notification settings. Here you can define for which event a message should be sent.

SaaS – License agreements in combination with Service Level Agreements (SLA’s)
For interface project additional Software Delivery Agreement

Via SaaS license agreements and Service Level Agreements (SLA’s)
Special conditions for On Premise Hosting (e.g.: license audits)

Yes, via Application Insights at Testify Shared Infrastructure.

Yes, depending on the chosen hosting variant and Service Level Agreements (SLA’s)

Via a Service Level Agreement.

The PoC is for a minimum of 3 months and a maximum of 6 months as an accompanied test phase. The following conditions apply for a transition to regular operation:

• Minimum term 12 months

• Cancellation period 3 months to the end of the month (data migration must be checked individually)

• Payment is made in advance for the selected accounting period (annual/quarterly/monthly)

What is a Role?

Furthermore: What is a User? and What is a Group?

Yes, Deployment-Pipeline according to the hosting variant and SLA in coordination with the client.

• Tablet

• Desktop-PC

• Smartphone

Yes, the Testify (Web)App can be given your own corporate design, using our white labeling options.

What is a Test object? and What is a Test object type?

• Test objects designate a unit to be tested or a unit to which a defect is to be assigned (example: ladder).

  Test object types combine test objects of the same type (example: platform ladder, single ladder, stepladder, ...)

In the "Administration" menu under Test object types. First create a test object type, then create the corresponding test objects.

In terms of audit security, test objects and test object types cannot be deleted.

Checklists can also be processed without a network connection. To do this, the data of the checklists available offline must be saved on the end device via the "Take offline" item in the task overview. The checklist(s) is/are then displayed under the "Offline data" menu item and can be started offline from there. Issues can always be created and processed offline.

Note: If you have worked offline, you must synchronize the local data on the server before exiting Testify. As long as "0" is not displayed on the "SYNCHRONIZED" tab in the "Offline data" menu item, not all data has been synchronized.