Squirrel
  • Member for 10 years, 6 months
  • Last seen more than 10 years ago
  • London, United Kingdom
1.5 Million lines of code. 0 tests. Where should we start?
7 votes

Step 0, Get the build automated when they check into the source control system. TeamCity pro could probably be made to checkout and run a command - it is and it's free and easy to set up. Step 1, ...

View answer
What goes in your definition of done (DoD) ?
6 votes

The elephant in the room: maintenance. How do we maintain this new feature: what things need to be configurable? can we easily roll this out (what's the roll out?)? what support tools do we need to ...

View answer
Developing Unit Tests While Refactoring Legacy Code?
6 votes

I think Stacy calls it 'Branching by Abstraction' For legacy code the best approch I've found is to find pinch points in your code where it's easy to insert an interface covering the inputs and ...

View answer
If I didn't use TDD but want to transition to agile, should I go back and create those unit tests?
3 votes

The key question is can you afford for it to go wrong? And the answer to this quite often is dependent on how quickly you can fix the problem if it occurs - debug it until it works in production. ...

View answer
Making scrum-fall work for the short-term
3 votes

Quite a few software projects have a tick-tock model of a feature version, then a stable version and I see this as similar on a smaller scail. The key thing is not to test things that the devs know ...

View answer
How does a tester decide how much debugging/investigation to do before handing an issue over to development?
2 votes

I'd argue, that when you're thinking that question, it's the right time. But wait, if you can, bring them over and go through it with them - you've got it in a debugger - if they're in the building ...

View answer
Best article/site to describe "Software Testing as a Service" concept and suggest comparable metrics
2 votes

I've always thought of software QA as enabling change. I.e. making changes less risky and thus enabling quicker turnarounds. However there are clearly pleantly of QA practices that build up brittle ...

View answer
Deployment Testing
2 votes

Agree with Lyndon, but why just for the release? how about heartbeat tests that run periodically checking that everything is as it should be. This way not only the upgrade will get tested, but if ...

View answer
Xml Diffing Best Practices
2 votes

One example of software that could be used for xml testing: http://xmlstar.sourceforge.net/ I think the only thing missing is being able to sort an xpath based on a child xpath. E.g. <xml> ...

View answer
Automate verification of emails being received
2 votes

I think this is related to this question which suggests a SMTP pretend server: Testing email generation but I suspect this would need to be extended to 'know' about certain emails and be able to ...

View answer
Transition from all manual testing to automated testing
1 votes

Download Hudson or preferably TeamCity Pro for free. Point it to your source code and ask it to run the compile. Write the simplest noddy test you can think of. Ask the CI server to run the test. The ...

View answer
My team codes in one language, I want to test using another. What can go wrong?
1 votes

Keep using the same two languages (KISS): C# English* Use http://specflow.org/ to have gerkin style text only tests. It's not fancy and there's very little to go wrong with it. Plays nicely with ...

View answer
What's the most efficient way to run lots of tests?
1 votes

On thoughtworks tech radar I noticed this in the right direction: https://github.com/test-load-balancer I think it's probably early days for nunit / team city integration but it's the kind of thing ...

View answer
How often do you run long automated user acceptance tests?
1 votes

As often as you can afford to. They are automated after all. If they're robust and don't give you false positives, then ideally every commit once the compile and other tests have passed, then kick ...

View answer