Skip to content
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

IntelliJ cannot run failed tests #8740

Closed
gthd opened this issue Mar 31, 2018 · 9 comments
Closed

IntelliJ cannot run failed tests #8740

gthd opened this issue Mar 31, 2018 · 9 comments
Labels
a-Build CI, task automation, build pipeline a-Testing Testing-related traits such as efficiency, robustness, coverage

Comments

@gthd
Copy link
Contributor

gthd commented Mar 31, 2018

When I try to run the failed tests in IntelliJ I get the following error:
issue_running_failed_tests

Has anyone encountered the same problem before and if yes how to solve it ?

@LuLechuan
Copy link
Contributor

@gthd Hi, just to make sure you have done the following:

  1. Go to test.property and specify the directory to your browser
  2. Run npm install in your terminal as there is a recent update on the dependencies, followed by npm run build
  3. Run the appengine.
    I have not encountered the same issue as you but just to check that the above are not the cause to the issue

@gthd
Copy link
Contributor Author

gthd commented Mar 31, 2018

Hi @LuLechuan I checked all three points but the problem still persists.

@bqnguyen94
Copy link
Contributor

Just curious, if you go the directory using system explorer do you see the file testng-failed.xml?

@whipermr5
Copy link
Member

That run config is only for rerunning failed tests that were originally launched from the command line, e.g. ./gradlew ciTests. IntelliJ already has a built-in function for rerunning failed tests that were launched from within the IDE.

@LiHaoTan
Copy link
Contributor

LiHaoTan commented Apr 1, 2018

I guess for consistency we might want to allow IntelliJ to generate testng-failed.xml as well.

@gthd if you want to do this you can go to the run configurations -> Listeners -> Use default reporters.

If anyone is interested in improving this, maybe can refer to 5e6fd5e

@gthd
Copy link
Contributor Author

gthd commented Apr 1, 2018

@bqnguyen94 There is no test-output folder for some reason
directory

@whipermr5 whipermr5 added a-Testing Testing-related traits such as efficiency, robustness, coverage a-Build CI, task automation, build pipeline labels Apr 1, 2018
@tshradheya
Copy link
Member

@LiHaoTan Why was the value of DEFAULT_REPORTERS changed to false after this commit 5e6fd5e ?

I am thinking of making it true so that it becomes stnadardized for IntelliJ

@LiHaoTan
Copy link
Contributor

@tshradheya actually that's because that commit wasn't merged to master (part of a dropped PR).

Do you want to also link the run config JDK to the project? That way we don't have to change the JDK version in the run config when we change versions.

@tshradheya
Copy link
Member

@LiHaoTan Okay. I have addressed the changes in #8845

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-Build CI, task automation, build pipeline a-Testing Testing-related traits such as efficiency, robustness, coverage
Projects
None yet
Development

No branches or pull requests

7 participants