Testify is the flexible enterprise solution for digital quality assurance of your business processes. From incoming inspection to final acceptance and beyond, you can create and manage digital checklists and workflows. You can get an overview of your business processes, implement safety and quality standards and analyze the data in the integrated dashboards.

With Testify, you can digitize all paper-based processes and documents and collaborate interactively across departments and organizations in a centralized web app. Testify is used in the following areas: production support, business process outsourcing, logistics management, quality management, risk analysis, knowledge management, process management and occupational safety.

Thanks to Testify’s digital checklists, production managers and quality managers save time and effort in issue recording and quality assurance of company processes such as maintenance, internal audits or incoming goods inspections. On average, our customers save 40% in time, paper checklists are replaced by digital checklists and the audit-proof documentation can be accessed in case of questions regarding production.

Initial training is carried out by Testify (knowledge transfer) by Key-Users defined by the company. Further training of the end-users by your company.

Yes, this is recommended by Testify. In line with the Key-User principle, we recommend that you nominate one or more employees to ensure the transfer of knowledge. Based on this, the training of your end-users can be ensured. 

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.

Tolerance ranges can be defined for the checks in a checklist (numerical checks) by specifying a lower and upper limit. In addition, action/warning limits can be defined. Thus, control chart management use cases can also be easily captured in Testify and evaluated in our dashboards.

This is possible based on an import of the variant from a previous system (SAP) in the sense of a parts list. It is relevant here to set up the test specification (checklist in Testify) in such a modular way that you receive a checklist for each variant characteristic, which you can then assign. In addition, the usability of our checklist construction kit is very simple and intuitive, which means that you can also very easily build a new checklist individually for each variant - of course, this depends on how often such a process is triggered.

• New page: When starting the checklist, only the overview of the pages is displayed. The checks for this page are only displayed when the page is selected.

• New section: The checks are assigned to a section in order to be able to make a distinction (e.g. emergency shower in section level 3). Sections can be marked as "optional" and are then not mandatory to be processed (e.g. snow clearing only if there is snow).

• New check: All checks are displayed one below the other.

It is recommended not to display the levels too nested to ensure clarity. Once a selection has been made, it cannot be undone.

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.

By Service Level Agreements (SLA’s) with proactive notification to defined Key-Users from Testify App Insights Monitoring.

Yes, about all components that could potentially affect the customer.

That depends on the classification of the business-critical components.

Start/end of the outage, reason, approach, workaround, impact

Via our intuitive Customer Service Desk, when using our SLA packages.

Yes, with the jointly defined Testify key users

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

What is an Issue? and What is an Issue categorie?

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?

Based on available features, roles can be designed individually and with fine granularity.

Pre-defined standard roles such as issue engineer, quality engineer, quality manager and testify admin are provided. Own role definitions can also be created and adapted individually.

All actions visible in the frontend (buttons, features, functions, etc.) can be individually authorized for each role. In connection with the creation of groups, we thus enable our customers to map their individual organizational structures – this functionality has already been tested with customers from various industries and of various sizes (from local players to multinational corporations).

Roles can be created individually and independently according to internal company guidelines and responsibilities.

We recommend that you define a role for a defined user group with all rights to avoid possible deadlock problems in advance. In addition, however, you can create your personal administrators with limited rights in various roles and thus map your corporate structure.

Yes, regular penetration tests are performed to ensure security.

Yes, in compliance with the Testify standard development process; in close cooperation with the client.

Further developments or customer-specific requirements are planned together with the customer in a requirements meeting and implemented in Testify Standard. Feature requests can be registered via a comfortable ticket portal if our SLAs are used. If required, the feature can be ordered after an internal refinement process. 

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

via iOS-App-Store; Android via Google-Play-Store;
alternatively via WebApp with the same functionality, e.g. in case of on-premise or client-side store restrictions

New versions will be installed in recurring intervals according to our standard release cycle (2 to 4 weeks). Thus, performance improvements are achieved and additional features are available. The basic operation does not change. Release updates are provided to the defined Key-User via our release notes in the user manual before the update.

• 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.