dear friend I am new to this group ....Pl. enrol me as a member of this group....I am MCA 2002 passout with around one year work exp ......... Pl. mail me as...
I'm just getting started and hoping someone can point me in a good direction. For reference, our team will be using .NET (C#) for the development platform. ...
... Ideally, you want the code that actually works with the database to be kept separate from the rest of your code. Then you can test it against a test...
Setting up a test database on the fly can get a bit unwieldly and slow. I have found that a stored procedure to remove the dynamic data (i.e. orders) whilst...
Hi David, Ultimately you are going to have to test the database if it is part of your environment, but it is important to keep the business object tests and db...
... Writing tests is a pain. The only thing worse than writing tests is *not* writing tests. Teams that convert to TDD must continually check their ...
... Check out FitNesse (http://fitnesse.org). This is a wiki/acceptance-test engine written in Java. It uses tables to run acceptance tests. The tests are...
... FitNesse invokes FIT by using System.execute to fire off a new process. The FIT process that is invoked can be in any language. Thus, FitNesse can invoke...
I like Bill Wake's 3 A's "arrange, act, assert" to describe the structure of a test: * Create some objects and set them up * Invoke some methods * Check the...
... Ones they've used before? New ones? I'm going with AAA. None of the As stretch far at all. And I think a good style guide might be to divide each test case...
Here's a problem that has been bugging me a bit due to the duplication (and bloat) of code that has been causing in my tests, and I'd like to know how other...
... You have picked up the meme "faults are syntax errors". Ideally, at failure time, you hit <F4>, and the editor puts the cursor on the failing line. See...
... I have also struggled with this. I deal with it in two ways: I am not nearly as ruthless about removing duplication in my test code as I am in my...
Tony Milici
milici@...
Aug 5, 2003 12:21 am
4585
... I forgot one theme in my post: I put asserts in both the extracted method, and around the call to that method. This lets me tap <F4> to see each inner...
I'm not sure I understand the problem. When one of my tests fails, the framework gives me the test function name and a traceback. This is in Python, and I...
... Do the exact opposite of what you tried. Pull all the test code up into a base class and use the TemplateMethod pattern. Each derivative will implement...
... I think the OP's test cases are already as far as this pattern: Any of the various macros called "assert" contains an __asm int 3;. That hard-codes a...
... a ... of ... name. ... However, at failure time, the OP wants the information "I failed on this line, and we just opened >that< file". So either we put too...
** Reply to message from "David Bosley" <D_BOSLEY@...> on Mon, 04 Aug 2003 01:19:54 -0000 ... I use both. I've gotten a lot of milage out of mocks for...
EXCITING CAREER!!! GOLDEN CHANCE WORK FROM HOME JOBS We Are An Excellent Resource For Legitimate Work at Home Jobs Work from Anywhere in India This Is An...
On Mon, 4 Aug 2003 16:45:58 -0700 ... Yes, I'm already doing that. ... Ah, that makes sense. I was leaning towards something like you described above, but...
On Mon, 4 Aug 2003 20:41:34 -0400 ... The way I have it set up, every time I compile my code, the IDE also compiles the tests and then runs them as the final...
On Mon, 4 Aug 2003 19:40:43 -0500 ... Ah, yes, that also makes lots of sense. Now I have to decide between that approach and the one Phlip suggested :-) I'll...
... on ... FAILED ... could ... Think of the test code source file as a "programmer's user interface". UIs self-document, and provide short-cuts. The...
... Eeek! If you were typing source, your hands are on the keyboard, not the mouse! From the keyboard, tap <F4> to go to the offending line!! ... Read my...
... Agreed, except for this simple test: assertTrue(new ArrayList().isEmpty()); It was suggested to me always to write: Object expected = ...; Object actual =...
