INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: MC Development Process  (Read 801 times)

Platu

  • Regular Member
  • Junior Woodchuck
  • **
  • Posts: 63
  • I'm a llama!
MC Development Process
« on: January 05, 2004, 06:52:21 pm »

Hi Matt,

I've been amazed at how quickly you are able to keep turning out new builds with relatively few major bugs.  I'm a software developer as well and was just wondering if you pass your software through an automated testing system such as Winrunner. Our company has recently started exploring the posibility of using Winrunner (or other test automation tool) to help automate our long tedious process of manual test cases for new releases and I was just wondering if you guys had any luck with anything similar. If you still test the old fashion way I won't hold it against you.  Your product is excellent by the way.


-Platu
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72439
  • Where did I put my teeth?
Re:MC Development Process
« Reply #1 on: January 05, 2004, 07:56:27 pm »

Thanks.  We do it by brute force.  Frequent builds force us to get it as right as we can, so we don't ever allow things to get too loose.

The key is the team, not the tool.  It's a great group of experienced people.  Lots of talent and lots of depth, and they work together extremely well.  I just get to enjoy watching it.
Logged

dragyn

  • Guest
Re:MC Development Process
« Reply #2 on: January 05, 2004, 09:23:09 pm »

MC v10 Statistics as of 01/05/04 10.0.28 (In case anyone was wondering):

builds: 20 (2 Internal)
fixes: 76
new features: 24
changed features: 67
total changes: 167
Logged
Pages: [1]   Go Up