[MGNLTEST-55] Quarantined tests are executed on jenkins but not locally Created: 03/Jun/20 Updated: 07/Jul/20 Resolved: 07/Jul/20 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | QA&Testing, fwk-infra-structure | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Epic Link: | core-TF-features-bugs-improvements |
| Description |
NEW descriptionThe old description seems to be wrong. Jenkins does still what it should.
OLD descriptionMethods annotated with info.magnolia.integrationtests.rules.Quarantine should not be executed per default, according to javadoc of info.magnolia.integrationtests.rules.QuarantineRule. But atm "quarantined methods" are executed on Jenkins. (See slack discussion.) We figured this out in the context of
Acceptance criteriaStep 1
Step 2 Completely get rid of the Quarantine annotation. Step-2 could be part of a follow-up
|
| Comments |
| Comment by Christoph Meier [ 03/Jun/20 ] |
|
tbh, I dislike the Quarantine annotation, seems just like postponing a problem. |
| Comment by Christoph Meier [ 07/Jul/20 ] |
|
While on jenkins everything works as expected, locally the tests are not run. Note that we also are on the way phasing out the JUnit-4 based UI-tests, see I close this. No need to investigate here atm. |