KEDA scales down Selenium Chrome nodes only after all tests complete, not after individual tests

[rajeshl8]

Description

I am using KEDA to manage auto-scaling of Selenium Chrome nodes in a Kubernetes environment. However, I am facing an issue where all pods remain active during the execution of tests, and KEDA only scales them down after the entire test suite has completed. I expected KEDA to scale down individual nodes as soon as their respective tests are finished, but this is not happening.

Expected Behavior

Each Selenium Chrome node should be scaled down as soon as its associated test completes, rather than waiting for the entire test suite to finish.

Actual Behavior

KEDA scales down the nodes only after the last test has completed, causing all pods to remain active for the entire duration of the test suite.

KEDA Configuration

apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: selenium-chrome-scaledobject
  namespace: sel-grid-auto-scaler
spec:
  scaleTargetRef:
    name: selenium-chrome-node
  minReplicaCount: 3
  maxReplicaCount: 800
  cooldownPeriod: 30
  pollingInterval: 5
  triggers:
    - type: selenium-grid
      metadata:
        url: 'http://selenium-hub:4444/graphql'
        browserName: 'chrome'