I am very new to this style of workflow, so please don't assume much in the answers.
I have started a new project using Vue CLI 3 creation tools, and including the Mocha-Chai tests. I can run the tests in Yarn (yarn run test:unit)
I would like to know:
How might I attach a debugger to the test run (I am using Visual Studio Code)?
How might I run the tests in a browser?
Related
is there a way to get some kind of Flutter Test Explorer into the IntelliJ IDE?
I am thinking of something like JUnit has in Visual Studio. Let's say that it should be something like this. My tests are stored in Feature Files.
If yes please send me a link to an addon or tool.
Thanks.
EDIT 1:
I am talking about the tool which "sees" all feature files and scenarios in it before the run. User than can select which scenario will be executed from the list of scenarios.
If you run tests in IntelliJ you should see something very similar to what you have screen shotted above for VS. You may find if you're using a build tool (Gradle/Maven) that running tests defaults to using the build tool to do so but you can switch this back to IntelliJ alone. What are you currently seeing/not seeing in IntelliJ?
See https://www.jetbrains.com/help/idea/performing-tests.html for more info + screen shot very similar to VS.
Need clarification- Can we build CI CD pipeline using Jenkins where my development code written is in C# and automation code is java eclipse
Requirement :
1. Whenever developer will commit the code then new Build should be generated
2. It should run unit test and smoke suite
3. Once Testing smoke suite passed it should show build passed else build should be failed
Can we achieve it using Jenkins. I have concerns like my development and automation code in two different language. In order to build pipeline do we need to have dev and test code in the same repository
Thanks in advance . Please suggests me
I am in exploration phase.
I need help in configuration. I don't think any code will require for this.
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]
I am using Nodeclipse to create a test automation framework using Protractor. However, I'm not able to debug (step through my code). I am however able to successfully do so using WebStorm. Its really very frustrating to debug tests using Protractor's browser.pause(); and browser.debugger(); statements.
Can anyone please help on this ? Is there any particular configuration which needs to be done on Nodeclipse just as we do on WebStorm as shown here: https://github.com/angular/protractor/blob/master/docs/debugging.md
I've just picked up CoffeeScript and I'm struggling to understand the deployment workflow. It seems you constantly have to compile the .coffee files before using them. (Yes, I'm aware that you can have it embedded in the browser, but that's not recommended for production applications).
Does one have to constantly (manually) compile the files before deploying? (For example, if using Eclipse, a simple Ctrl+S saves and deploys the .war/.ear on the local machine's server.) Do we have to change the build scripts (for a central, possible CI server) for deploying .coffee files? Is there anyway to have integrated compiling via the IDEs (Eclipse/Netbeans)
Any ideas/pointers/examples on this? How/what have you used in the past?
I call browserify in my Cakefile to pre-compile and package my CoffeeScript for the browser. For an example of how I call browserify as well as coffeedoc and coffeedoctest take a look at the Cakefile for my Lumenize project.
If you are using express or some other node based server, you can have your CoffeeScript compiled at request time, using tools like NibJS or as described in The Little Book on CoffeeScript (Applications chapter), you can use Stitch. BTW, I highly recommend, The Little Book. The "Compiling" chapter has information about Cake and compiling that might help you.
Yes, you should have a build script. Most CoffeeScript projects use a Cakefile for this; see, for example, 37signals' pow. With a Cakefile, you can just run
cake build
from the command line to run the build task in the Cakefile.
You can run the Cakefile on a CI server, assuming that you have Node and CoffeeScript installed on that server.
Don't deploy the coffee files, use something like "coffee -cwj" to constantly watch and compile the .coffee files into javascript (.js) files and deploy those.
The options are c=compile, w=watch and j=join the files.
See the coffee-script web site for details of the options you can pass in.