Technical Overview > Design View > Testing

Testing

You can test your database immediately. Using kinodb, there is no need to write SQL statements or to code and test input forms. Once you have told kinodb about your database, it does the rest.

As you define the objects in your database, kinodb creates them. At any time in the design process, you can start to use the database exactly as it will appear to the users.

All SQL statements are generated by kinodb’s SQL generation engine as they are required, so changes to the data structure are reflected immediately, and can be tested in the design environment, where they will behave in exactly the same way as when users access the system.

All forms are created as they are required: this means that there is no possibility of your database being out of sync with the data input and editing forms required by your application.

The development process becomes highly interactive and is so fast that you can even use kinodb in workshops where an application is built as a direct output of the requirements gathering process. The unprecedented speed of development of even complex databases means that IT departments can produce production-strength databases ready for enterprise-wide deployment in less time than is required for an initial demonstrable prototype using conventional methodologies.

Users can start entering real data into your application as soon as there’s a place to hold it: this means that users can be using the completed parts of a complex application as soon as they are developed, while additional data design and functionality are still being incorporated.

Because kinodb removes the activities that normally lead to faults in developed applications (coding complex SQL statements, designing input forms, ensuring that referential integrity is maintained and so on), the requirement for testing is vastly reduced. As you can test the operation of the components of the system during their development, design errors can be identified and fixed immediately.

Because kinodb’s metadata engine is database independent, you can develop on any supported platform for production deployment onto any other. Typically this means that a database can be developed using a low-cost development environment such as Microsoft Access before deploying to a production-strength Oracle or SQL Server platform. Of course, once you have migrated to the production platform, you can continue to develop your application there, using kinodb, if required.

See Also

Other topics in this section:

Back to Design View

Back to Technical Overview