tdd

do you know about some interesting Eclipse plugins that supports Test driven development? Infinitest and JUnitMax do "Continuos Testing". All your tests are run in the background and testing errors appear as error annotations as if they are compiler errors. Interesting indeed ;). http://infinitest.github.com/ http://www.threeriversinstitute.org/junitmax/ Pulse is a visually nice plugin that lets you track your TDD flow. http://www.happyprog.com/pulse/ 来源： https://stackoverflow.com/questions/5936945/eclipse-plugins-that-supports-tdd

How can I test that a certain JQuery selector has been executed with Jasmine? I'm trying to do the following: spyOn($.fn, 'init').andCallThrough(); // my code expect($.init).toHaveBeenCalled(); But after this call, $('div') returns Object { selector="div", context=document, NaN=div.spec, more...} , though it has to return (and $.fn.init('div') does return it): [div.jasmine_reporter, div.banner, div.logo, 4 more...] . This stuff naturally breaks the code since the JQuery object is no longer usable. Example: Say I want to test that a JQuery selector has been called, I write: it('tests', function

I get a cast exception System.InvalidCastException : Unable to cast object of type 'System.Object[]' to type 'System.Object[,]'. at Castle.Proxies.ITestProxy.Get2DArray() at Scratch.TestFixture.Get2DArray() in TestTest.cs: line 17 from from the below: [TestFixture] public class TestFixture { [Test] public void Get2DArray() { Substitute.For<ITest>().Get2DArray().Returns(new object[1,1]); } } public interface ITest { object[,] Get2DArray(); } can anyone throw any light on this? I'm thinking it's a NSubstitute bug? NSubstitute depends on Castle, which depends on Reflection.Emit, so they blame

I am coming from a TDD mindset into BDD. I understand that using BDD is to focus on ensuring the behaviours and business goals of software are being met. What confuses me is that if I start using BDD in place of TDD, it seems I'm not able to test at such a low-level. For example, when writing a test with a TDD mindset, I might test that properties have been attached to the scope: it('should attach properties to scope', function () { expect(MainCtrl.items.length).toEqual(1); }); In doing this, another developer knows the assignment to scope was expected and required for future use, saving them

Closed . This question is opinion-based . It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . Closed 5 years ago . I'm wondering why unittest systems like PHPUnit include what seems to be repetitive operators that just add overhead to the unit tests. I can understand a couple of those methods, but most seem like a total waste of time. public function testPop(array stack) { this->assertEquals('foo', array_pop(stack)); this->assertEmpty(stack); } vs raw code (which is shorter and faster)

I found Open source projects with good quality tests but I wanted to ask something a bit different. I'm having a hard time visualizing how to build production code using TDD practices, particularly for networked database-driven applications where big chunks of functionality are dependent on one or more external systems. The two main strategies I've seen discussed for accomplishing that are decoupling code from the systems in question and using mocks. However, my intuition is that doing either one properly would also be complex and error-prone. I'd like to take a look at some real-life code