Create stepimplementer for NPM UT and UAT

[kharyam]

Purpose

Adding stepimplementers for NPM Unit Tests and User Acceptance Tests.

Since NPM is not standardized to the same degree as maven, the following implementation has been used:

• The npm commands used to run the UT / UAT steps are configurable but default to "test" and "test:uat" respectively.
• Making the assumption that the tests will be configured via environment variables. Key-value pairs will be passed to the stepimplementer and used to set env vars.
• The UAT step will require an endpoint to test against. A dedicated parameter will specify the name of an environment variable to set with the deployed application endpoint
• The test step will generate "xunit" formatted test results that can be parsed by this step implementer

Example Config:

unit-test:
- implementer: NpmXunitTest
  config:
    test-reports-dir: test_results

uat:
- implementer: NpmXunitIntegrationTest
  config:
    target-host-env-var-name: APP_ROUTE
    test-reports-dir: uat-reports
    npm-envs:
       WEB_DRIVER_URL: http://selenium-grid.devsecops:4444/wd/hub
       BROWSER: chrome
       USER1: test1
       USER2: test2

Breaking?

No

Integration Testing

Performed integration testing in a client's environment. Future: update ploigos npm reference app and implement a UAT step.

[codecov]

Codecov Report

Merging #227 (742c10e) into main (f192def) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              main      #227    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           87        91     +4     
  Lines         3559      3674   +115     
==========================================
+ Hits          3559      3674   +115     

Flag	Coverage Δ
pytests	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/ploigos_step_runner/__init__.py	100.00% <ø> (ø)
...er/step_implementers/uat/maven_integration_test.py	100.00% <ø> (ø)
...tep_runner/step_implementers/unit_test/tox_test.py	100.00% <ø> (ø)
...s_step_runner/step_implementers/shared/__init__.py	100.00% <100.00%> (ø)
...tep_runner/step_implementers/shared/npm_generic.py	100.00% <100.00%> (ø)
...nner/step_implementers/shared/npm_xunit_generic.py	100.00% <100.00%> (ø)
...step_implementers/static_code_analysis/__init__.py	100.00% <100.00%> (ø)
...step_implementers/static_code_analysis/tox_lint.py	100.00% <100.00%> (ø)
...igos_step_runner/step_implementers/uat/__init__.py	100.00% <100.00%> (ø)
...tep_implementers/uat/npm_xunit_integration_test.py	100.00% <100.00%> (ø)
... and 3 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 871b950...742c10e. Read the comment docs.

[itewk]

@kharyam can you squash your commits?

[itewk]

@kharyam can you confirm you have tested this in some integration type scenario?

[itewk]

@kharyam is this ready for review or should it be put in WIP status?

[kharyam]

@itewk This one is ready for review. It has been tested in a client's environment. I plan on updating the reference NPM app "at some point" to use this.

[itewk]

@kharyam can you rebase on main, i think you accidenlty squashed in some old changes or something from a previous version of main.

[kharyam]

@kharyam can you rebase on main, i think you accidenlty squashed in some old changes or something from a previous version of main.
@itewk oopsie - should be good now.

[itewk]

@kharyam thanks.