You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Acceptance tests may comprise of hundred test cases and it therefore is more convenient to run them as one Jenkins job. This can be achieved by adding "all" to the test list, i.e.:
I'm not clear about your benefits here. By calling with "all", xtesting basically schedules all the tests one by one sequentially. If you list them all in the yaml files, Jenkins or GitLab CI/CD is rather in charge of the schedulling which allows you more flexibility especially to run them in parallel.
If I understand correctly, your request would be not to create 1 job per testcase but a single 'all' job ; the test case publications (DB and S3) would remain unchanged. That would result in a bit of extra logic in jenkins job template.
I must also check if it would work with a mutiple container use.
@collivier
thank you for your comments.
I believe the issue is using the same URL http://10.0.3.15:8181/RTE2QIGHRW2J/hello_world-127_0_0_1-hello-world-tests-latest-all-3/xtesting.log
across the individual tests. This probably creates a race condition resulting in the truncated log file.
I further assume this root cause is found in the xtesting Python library rather than in the CI framework.
Acceptance tests may comprise of hundred test cases and it therefore is more convenient to run them as one Jenkins job. This can be achieved by adding "all" to the test list, i.e.:
The console output in Jenkins is showing the following expected result:
The JSON files accessible via
show test individual information (which is ok), example for Test2:
{"project_name": "hello_world", "scenario": "os-nosdn-nofeature-noha", "stop_date": "2024-08-09 17:46:58", "case_name": "Test2", "build_tag": "RTE2QIGHRW2J", "version": "unknown", "pod_name": "hello_world", "criteria": "PASS", "installer": "unknown", "_id": "66b65612f58ff39d3d7ddb7b", "start_date": "2024-08-09 17:46:58", "details": {"links": ["http://10.0.3.15:8181/RTE2QIGHRW2J/hello_world-127_0_0_1-hello-world-tests-latest-all-3/xtesting.log"]}}
But the published log file accessible via
that is the same for both tests involved is truncated as follows:
The expectation is that when running all tests at once, the log file should be generated and published once, after all tests have been executed.
The text was updated successfully, but these errors were encountered: