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.
I had to add the following to the extension.vsixmanifest in Chutzpah.VS2012.vsix, to get it to install in VS Express: <InstallationTarget Version="[11.0,12.0)" Id="Microsoft.VisualStudio.VWDExpress" />