Results 1 to 3 of 3

Thread: Automated Tests

  1. #1
    Post Fiend
    Join Date
    Jul 2008
    Posts
    114

    Automated Tests

    This is actually getting kind of tiring, every change you guys make comes with a billion+1 OBVIOUS bugs. There's nothing subtle here, these are clear functionality bugs, which makes it painfully obvious that once you code something in you don't take the time to test it.

    Honestly, I don't know what kind of development model this is, where I work, for every patch there are 200 something automated functionality tests and manual testing as well, before we deploy it. So, in conclusion, just develop some damn tests and let them run to make sure the minimum functionality is there before you deploy an update.

  2. #2
    Member bcolargol's Avatar
    Join Date
    Aug 2009
    Posts
    33
    Agreed. With this kind of software each release should undergo extensive regression testing. A simple syntactic test can be used to discover these type of bugs easily.

  3. #3
    Forum Addict
    Join Date
    Oct 2009
    Posts
    1,228
    Hell , no need to go that far. Having a test server and trying out the basic functionality before going live would have caught 99% of those bugs. :/
    Quote Originally Posted by :p
    The chance of needing 20 NBs to cure the plague is c. 1/470 trillion.
    Your logic is non existent, You should read more than one post.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •