How to raise quality of your software projects?

So what strange things have you heard, that has been done to lower the risk of having critical bugs in your software? What have given the best results and has been most cost efficient?

My opinion is, that if you have some very important logic in your project (like calculating prices), then it is good to make some testcases and show them to some other team members or to a client, because other people may spend only 10 minutes of his time and notice some really huge misunderstandigs...

JMeter tests also helps alot, because you can create very useful tests with very short period of time and those test doesn`t need to be changed very often. For example, there is a project that has been built for many years by approx. 3 programmers. Now someone comes and learns this project, then uses 1 week (with full time) for creating tests with JMeter and if all goes well, you have tests with test coverage up to 50 percent.

Comments

  • >So what strange things have you heard, that has been done to lower the risk of having critical bugs in your software?

    Testing, testing, and more testing, by as many people as you can get as long as they are not part of the programming team that worked on the project. You need testers who will make mistakes to find out how your program reacts to them. Make every attempt possible to screw the program up That's why larger software companies have teams that do nothing more then testing. And after that put the program out to the public for beta testing.
  • Testing (both functional tests and unit testing), and peer code reviews.
  • Short sprints (e.g. 1 month) and also daily (or over the day) stand-up meetings will help. Reduce the total number of active bugs because fixing tens of bugs at the end of the sprint can mess things up real bad.
Sign In or Register to comment.