RE: [tosca] key_schema in TOSCA 1.3?

[Chris Lauwers <lauwers@ubicity.com>]

Yes, this is another topic we should revisit when possible. What I had in mind is for the metadata in a service template to âdescribeâ (in some pseudo-standard form) the template error that should be flagged by a validator.

 

Chris

 

From: Tal Liron [mailto:tliron@redhat.com]
Sent: Wednesday, September 18, 2019 9:43 PM
To: Chris Lauwers
Cc: Calin Curescu; tosca@lists.oasis-open.org
Subject: Re: [tosca] key_schema in TOSCA 1.3?

 

On Wed, Sep 18, 2019 at 4:22 PM Chris Lauwers <lauwers@ubicity.com> wrote:

I find that the biggest challenge is to create ânegativeâ test cases (i.e. TOSCA files with specific errors that the TOSCA parser/validator is expected to flag). Itâs challenging to automate such tests without standardizing output formats.

 

One solution could be to write all the tests in a nice dynamic language (Python?) which would make it easy to implement an output-fetching-API. So, essentially ever parser would have to write their own custom adapter for the test suite.

 

I agree that it's extremely challenging to create a test suite for a language. I would even say that it's an art form, due to the infinite complexity of possibilities. But it's not impossible to create something useful. :)