Have you looked at [ScalaTest][1] ?

I&#39;ve not used it, but it comes from Bill Venners and co at Artima, and consequently I suspect it&#39;ll do the job. It doesn&#39;t appear to have IDE integration, however.

[This blog entry][2] is a little old, but suggests that TestNG is the best option for testing Scala. TestNG will certainly have IDE integrations.

EDIT: I&#39;ve just realised that I wrote this answer in 2009, and the world has moved on (!). I am currently using ScalaTest, the IDE integration works fine, and I can strongly recommend it. In particular the [matcher DSL][3] works very nicely


  [1]: http://www.artima.com/scalatest/
  [2]: http://www.theserverside.com/blogs/thread.tss?thread_id=48085
  [3]: http://www.scalatest.org/user_guide/using_matchers

I&#39;m the author of specs. If you&#39;re a Intellij user, I advise you to mix-in in the org.specs.runner.ScalaTest trait to your specification and run it as a ScalaTest suite.

If you have any issue with that, or anything else feel free to send a message to the [specs-users][1] mailing list.

  [1]: http://groups.google.com/group/specs-users

You could also check out [Specs][1] it&#39;s fairly complete and IIRC is heavily used as part of Lift.


  [1]: http://code.google.com/p/specs/ &quot;Specs&quot;

I would like to write a Ruby on Rails application that consumes a RESTful web service API performs some logic on the result and then displays that data on my view.  For example, let&#39;s say I wanted to write a program that did a search on search.twitter.com.  Using pure ruby I might create the following method:

    def run(search_term=&#39;&#39;, last_id=0)
      @results = []
      url = URI.parse(&quot;http://search.twitter.com&quot;)
      res = Net::HTTP.start(url.host, url.port) do |http|
        http.get(&quot;/search.json?q=#{search_term}&amp;since_id=#{last_id.to_s}&quot;)
      end
      @results = JSON.parse res.body
    end

I&#39;m tempted to just drop that method into my Rails controller as a private method, but part of me thinks that there is a better, more &quot;Rails&quot; way to do this.  Is there a best practice approach or is this really the best way?

What is the proper &quot;Rails Way&quot; to consume a RESTful web service on another domain?

How can I adjust the size of the window in XNA. 

Default it starts in a 800x600 resolution.

How do I set the window / screen size in xna?

I just recently started learning the Scala language and would like to do it in [TDD][1]-way. Could you share your experiences on the unit testing frameworks there are for Scala and the pros/cons of them.

I&#39;m using IntelliJ IDEA for Scala development, so it would be nice to be able to run the tests with IDE-support.


  [1]: http://en.wikipedia.org/wiki/Test-driven_development

Unit testing Scala

<p>I just recently started learning the Scala language and would like to do it in <a href="http://en.wikipedia.org/wiki/Test-driven_development" target="_blank" rel="noopener noreferrer">TDD</a>-way. Could you share your experiences on the unit testing frameworks there are for Scala and the pros/cons of them.</p>
<p>I'm using IntelliJ IDEA for Scala development, so it would be nice to be able to run the tests with IDE-support.</p>


We have a large, multi-platform application written in C. (with a small but growing amount of C++) It has evolved over the years with many features you would expect in a large C/C++ application:

* `#ifdef` hell
* Large files that make it hard to isolate testable code
* Functions that are too complex to be easily testable

Since this code is targeted for embedded devices, it&#39;s a lot of overhead to run it on the actual target. So we would like to do more of our development and testing in quick cycles, on a local system. But we would like to avoid the classic strategy of &quot;copy/paste into a .c file on your system, fix bugs, copy/paste back&quot;. If developers are going to to go the trouble to do that, we&#39;d like to be able to recreate the same tests later, and run in an automated fashion.

Here&#39;s our problem: in order to refactor the code to be more modular, we need it to be more testable. But in order to introduce automated unit tests, we need it to be more modular.

One problem is that since our files are so large, we might have a function inside a file that calls a function *in the same file* that we need to stub out to make a good unit test. It seems like this would be less of a problem as our code gets more modular, but that is a long way off.

One thing we thought about doing was tagging &quot;known to be testable&quot; source code with comments. Then we could write a script scan source files for testable code, compile it in a separate file, and link it with the unit tests. We could slowly introduce the unit tests as we fix defects and add more functionality.

However, there is concern that maintaining this scheme (along with all the required stub functions) will become too much of a hassle, and developers will stop maintaining the unit tests. So another approach is to use a tool that automatically generates stubs for all the code, and link the file with that. (the only tool we have found that will do this is an expensive commercial product) But this approach seems to *require* that all our code be more modular before we can even begin, since only the external calls can be stubbed out.

Personally, I would rather have developers think about their external dependencies and intelligently write their own stubs. But this could be overwhelming to stub out all the dependencies for a horribly overgrown, 10,000 line file. It might be difficult to convince developers that they need to maintain stubs for all their external dependencies, but is that the right way to do it? (One other argument I&#39;ve heard is that the maintainer of a subsystem should maintain the stubs for their subsystem. But I wonder if &quot;forcing&quot; developers to write their own stubs would lead to better unit testing?)

The `#ifdefs`, of course, add another whole dimension to the problem.

We have looked at several C/C++ based unit test frameworks, and there are a lot of options that look fine. But we have not found anything to ease the transition from &quot;hairball of code with no unit tests&quot; to &quot;unit-testable code&quot;.

So here are my questions to anyone else who has been through this:

* What is a good starting point? Are we going in the right direction, or are we missing something obvious?
* What tools might be useful to help with the transition? (preferably free/open source, since our budget right now is roughly &quot;zero&quot;)

Note, our build environment is Linux/UNIX based, so we can&#39;t use any Windows-only tools.

How do you introduce unit testing into a large, legacy (C/C++) codebase?

I have run into a problem wherein we keep having complex SQL queries go out with errors. Essentially this results in sending mail to the incorrect customers and other &#39;problems&#39; like that.

What is everyone&#39;s experience with creating SQL queries like that? We are creating new cohorts of data every other week.

So here are some of my thoughts and the limitations to them:

- **Creating test data** Whilst this would prove that we have all the correct data it does not enforce the exclusion of anomalies in production.  That is data that would be considered wrong today but may have been correct 10 years ago; it wasn&#39;t documented and therefore we only know about it after the data is extracted.

- **Create Venn diagrams and data maps** This seems to be a solid way to test the design of a query, however it doesn&#39;t guarantee that the implementation is correct.  It gets the developers planning ahead and thinking of what is happening as they write. 

Thanks for any input you can give to my problem.

Best way to test SQL queries

I have a couple of ActionMethods that queries the Controller.User for its role like this

    bool isAdmin = User.IsInRole(&quot;admin&quot;);

acting conveniently on that condition.

I&#39;m starting to make tests for these methods with code like this

    [TestMethod]
    public void HomeController_Index_Should_Return_Non_Null_ViewPage()
    {
        HomeController controller  = new HomePostController();
        ActionResult index = controller.Index();
    
        Assert.IsNotNull(index);
    }

and that Test Fails because Controller.User is not set.
Any idea?

How to mock Controller.User using moq

I&#39;ve recently been building a test framework for a bit of C# I&#39;ve been working on. I have NUnit set up and a new project within my workspace to test the component. All works well if I load up my unit tests from Nunit (v2.4), but I&#39;ve got to the point where it would be really useful to run in debug mode and set some break points.

I&#39;ve tried the suggestions from several guides which all suggest changing the &#39;Debug&#39; properties of the test project:

    Start external program: C:\Program Files\NUnit 2.4.8\bin\nunit-console.exe
    Command line arguments: /assembly: &lt;full-path-to-solution&gt;\TestDSP\bin\Debug\TestDSP.dll

I&#39;m using the console version there, but have tried the calling the GUI as well. Both give me the same error when I try and start debugging:

    Cannot start test project &#39;TestDSP&#39; because the project does not contain any tests.

Is this because I normally load &lt;full-path-to-solution&gt;\DSP.nunit into the Nunit GUI and that&#39;s where the tests are held?

I&#39;m beginning to think the problem may be that VS wants to run it&#39;s own test framework and that&#39;s why it&#39;s failing to find the NUnit tests?

**Edit**: To those asking about test fixtures, one of my .cs files in the TestDSP project looks roughly like this:

    namespace Some.TestNamespace
    {
        // Testing framework includes
        using NUnit.Framework;
        
        [TestFixture]
        public class FirFilterTest
        {
            [Test]
            public void Test01_ConstructorTest()
            {
                ...some tests...
            }
        }
    }

...I&#39;m pretty new to C# and the NUnit test framework so it&#39;s entirely possible I&#39;ve missed some crucial bit of information ;-)

**Final Solution**: The big problem was the project I&#39;d used. If you pick `Other Languages -&gt; Visual C# -&gt; Test -&gt; Test Project` ...when you&#39;re choosing the project type, Visual Studio will try and use it&#39;s own testing framework as far as I can tell. You should pick a **normal** C# class library project instead and then the instructions in my selected answer will work.

How do I run NUnit in debug mode from Visual Studio?

Is it bad practice to have more than one assertion in a unit test? Does it matter?

Is it bad practice to have more than one assertion in a unit test?

How is pattern matching in Scala implemented at the bytecode level?

Is it like a series of `if (x instanceof Foo)` constructs, or something else? What are its performance implications?

For example, given the following code (from [Scala By Example][1] pages 46-48), how would the equivalent Java code for the `eval` method look like?

    abstract class Expr
    case class Number(n: Int) extends Expr
    case class Sum(e1: Expr, e2: Expr) extends Expr

    def eval(e: Expr): Int = e match {
      case Number(x) =&gt; x
      case Sum(l, r) =&gt; eval(l) + eval(r)
    }

P.S. I can read Java bytecode, so a bytecode representation would be good enough for me, but probably it would be better for the other readers to know how it would look like as Java code.

P.P.S. Does the book [Programming in Scala][2] give an answer to this and similar questions about how Scala is implemented? I have ordered the book, but it has not yet arrived.

  [1]: http://www.scala-lang.org/docu/files/ScalaByExample.pdf
  [2]: http://www.amazon.com/Programming-Scala-Comprehensive-Step-step/dp/0981531601


How is pattern matching in Scala implemented at the bytecode level?

The use of symbol literals is not immediately clear from what I&#39;ve read up on Scala. Would anyone care to share some real world uses?  

Is there a particular Java idiom being covered by symbol literals?  What languages have similar constructs?  I&#39;m coming from a Python background and not sure there&#39;s anything analogous in that language.

What would motivate me to use &#39;HelloWorld vs &quot;HelloWorld&quot;?

Thanks

What are some example use cases for symbol literals in Scala?

I&#39;m new to Scala and don&#39;t know Java. I want to create a jar file out of a simple Scala file. So I have my HelloWorld.scala, generate a HelloWorld.jar. 

Manifest.mf:

    Main-Class: HelloWorld

In the console I run:

    fsc HelloWorld.scala
    jar -cvfm HelloWorld.jar Manifest.mf HelloWorld\$.class HelloWorld.class
    java -jar HelloWorld.jar 
      =&gt; &quot;Exception in thread &quot;main&quot; java.lang.NoClassDefFoundError: HelloWorld/jar&quot;

    java -cp HelloWorld.jar HelloWorld 
      =&gt; Exception in thread &quot;main&quot; java.lang.NoClassDefFoundError: scala/ScalaObject
	    at java.lang.ClassLoader.defineClass1(Native Method)
	    at java.lang.ClassLoader.defineClass(ClassLoader.java:675)
	    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
	    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
	    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
	    at java.security.AccessController.doPrivileged(Native Method)
	    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
	    at java.lang.ClassLoader.loadClass(ClassLoader.java:316)
	    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:280)
	    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)
	    at hoppity.main(HelloWorld.scala)


Creating a jar file from a Scala file

In this slide show on [ScalaActors.pdf][1] what does the single quote indicate when the message is sent to the pong actor? 

    class Ping(count: int, pong: Pong) extends Actor {
    def act() {
       pong ! &#39;Ping // what does the single quote indicate???
          receive {
             case &#39;Pong =&gt;
          }
       }
    }


  [1]: http://lamp.epfl.ch/~phaller/doc/ScalaActors.pdf

What does a single apostrophe mean in Scala?

I am attempting to use JSON to send data between the browser and my app.

I am attempting to use Lift 1.0 to create and parse JSON strings, but for some reason I am unable to parse the JSON I just constructed:

    scala&gt;import scala.util.parsing.json.JSON._
    import scala.util.parsing.json.JSON._
    
    scala&gt; import net.liftweb.http.js._
    import net.liftweb.http.js._
    
    scala&gt; import net.liftweb.http.js.JE._
    import net.liftweb.http.js.JE._
    
    scala&gt; val json = JsObj((&quot;foo&quot;, 4), (&quot;bar&quot;, &quot;baz&quot;)).toJsCmd
    json: String = {&#39;foo&#39;: 4, &#39;bar&#39;: &#39;baz&#39;}
    
    scala&gt;  parseFull(json)  
    res3: Option[Any] = None

How do I programmatically construct a valid JSON message in Scala/Lift that can also be parsed again?




How can I construct and parse a JSON string in Scala / Lift

What book would you recommend to learn test driven development? Preferrably language agnostic.

Test driven development book

We have tried to introduce unit testing to our current project but it doesn&#39;t seem to be working. The extra code seems to have become a maintenance headache as when our internal Framework changes we have to go around and fix any unit tests that hang off it.

We have an abstract base class for unit testing our controllers that acts as a template calling into the child classes&#39; abstract method implementations i.e. Framework calls Initialize so our controller classes all have their own Initialize method.

I used to be an advocate of unit testing but it doesn&#39;t seem to be working on our current project.

Can anyone help identify the problem and how we can make unit tests work for us rather than against us?

Unit test adoption

With MS ramming powershell into all new server products, I&#39;m starting to (reluctantly) think I need to take it seriously. Part of &quot;taking it seriously&quot; is TDD. Have you found good methods to unit test power shell scripts? 

I&#39;ve found samples of mocking from [Mr Geek Noise][1] - but I&#39;d really like something like [RhinoMocks][2]. [Brian Hartsock][3] has a sample of running tests on powershell strings from MS Test. A little hacky, but it seems to work. 

What I want is a Powershell TDD experience that is as clean as it is in &quot;real&quot; languages. 


----------

**Update to clarify:**
 
The first two answers attempt to steer me away from testing Powershell. The opinions are interesting. I don&#39;t want to know if it&#39;s a good idea to test in powershell. That&#39;s a subjective question that should be asked in a different forum. I want a solution to unit testing powershell. If you think it&#39;s a bad idea (it might be), treat it as a fun academic question.

 - Yes, scripting languages glue together disparate systems. However, as already pointed out, it&#39;s also easy to mock and break seams in a dynamic language. 
 - I&#39;m not asking about &quot;debugging&quot;. Debugging is an extremely useful topic. I&#39;ll let someone else ask it. 
 - Maybe PS scripts should be simple. The language supports modularity and it is inevitable that complex processes will be implemented in PS (even if a bad idea). 
 - The answer to this question is not &quot;You can&#39;t&quot;. I can see (from linked blogs - which are a little old) that some people have made headway on the problem.  

To re-state: **How do you implement an automated testing of Powershell logic in the style of xUnit?**  Integration tests are interesting, unit tests that break dependencies most interesting. 

  [1]: http://www.peterprovost.org/blog/post/TDD-with-PowerShell-Mocking-Things.aspx
  [2]: http://ayende.com/projects/rhino-mocks.aspx
  [3]: http://blog.brianhartsock.com/2009/03/27/tdd-with-powershell-from-the-client-perspective/

How to do TDD and unit testing in powershell?

I think back to Joel Spolsky&#39;s article about never rewriting code from scratch.  To sum up his argument:  The code doesn&#39;t get rusty, and while it may not look pretty after many maintenance releases, if it works, it works.  The end user doesn&#39;t care how pretty the code is.

You can read the article here: [Things You Should Never Do][1]

I&#39;ve recently taken over a project and after looking through their code, it&#39;s pretty awful.  I immediately thought of prototypes I had built before, and explicitly stated that it should not be used for any production environment.  But of course, people don&#39;t listen.

The code is built as a website, has no separation of concerns, no unit testing, and code duplication everywhere. No Data layer, no real business logic, unless you count a bunch of classes in App_Code.

I&#39;ve made the recommendation to the stake holders that, while we should keep the existing code, and do bug fix releases, and some minor feature releases, we should start rewriting it immediately with Test Driven Development in mind and with clear separation of concerns.  I&#39;m thinking of going the ASP.NET MVC route.

My only concern is of course, the length of time it might take to rewrite from scratch.  It&#39;s not entirely complicated, pretty run of the mill web application with membership, etc..

Have any of you come across a similar problem?  Any particular steps you took?

**UPDATE:**

So.. What did I end up deciding to do?  I took Matt&#39;s approach and decided to refactor many areas. 

 - Since App_Code was getting rather
   large and thus slowing down the build
   time, I removed many of the classes
   and converted them into a Class
   Library.
 - I created a very simple Data Access
   Layer, which contained all of the ADO
   calls, and created a SqlHelper object
   to execute these calls.
   
 - I implemented a cleaner logging   
   solution, which is much more concise.

While I no longer work on this project [funding, politics, blah blah], I think it gave me some enormous insight into how bad some projects can be written, and steps one developer can take to make things a lot cleaner, readable and just flat out better with small, incremental steps over time.


  [1]: http://www.joelonsoftware.com/articles/fog0000000069.html

When to rewrite a code base from scratch

By default nunit tests run alphabetically. Does anyone know of any way to set the execution order? Does an attribute exist for this?

Content Type	Original Author	Original Content on Stackoverflow
Question	Kaitsu	View Question on Stackoverflow
Solution 1 - Unit Testing	Brian Agnew	View Answer on Stackoverflow
Solution 2 - Unit Testing	Eric	View Answer on Stackoverflow
Solution 3 - Unit Testing	Saem	View Answer on Stackoverflow

Unit testing Scala

Unit Testing Problem Overview

Unit Testing Solutions

Solution 1 - Unit Testing

Solution 2 - Unit Testing

Solution 3 - Unit Testing

How do I set the window / screen size in xna?

What is the proper "Rails Way" to consume a RESTful web service on another domain?

Attributions