Nice tool. Minor quibble - it'd have been nice to be able to disable TeamCity integration instead of having it always on by default in that context. Whilst I'm sure it's useful for some, in my particular implementation my Chutzpah/Qunit tests are just one step in a longer NAnt script. The automatic TeamCity integration makes Chutzpah behave differently on a developer machine compared to how it does on the TeamCity server. Specifically, it changes the top line output message from "Success" to "Tests Passed: 1". When in reality there's a lot more going on in the wider script than just that one output from the Chutzpah runner.
Work-arounds I've used have included listing Chutzpah as a completely separate build step (not my preferred option - I like everything to be in NAnt, and besides there are some build steps Chutzpah depends upon and I don't want to have two NAnt scripts for before and after Chutzpah). Or, wrapping chutzpah.console.exe in a Console App to fool it into thinking it's not running in TeamCity at all, thereby getting it to stop changing the top line output and just give me the same output as on a developer PC.
Nice Tool, also with the extension of the context menu, but I recieve an error wenn I want to look at the settings of Unit Test Explorer, I cannot open the unit test explorer and I keep getting an System.Runtime.InteropServices.COMException (0x8971001E) when I try to run JS Tests in debugger.
UPDTAE: I reinstalled evrything and the COM Exception is gone, but I still cannot "use Chutzpah with debugger", it gives me this exception Error: System.Runtime.InteropServices.COMException (0x8971001E): Ausnahme von HRESULT: 0x8971001E bei EnvDTE80.Process2.Attach2(Object Engines) bei Chutzpah.VS.Common.DteHelpers.DebugAttachToProcess(Int32 subjectProcessId, String debugEngine) bei Chutzpah.VS.Common.VsDebuggerTestLauncher.LaunchTest(TestContext testContext) bei Chutzpah.TestRunner.<>c__DisplayClassc.<ExecuteTestContexts>b__b(TestContext testContext)
and in the Unit Test Explorer the Jscript tets are always listed as not executed.
This extension is fantastic and powerful. Very configurable. Incredibly versatile. Documentation is very detailed and helpful. The developer is very responsive and does a great job helping users with issues. Highly recommend it.
I am trying to integrate this tool with tfs build. it is working as expected.but resultant trx file is directly publishing to build URI, Is there any possible way to locate the trx in local folder(build controller location) and Can you please let me know how to generate the code coverage and publish the same to build uri. Even i tried with enable code coverage option but no luck. your help is much appreciated. Thanks.
A great Visual Studio (VS) extension; it enables Jasmine JS Specs to be run directly in IDE and the results displayed within VS's Test Explorer window. The only real short fall I've found is that you cannot load Jasmine Fixtures within Chutzpah Test Adapter. This is a real shame as we have to resort to using a Spec Runner page/view within a browser and it limits what we can test during the IC process. If anyone has a solution, please let me know what it is?
This is a bug in the version of QUnit chutzpah uses. I just commited a change to rev to the next version (https://chutzpah.codeplex.com/SourceControl/changeset/360a23f199f2ba8c08167986d20a54344ee13a1d).
I like the plugin on my local development environment. But it has been a huge problem on setting up TFS with chutzpah in typescript. I have not able to fix an issue in the issue tracker almost a month: http://chutzpah.codeplex.com/workitem/98
I also not sure whether it is the only problem I faced unless I can solve it and move forward. Also the blog for setting up TFS with chutzpah is outdated. The dll files are not matched. So I am also wonder whether I am doing a right by following the blog. Thanks.
Sorry that you are running into issues. I responded a few days ago on your StackOverflow post asking if you could file a bug on chutzpah.codeplex.com and attach a zip file which contains a repro. That would help me track and diagnose your issue.