Comments on: Running Jasmine in .NET http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/ Startups, open source, and coffee. Sat, 02 Feb 2013 20:13:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: AdenaHewitt http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/#comment-160 AdenaHewitt Tue, 06 Nov 2012 08:32:00 +0000 http://lostechies.com/josharnold/?p=159#comment-160 I am happy to find so many useful information here in the post, we need develop more strategies in this regard, thanks for sharing. I am happy to find so many useful information here in the post, we need develop more strategies in this regard, thanks for sharing.

]]> By: Abraão Alves http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/#comment-128 Abraão Alves Tue, 10 Apr 2012 17:17:00 +0000 http://lostechies.com/josharnold/?p=159#comment-128 Jasmine testrunner in VisualStudio, console, browser, teamcity with one plugin package chutzpah.codeplex.com Jasmine testrunner in VisualStudio, console, browser, teamcity with one plugin package chutzpah.codeplex.com

]]> By: Anonymous http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/#comment-122 Anonymous Mon, 05 Mar 2012 22:08:00 +0000 http://lostechies.com/josharnold/?p=159#comment-122 @google-da8c79ac665d8e1a91d56ccde84c7ef3:disqus I think that I didn't properly communicate the origins of this tooling. It was born out of FubuMVC work and thus does not follow the standard that you may be used to. By "All .NET web templates", I think that you're referring to "All ASP.NET MVC web templates". We use a top-level content folder that is used as the primary directory for all assets (scripts, styles, images). This then feeds into our asset pipeline giving you a lot of power and control over each file. @google-da8c79ac665d8e1a91d56ccde84c7ef3:disqus I think that I didn’t properly communicate the origins of this tooling. It was born out of FubuMVC work and thus does not follow the standard that you may be used to.

By “All .NET web templates”, I think that you’re referring to “All ASP.NET MVC web templates”. We use a top-level content folder that is used as the primary directory for all assets (scripts, styles, images). This then feeds into our asset pipeline giving you a lot of power and control over each file.

]]> By: Tom McKearney http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/#comment-121 Tom McKearney Mon, 05 Mar 2012 21:05:00 +0000 http://lostechies.com/josharnold/?p=159#comment-121 Seems a little odd to buy into the standard delivery mechanism of the code via NuGet, yet require non-standard (for ASP.NET) location of the "Scripts" folder.  All .NET web templates have "Scripts" as a root-level folder. Seems a little odd to buy into the standard delivery mechanism of the code via NuGet, yet require non-standard (for ASP.NET) location of the “Scripts” folder.  All .NET web templates have “Scripts” as a root-level folder.

]]> By: Derick Bailey http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/#comment-119 Derick Bailey Tue, 28 Feb 2012 16:40:00 +0000 http://lostechies.com/josharnold/?p=159#comment-119 +1 to the annoyance! it gets messy and painful, fast. +1 to the annoyance! it gets messy and painful, fast.

]]> By: Anonymous http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/#comment-118 Anonymous Tue, 28 Feb 2012 16:36:00 +0000 http://lostechies.com/josharnold/?p=159#comment-118 RE: The standalone runner, you are right and I'll make an update to the post for that. I was attempting to refer to the pain involved with maintaining either individual runners or one big one. This is only annoying when you get into script dependencies. RE: The standalone runner, you are right and I’ll make an update to the post for that. I was attempting to refer to the pain involved with maintaining either individual runners or one big one. This is only annoying when you get into script dependencies.

]]> By: Derick Bailey http://lostechies.com/josharnold/2012/02/25/running-jasmine-specs-in-dotnet-with-serenity/#comment-117 Derick Bailey Tue, 28 Feb 2012 15:42:00 +0000 http://lostechies.com/josharnold/?p=159#comment-117 This couldn't have been better timed! I was just looking for some tips from the .NET world on using Jasmine with ASP.NET MVC. :) I'm definitely going to be trying Serenity ... maybe even later today as I was hoping someone would create a Jasmine runner for .NET. :) FWIW: I think the statement "For each spec file that you want to test, you need an equivalent test runner html file" is a bit off. When I use the standalone runner (as I'm doing now) I put all my specs in the one runner. This really isn't any different than using an automated runner, where all of the specs are run. The big difference is that you have to manually maintain the spec runner html file, and it's difficult to integrate in to a build process, as you pointed out. This couldn’t have been better timed! I was just looking for some tips from the .NET world on using Jasmine with ASP.NET MVC. :)

I’m definitely going to be trying Serenity … maybe even later today as I was hoping someone would create a Jasmine runner for .NET. :)

FWIW: I think the statement “For each spec file that you want to test, you need an equivalent test runner html file” is a bit off. When I use the standalone runner (as I’m doing now) I put all my specs in the one runner. This really isn’t any different than using an automated runner, where all of the specs are run. The big difference is that you have to manually maintain the spec runner html file, and it’s difficult to integrate in to a build process, as you pointed out.

]]>