Can somebody tell how to setup NCrunch so that it does not build or run unit tests while editing javascript (.js), .html or .cshtml files?
If you use the "Run Impacted tests automatically, others manually" engine mode you can get close to what you are looking to do.
I posted this question on the NCrunch forum. As of the date of this post, NCrunch does not support ignoring certain files types, but performs a build as soon as any change is made to a file that is part of the solution.
NCrunch Forum Post
Related
I am looking into organizing HTML reports into directories other than the default target/surefire-reports.
I have read in the docs that there is an existing reportDir() method for Runner. Can I utilize this method for JUnit 5 tests? If not, are there any other ways?
I came across a similar post but I am not using executable jar version so the accepted answer would not be applicable.
Any help would be appreciated.
Please start trying the 1.0 RC version: https://github.com/intuit/karate/wiki/1.0-upgrade-guide - there are changes to the Runner API and how you can control the report output dir.
And there is no reason to make this customizable for JUnit based tests, that option is only for developer convenience: https://stackoverflow.com/a/65578167/143475
Also note that in the 1.0 version, if the reports dir already exists, it will be renamed - and maybe that behavior is sufficient.
Any other change may require you to contribute code.
Also see: https://stackoverflow.com/a/69490494/143475
I am looking into organizing HTML reports into directories other than the default target/surefire-reports.
I have read in the docs that there is an existing reportDir() method for Runner. Can I utilize this method for JUnit 5 tests? If not, are there any other ways?
I came across a similar post but I am not using executable jar version so the accepted answer would not be applicable.
Any help would be appreciated.
Please start trying the 1.0 RC version: https://github.com/intuit/karate/wiki/1.0-upgrade-guide - there are changes to the Runner API and how you can control the report output dir.
And there is no reason to make this customizable for JUnit based tests, that option is only for developer convenience: https://stackoverflow.com/a/65578167/143475
Also note that in the 1.0 version, if the reports dir already exists, it will be renamed - and maybe that behavior is sufficient.
Any other change may require you to contribute code.
Also see: https://stackoverflow.com/a/69490494/143475
I have upgraded my Community version of PyCharm to 2016.3.2, and I'm not positive it was this exact version, but when I went to run files that had unittests in them, only some of them are recognized as UnitTests that I can right click and run.
I have looked to make sure that my classes implement unittest.TestCase
class clWorkflowWebClientTest(unittest.TestCase):
all of my tests begin with test_blahblah()
If I go into Edit Configurations and add one manually, I can right click and run it from the project tree, and it runs as a UnitTest. But I don't get the "Run UnitTests in Blah' dialog when I right click the file.
This turned out to be an issue I caused myself. we had added a folder called 'UnitTest' and introducing this to the path caused issues with PyCharm knowing what was a true UnitTest file.
I still don't know exactly what caused some files to work, but there appears to be one method in those files that did work that was probably being imported from another file that had the proper pathing.
This question already has answers here:
Closed 13 years ago.
Possible Duplicate:
using frameworks in a command line tool
Hey,
I've written a command line 'foundation tool' that uses the RegexKit.framework extensively. Everything works when run in Xcode but if I compile the release build and try to run it in Terminal I get the following error:
dyld: Library not loaded: #executable_path/../Frameworks/RegexKit.framework/Versions/A/RegexKit
Closer inspection reveals that the RegexKit.framework bundle is sat in the same directory as my executable file... I've done some research and I'm thinking that as command line tools don't use application bundles there's no where for Xcode to copy the framework to. So I'm guessing that I need to compile the framework as a static library and include it in my code... am I right? If so, how do I go about doing this? Is there anything I can do in Terminal to point to the framework externally?
Any help would be very greatly received, I've been banging my head against this for a few days now!
Thanks in advance,
Tom
So... What I did in the end was to recompile the framework with a different Installation Directory (in the Deployment section, under the Build tab in the Target's Info) - I set it to just #executable_path.
I then compiled the framework and replaced the one in my Utilitie's project, I also changed the Copy Files build phase to copy the framework to "Executables" rather than Frameworks.
The good news is that this fixes my original problem - but obviously the framework has to be in the same directory as the executable.
So this got me unstuck but I'd still love to know how to compile RegexKit.framework statically!
You shouldn't be installing the framework in the Executable folder of your bundle. It should be in the Frameworks folder. You need a Copy Files phase in your project that copies the framework and you need to set the Destination to "Frameworks". "Copy only when installing" should be unchecked.
When testing this, you should make sure you perform a clean build. I typically delete the build folder rather than using Xcode's Clean menu option since it's quicker and more comprehensive.
Also: you cannot statically link to a framework. If you want to statically link to something, it needs to be a static library so in this case, you'd need to hack about with RegexKit. Bear in mind that static libraries cannot contain resources, whereas Frameworks, being bundles, can.
I'm in a bit of a pickle. I'm trying to run some environmental scripts before I run the build in a m2 project, but it seems no matter how hard I try - the 'pre' build script are never run early enough.
Before the 'pre-build' scripts are run, the project checks to see if the correct files are in the workspace - files that won't be there until the scripts I've written are executed.
To make them 'pre-build', I'm using the M2 Extra Steps plugin - but's it's not 'pre' enough.
Has anyone got any suggestions as to how I can carry out what I want to do?
Cheers.
Have you considered breaking it up into two projects, and setting the pre-build project to be upstream of the build project?
e.g.,
Foo Pre-build
Foo Build
After Foo Pre-build runs, cause "Foo Build" to run.
I have used this, admittedly in different scenarios than yours, quite successfully. This has the added benefit (if you need it) of allowing you to manually run a build without going through the pre-build steps, if you know they aren't necessary.
You should use the free form project type and not the maven project type.
If this is a problem (ie, there are projects that are expecting to be triggered by or triggering from), consider using a custom workspace location and having a free form project execute in this workspace before the maven project runs. The free form project can be used as the trigger for the maven project.
Does adding another build step as a shell script work?
My problem stemmed from the fact I wanted to set-up my workspace before I ran anything due to an issue with Dynamic Views (ClearCase) not being accessible from the workspace - I wanted to add a symlink to fix this.
However, Andrew Bayer has made a change to the plugin that I'm currently testing that should fix this...so the question is probably invalid in it's current form.
Will edit it once we come to a conclusion.