Somehow the list of tests on the left pane of the test runner in RubyMine went away. Any ideas how to re-activate it?
Thanks
J. Pablo,
Please check that Test::Unit test framework reporter is enabled in your rake task run configuration settings (RubyMine | Run | Edit Configurations | Rake | your_rake_task).
Try the 'Layout'->'Restore Layout' action on the test-runner toolbar. This should help.
Related
On a new VS solution, I've started using NUnit 3.2. Older versions (2.6) had a external NUnit GUI, that made it possible to watch assemblies and automatically run tests on modifications. But I cannot find anything similar to this for 3.2 - neither in the docs nor through Google.
I've installed NUnit.3.2.0.msi, I've also installed the NUnit3 Test Adapter in VS + NUnit3.2 nuget package for my project.
I can easily run all my tests through VS' Test Explorer. But I miss some way to run them automatically. Anyone know how?
In older versions of Visual Studio, there used to be an option to run tests after every build, but it was removed. It was always buggy and tended to lock files and prevent you from rebuilding.
You could set a post build command on your test project to automatically run NUnit console whenever your test project recompiles. You have NUnit console installed, so you could point to that, or use the NUnit.Runners package to install it into the packages folder of your solution.
Open your test project settings and go to the Build Events tab. Click on Edit Post-Build. Enter the following;
"C:\Program Files (x86)\NUnit.org\nunit-console\nunit3-console.exe" "$(TargetPath)"
Now, whenever you build, your tests will be run and the results will appear in the output window.
Maybe not ideal if there is a lot of build output after your tests but it works.
FYI, the colour in the build output is a side-effect of the VSColorOutput Visual Studio extension, it is not from NUnit.
Visual Studio captures STDOUT, so I haven't been able to get it to open a CMD window and run the tests. If anyone knows how to do that, add a comment and I will update.
There is a GUI for NUnit 3 under developement on GitHub - but it's not advised for production use yet.
We set our tests up using the NUnitLite runner. This allows you to turn your test assembly into an executable - and on run, will launch the console and run all tests. [Documentation]
Resharper 9.0 says 'No tests found in selected solution items.' Yet there are over 100 tests.
I right click my solution in Visual Studio 2013 and click the "Run Unit Tests" option near the bottom of the context menu. I get the error message: "No tests found in selected solution items.".
Every once in a while, they do show up and run, but most of the time, they don't show up and I get the error message.
I have NCover installed and it has a 'Bolt Tests' tab from which I can run all the tests. However, I would prefer to run the tests from the main menu using Resharper.
Does anybody know why these tests aren't showing up and how to get them to consistently be discovered?
Thanks,
Curtis
Looks like the latest update of 9.1 solved the problem. Thanks everybody.
I want to run a grunt.js file inside a folder that is inside a netbeans project.
Test 1:
when I check if grunt is working correct in c:\Users\someuser: grunt -v
it gets me the grunt version info.
Test 2:
when Im inside the project folder with grunt inside
c:\wamp\www\project\grunt\ (with grunt.js inside)
I run grunt or grunt -v (just for testing and I get this)
The launcher has determined that the parent process has a console and will reuse
it for its own console output.
Closing the console will result in termination of the running program.
Use '--console suppress' to suppress console output.
Use '--console new' to create a separate console window.**
What can I do to fix this?
Thank you
fixed. My mistake. Mi grunt file was Grunt.js not Gruntfile.js
When I run dbm-generate-changelog exception is thrown. I would like to debug this script but I can't figure how to do it. I tried to put breakpoint to the script file _DatabaseMigrationCommon.groovy and then in eclipse created new "debug configuraion" command. When I run this none of breakpoints suspend the execution. I also tried with --debug argument.
setup:
Grails: 2.3.3
GGTS: 3.4
Eclipse: 4.3
Do the following:
launch grails with the -debug option
grails -debug run-app
create Remote Java Application debug configuration in Eclipse and set port to 5005
enjoy breakpoints and step-by-step debugging
Try to use dbm-generate-changelog -verbose -stacktrace, it could help you to find cause of fault.
I'm using GGTS tool. Open it.
Go to "Debug As" (bug icon).
Select "grails" in the list and select "new configuration" (blank paper icon).
In the next window, select your grail project in the "project field".
Write "run-app" in the grails commmand field.
click "Apply" and click "Debug".
That is.
In Grails 4, you have to use the debug-jvm argument, i.e. grails run-app -debug-jvm
Source: https://docs.grails.org/4.0.10/ref/Command%20Line/run-app.html
This doesn't answer your question as to "how to debug it", but the dbmInit target had a bug in it.
The dbmInit target depends on bootsrap and loadApp, then manually calls configureApp. This bootstraps the system twice, and some beans (quartz scheduler and grails_cache) get mad if they get recreated with the same name.
changing the top few lines to
target(dbmInit: 'General initialization, also creates a Liquibase instance') {
// depends(classpath, checkVersion, configureProxy, enableExpandoMetaClass, compile, bootstrap, loadApp)
depends(classpath, checkVersion, configureProxy, enableExpandoMetaClass, compile, bootstrapOnce)
// configureApp()
try {....
basically replacing bootstrap, ladApp, and configureApp() with a call to bootstrapOnce might clean (well, 9 years ago, so have cleaned) things up for you.
We're using 'grails war' to build a war on hudson then another job to deploy to our test environment.
The problem is that when the 'grails war' encounters a plugin upgrade, it will continuously ask the user to upgrade certain plugins.
Is there a way to respond 'y' on all user input?
I tried --non-interactive but that seems to do nothing.
You may need to put quotes around the run target in the Targets text field:
"war --non-interactive"
yes | grails war
assuming your on OSX/unix/Linux/cygwin. That answers yes for all questions that the program you pipe it to asks.
if you only want to say yes once, you can use
echo y | grails war