Prototype validation

Prototype evaluation

After deployment of the Prototype it is necessary to validate the results. The Prototype is part of some business process that can be critical. DC should work as they worked before, along with prototype (like it doesn't exist). The results of the both executions of the business process should be compared and evaluated for some period. If the prototype usage gives satisfactory results, then business process can be upgraded to function only with the prototype solution based on ODN. It is essential that prototype stores, processes and retrieves the data from ODN so the foundation for dApps development is properly laid out. Any minor or major changes on a prototype architecture can trigger extensive costly upgrades of dApps.

Testing process

The prototype is usually designed to cover the largest possible set of executions in analyzed use case. The edge cases are usually neglected by purpose or by accident. The testing process should also be structured on that way. The first tests should cover regular non-problematic data sets. After the successful testing of the regular cases, edge cases should be evaluated and handled.

If there are any problems during testing of the edge cases than there are several approaches to resolve issues. Most common are further development or enabling additional logic controls that will not enable edge cases to come to this part of the business process. For example, if you are trying to upload a very big file and there is an error, you can do additional development to split file into set of smaller files or you can add logic control to immediately forbid user (or system) to upload big files.