Every newly inserted template must be tested adequately. Testing often feels as a large responsibility, because a ‘go live’ may have a large impact (in all of a sudden, end-users will blindly believe that the generated contracts are reliable and adequate). For the tester, this may feel ‘uncomfortable’. Weagree has made testing very simple and reliable.
Testing roles #
It is useful to distinguish:
- for who will test: testing by the admin versus testing by the responsible end-user (to approve a ‘go live’).
- between your stage of implementation: first-time testing requires that you also review if the look & feel of the contract.
The admin must make sure that:
- no provisions are missing,
- all cross-references are correct,
- all definitions and all schedules and annexes are capable of appearing in te contract (if only conditional upon a Q&A-question),
- all Q&A-answers ‘deliver’ some answer text (e.g. a dropdown list of 30 days, 60 days, 90 days, etc.),
- wherever a Q&A-question is triggered, there is also a proper question formulated.
An end-user responsible for testing should be able to rely on the admin having tested their work adequately. The end-user should review whether:
- any conditionality or interdependency in the Q&A-questions comes out correctly. The admin should be able to indicate where in the template such conditionality or interdependency exists.
- the info on the New contracts overview is appropriate.
- with the first Weagree template, whether the contract house style is correct.
First-time: also ‘test’ the contract house style #
Based on the model contracts we received, Weagree has configured a contract house style (‘look-and-feel’), both as regards the layout of elements (cover page, type of information in headers and footers) and as regards font, indentation, numbering style etc. Feedback may relate to all aspects.
It is strongly recommended that the number of house styles remains limited. In principle, subsequent templates will be based on the configured contract house styles. Contract house styles are managed in a central place, so any required update can be done at any time (for further information, see the Contract house styles subsection of this knowledge base’s Contract automation section).
