Browse Source
Although it should not happen in theory, sometimes a test class is discovered more than once via the TestClassScanner in our integration tests. When it does happen in our tests, the two Class objects have the same fully-qualified class name but represent different classes which leads to failures due to incorrect associations between test class names and their MergedContextConfiguration. To address this, this commit modifies TestContextAotGenerator so that it skips duplicate test class names.pull/31445/head
Sam Brannen
1 year ago
1 changed files with 20 additions and 10 deletions
Loading…
Reference in new issue