search

ansible-collections / ibm_zos_core

Red Hat Ansible Certified Content for IBM Z
77 stars 44 forks source link

[Enabler] Run all tests cases with the concurrent executor (CE). #1600

Open ddimatos opened 4 months ago

ddimatos commented 4 months ago

Is there an existing issue for this?

Enabler description

This is part of epic: [Epic][Enabler][CE] Concurrent Executor tasks enabling concurrency in the pipeline.

CE has only been tested with:

  1. The simple load balancer test suite consisting of 100 simple equality checks, this test suit runs fast in under 5 seconds and is primarily intended to expedite development and changes for CE.
  2. The zos_tso_command.py test suite
  3. The zos_operator.py test suite
  4. A couple of times, the zos_job_submit.py test suite

The reason limited testing was performed on CE was because there is pending work in epic [Epic][Portability] Ensure test suite execution portability & parallelism

This issue should test the full regression bucket for both functional and unit tests with the CE tool.

Currently the tool is not deployed to Jenkins nor a Linux VM and been run only locally. The goal would be to minimally have this deployed to Linux machine and run from there so its on the same subnet.

This relates to PR https://github.com/ansible-collections/ibm_zos_core/pull/828. Epic #1585 must complete before this can be started.

fernandofloresg commented 1 month ago

Comments from Demetri:

This might happen organically meaning I run it so I can debug anything in the tool sooner than later but not all the ECs are up yet 5 i mentioned today so that is my near term focus. Even if it does get done its still good to do.

I have a RHEL image with it installed, not sure if you would want to start fresh as a fresh install on RHEL, i did add some logic for different OSs during the venv -setup for packages needed if it were RHELL or Ubuntu.

Three is verbosity on the command line if set to true, its going to be way to much to read from a cli, the logs get written as HTML so you can use CLI browsers like Lynx to read it from shell or maybe I also write the logs in text and not just HTML (the library I have writes in HTML and can do text too) The HTML logs are nice as its an easy scroll

I would expect you are doing a bit more than just running, evaluating usability, eg, did I miss something , does it need more work to be everyones needs.