Signi Testing Variants

In business-critical processes, nothing is more annoying than when something "breaks". Especially in integrated solutions, the probability increases, because any component can cause a failure. A good opportunity is to upgrade any component, change their settings or change the process.

What to do?

• Write test scenarios for critical processes

• and test them on the appropriate configuration at the appropriate time.

In the case of standalone Signi, there are two options:

1. Have a company DEMO workspace under your main Signi account where you can try anything, e.g. after deploying a new version, click through the key test scenarios on already prepared data.

2. The more vigilant can test existing and new functionality ahead of time on Signi preproduction.

Test environment configuration

It is always necessary to choose a meaningful layout for the testing environment.

Variants of component testing during integration. 

In the case of integrations with or without the use of an integration service, it is necessary to find suitable combinations, e.g. for testing a newly deployed version of Signi:

1. Application Test Instance,

2. a production instance of the integration service with test metadata referring to the test DEMO workspace,

3. a production Signi with a DEMO test workspace,

or to test a new version of Signi in advance:

1. Production application instances with test,

2. a production instance of the integration service with test metadata referencing the test DEMO PRE CZ workspace,

3. pre-production Signi with DEMO PRE CZ test workspace

or for testing a new version of an integrated application:

1. production Signi with your organization's DEMO test workspace,

2. production integration service with test metadata referring to your organization's DEMO workspace and pre-production of the new version of the application,

3. pre-production with a new version of the application

4. etc.