New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Acceptance tests for Warnings Next Generation Plugin #479
Conversation
Add inputs for ReferenceFinder
Issue regex filter
…ce-test-harness into A-MSG-TestUIAggregation # Conflicts: # src/test/java/plugins/AnalysisPluginsTest.java
…ce-test-harness into A-MSG-TestUIAggregation # Conflicts: # src/test/java/plugins/AnalysisPluginsTest.java
# Conflicts: # src/test/java/plugins/AnalysisPluginsTest.java
# Conflicts: # src/test/java/plugins/AnalysisPluginsTest.java
…nce-test-harness into DarphBobo-hm-edu-testing # Conflicts: # src/main/java/org/jenkinsci/test/acceptance/plugins/warnings/IssuesRecorder.java
…nce-test-harness into DarphBobo-hm-edu-testing # Conflicts: # src/main/java/org/jenkinsci/test/acceptance/plugins/warnings/IssuesRecorder.java
@olivergondza I finally managed it to get all tests running 🥇 On the configuration page I needed to remove the div with our famous navigation bar. |
@olivergondza ping. Anything else I should do? |
@@ -0,0 +1,35 @@ | |||
<?xml version="1.0" encoding="UTF-8"?> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file appears unused
I am glad to hear that! @uhafner, what is your vision about assertj's usage in ATH? I am still a bit uneasy to use both hamcrest and assertj (putting aside plain old junit's |
Did you see https://github.com/jenkinsci/acceptance-test-harness/pull/479/files#r256992566? I don't want to force something new here. I think AssertJ style is better than the other styles but I don't think it is worth the effort to replace existing code. So if you feel uncomfortable with both styles then I can remove it. Since we anyway have the idea to move most of the tests to the plugin itself and just leave one or two inside the ATH I can remove it from the ATH sub set of tests and leave it in the warnings-ng part of the tests. Is this approach of moving tests to a plugin working already? You referenced a PR some time ago but I don't find it anymore... |
Acceptance tests for Warnings Next Generation Plugin
I played with the assertj a bit and it seems to deliver better coding assistance and readability without impacting defect localization when compared to the alternatives. Let's keep it as it is so we will learn how well it does in the long term. While at it, it found out the tests was failing for me locally because of The ATH extracting: I was able to achieve that but mind the TODO: https://github.com/jenkinsci/kerberos-sso-plugin/pull/14/files#diff-58231b16fdee45a03a4ee3cf94a9f2c3R14. The |
Has been merged already. |
Acceptance tests for Warnings Next Generation Plugin
Thanks @uhafner, merged! |
Acceptance tests for Warnings Next Generation Plugin
Provides several tests for the Warnings Next Generation Plugin.