Skip to content

Change Test expectation artifacts to include Tracking signatures info

Vishwa Bhat requested to merge vbhat161-enable-tracking-ff into main

What does this MR do?

Problem: The reference/expectation SAST artifacts in the analyzer repository(qa/expect) are generated with Tracking Calcular feature disabled by default. This was due to the decision to test the Tracking Calculator feature as an independent testcase instead of enabled-all-by-default in the integration-tests. However, the scheduled QA orchestrator runs against downstream projects with the Tracking Calculator Feature flag(vulnerability_finding_signatures) enabled by default, and the resultant SAST artifact is compared against the reference/expectation SAST artifact in the analyzer repository causing orchestrator jobs to fail.

Solution: As mentioned in the comment, this MR does the following:

  • regenerates reference/expectation SAST artifacts with Tracking Calculator Feature Flag enabled for c, java and python projects but not go since there was already a dedicated testcase for testing tracking-calculator case for the same project(go/default) whose expectation artifact can be used in the corresponding downstream project.
  • modify the spec file to support the behavior of running against Tracking Calculator Feature Flag enabled.

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

Edited by Lucas Charles

Merge request reports