[tests] (#573) Add option to install type definitions for the unit test framework based on the project configuration

[pboychev-bcom]

Installing type definitions for the unit tests framework based on the project configuration instead of using static definitions.

Description

Based on the configuration of the project the solution will:

• Remove the default dependency on static Jasmine type definitions.
• Add dynamic dependency on the specified unit test framework type definitions, taking into consideration the specified framework, version and any explicit type definitions version.

Checklist

• I have added relevant error handling and logging messages to help troubleshooting
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation, relevant usage information (if applicable)
• I have updated the PR title with affected component, related issue number and a short summary of the changes introduced
• I have added labels for implementation kind (kind/) and version type (version/)
• I have tested against live environment, if applicable
• I have synced any structure and/or content vRA-NG improvements with vra-ng and ts-vra-ng archetypes (if applicable)
• I have my changes rebased and squashed to the minimal number of relevant commits. Notice: don't squash all commits
• I have added a descriptive commit message with a short title, including a Fixed #XXX - or Closed #XXX - prefix to auto-close the issue

Related issues and PRs

Unit test framework types are static #573

[VenelinBakalov]

@pboychev-bcom you know that I have to beg you for Release.md right :)

[Michaelpalacce]

This all can be done post the setup, when you have a structure you can play around with and change, right? Do we want things to be that configurable?

[pboychev-bcom]

This all can be done post the setup, when you have a structure you can play around with and change, right? Do we want things to be that configurable?

Not really. You can configure the testbed configuration, this is related to the type definitions made available in the transpilation process, it has affects two aspects:

• The type definitions being available in the IDE
• The types being available for transpiling the code to pure JS, after that you will have a testbed prepared you can copy the configuration from and modify for the tests execution.

[vmwclabot]

@pboychev-bcom, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 9c74545 must be signed by [email protected]

[vmwclabot]

@pboychev-bcom, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 9c74545 must be signed by [email protected]

[pboychev-bcom]

@pboychev-bcom you know that I have to beg you for Release.md right :)

Done, thanks for the reminder, Veni :)

[vmwclabot]

@pboychev-bcom, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ccab0fd must be signed by [email protected]

[vmwclabot]

@pboychev-bcom, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ccab0fd must be signed by [email protected]

[Michaelpalacce]

One small thing

[vmwclabot]

@pboychev-bcom, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ccab0fd must be signed by [email protected]

[vmwclabot]

@pboychev-bcom, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ccab0fd must be signed by [email protected]

[Michaelpalacce]

LGTM, great job

[VenelinBakalov]

@pboychev-bcom you know that I have to beg you for Release.md right :)

Done, thanks for the reminder, Veni :)

The politically correct approach to telling someone "You are annoying" :D :D