test(chart): Parallel tests execution against autoscaling in Kubernetes

[VietND96]

Thanks for contributing to the Docker-Selenium project!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines, applied for this repository.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

test(chart): Parallel tests execution against autoscaling in Kubernetes

Motivation and Context

Reuse existing sanity tests within the implementation of the concurrent executor to test the feature Selenium Grid Autoscaling on Kubernetes using KEDA.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[diemol]

My concern is... what do we do when it fails? How do we know what needs to be done if it fails?

[VietND96]

You mean how do we know what needs to be done for the test failed or the fix needed for grid or chart?

[diemol]

You mean how do we know what needs to be done for the test failed or the fix needed for grid or chart?

Exactly. Since this is testing an external dependency (keda).

[VietND96]

Yes, when I was adding this, I thought to guarantee regression issue only. For example use cases

• Someone raises PR to bump the default KEDA version used in chart.
• Someone raises PR to improve the chart template related to feat autoscaling

If this test failed...the author should rework it.

[diemol]

Let's add it then. If it gets unstable we need to analyze how much time we are investing in it.

Thanks, @VietND96!

[VietND96]

Thank you! I will merge this.