Improve devfile library test

[elsony]

Existing devfile library have limited test on the parser. This item will improve the existing library test to provide a more comprehensive test.

[mmulholla]

Test of Library api's

• Commands
  • Apply (AddApply, VSCodeLuanch and VSCodeTask command to tests #342)
  • Exec
  • Composite
  • VsCodeTask (AddApply, VSCodeLuanch and VSCodeTask command to tests #342)
  • VSCodeLaunch (AddApply, VSCodeLuanch and VSCodeTask command to tests #342)
• Components
  • Container
  • Kubernetes (Add Kubernetes and Object components to library tests #495)
  • Openshift (Add Kubernetes and Object components to library tests #495)
  • Plugin (no longer needed)
  • Volumes
• Events (Add Events and Metadata tests #502)
• MetaData (blocked by : Add library writer api to set top level attributes #351) (tracking issue: Add Events and Metadata tests #502)
• Parents (Add Parent tests #510)
• Projects (Add projects and starter project to parser tests #331)
• StarterProjects (Add projects and starter project to parser tests #331)
• API errors
• Top level attributes (blocked by: Add library writer api to set top level attributes #351)

Test of schema parsing

• All attributes and errors (Add library tests: check parsing for all possible attributes and errors #303)

api and library tests to share common code (#347)

• Add new test and common code to api repo
• Add new test to library repo which uses common code from api repo.

Devfile parser

• Test calling the ParseDevfileAndValidate function with various parserArgs. Some of this is being done in the main.go example. Some of this is done, but further improvements will be tracked in this issue: Improve ParseDevfileAndValidate tests #1099
• Ensure unset booleans are set to their default values Add automation tests to verify boolean values are set and overridden properly #655

[mmulholla]

@elsony My plan is to open a new issue for each function as I add it and add a link to the table. You may want to add priorites to the table. Also need to understand what the parser supports.

[kim-tsao]

We can use the code coverage reports (once in place) to correlate what's missing: #470

[kim-tsao]

#215 (comment) is only relevant to the unit tests we have which I've captured in another issue #489

When this issue was first opened, it was intended to capture updating the tests with respect to version 2.0.0. Since then, we've had v2.1.0 and v2.2.0 which introduced new changes. I will open a new issue to track updating these tests to the new spec levels.

[kim-tsao]

The remaining tests for error scenarios will be tracked by epic: #1100