Skip to content

Change test run ordering#171

Merged
VitjanZ merged 9 commits into
mainfrom
feat/test_run_ordering
May 12, 2026
Merged

Change test run ordering#171
VitjanZ merged 9 commits into
mainfrom
feat/test_run_ordering

Conversation

@VitjanZ

@VitjanZ VitjanZ commented May 5, 2026

Copy link
Copy Markdown
Collaborator

When implementing/fixing conformance tests the current testing schedule if the implementation code changes is as such:

  1. Unit tests
  2. Previous conformance tests
  3. New conformance test

This PR changes the ordering to:

  1. Unit tests
  2. New conformance tests.
  3. Previous conformance tests.

This first makes sure the new conformance tests passes and then makes sure that the new code and tests did not cause any regressions.

@VitjanZ VitjanZ requested a review from pedjaradenkovic May 5, 2026 08:33
@dusano

dusano commented May 5, 2026

Copy link
Copy Markdown
Contributor

That's a very smart change!

@VitjanZ VitjanZ self-assigned this May 6, 2026
@VitjanZ VitjanZ force-pushed the feat/test_run_ordering branch from d336218 to 84129f4 Compare May 7, 2026 14:18
@VitjanZ VitjanZ requested a review from zanjonke May 8, 2026 08:50
@VitjanZ VitjanZ force-pushed the feat/test_run_ordering branch from 0979039 to 575e45e Compare May 11, 2026 14:12

@zanjonke zanjonke left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Left one small comment. I'll test it out locally just to make sure.

Comment thread render_machine/render_context.py Outdated
Comment on lines +533 to +537
ctx = self.conformance_tests_running_context

# Get next test to run
self.conformance_tests_running_context = self._get_next_test_to_run()

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would flip these 2 lines. At the moment ctx point points to the same object and there is no problem, but in the future if _get_next_test_to_run would create a new object, would be a bug.

@VitjanZ VitjanZ merged commit 1dfa799 into main May 12, 2026
10 checks passed
@VitjanZ VitjanZ deleted the feat/test_run_ordering branch May 12, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants