Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Twelve Days of Testing

Twelve Days of Testing

Scheduled Pinned Locked Moved The Lounge
testingbeta-testingtools
12 Posts 9 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Nagy Vilmos

    On the first day of testing my software gave to me a crash on exit at the end. On the second day of testing my software gave to me two runtime errors and a crash on exit at the end. On the third day of testing my software gave to me three missing functions, two runtime errors and a crash on exit at the end. On the forth day of testing my software gave to me four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the fifth day of testing my software gave to me five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the sixth day of testing my software gave to me six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the seventh day of testing my software gave to me seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eighth day of testing my software gave to me eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the ninth day of testing my software gave to me nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the tenth day of testing my software gave to me ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eleventh day of testing my software gave to me eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the twelfth day of testing my software gave to me twelve pages hanging, eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end.


    S Offline
    S Offline
    Simon P Stevens
    wrote on last edited by
    #2

    Nice.

    Simon

    1 Reply Last reply
    0
    • N Nagy Vilmos

      On the first day of testing my software gave to me a crash on exit at the end. On the second day of testing my software gave to me two runtime errors and a crash on exit at the end. On the third day of testing my software gave to me three missing functions, two runtime errors and a crash on exit at the end. On the forth day of testing my software gave to me four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the fifth day of testing my software gave to me five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the sixth day of testing my software gave to me six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the seventh day of testing my software gave to me seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eighth day of testing my software gave to me eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the ninth day of testing my software gave to me nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the tenth day of testing my software gave to me ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eleventh day of testing my software gave to me eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the twelfth day of testing my software gave to me twelve pages hanging, eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end.


      realJSOPR Offline
      realJSOPR Offline
      realJSOP
      wrote on last edited by
      #3

      Nagy Vilmos wrote:

      On the third day of testing my software gave to me...

      A pain in the ass, so I handed the testing off to a junior programmer.

      .45 ACP - because shooting twice is just silly
      -----
      "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
      -----
      "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

      N 1 Reply Last reply
      0
      • realJSOPR realJSOP

        Nagy Vilmos wrote:

        On the third day of testing my software gave to me...

        A pain in the ass, so I handed the testing off to a junior programmer.

        .45 ACP - because shooting twice is just silly
        -----
        "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
        -----
        "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

        N Offline
        N Offline
        Nagy Vilmos
        wrote on last edited by
        #4

        And who, pray tell, signed off the development? It's just that type of slacking which has caused global warming, the credit crunch and Mrs Wife being p'ed because I had a 'refresher' at beer lunch time.


        Panic, Chaos, Destruction. My work here is done.

        realJSOPR 1 Reply Last reply
        0
        • N Nagy Vilmos

          And who, pray tell, signed off the development? It's just that type of slacking which has caused global warming, the credit crunch and Mrs Wife being p'ed because I had a 'refresher' at beer lunch time.


          Panic, Chaos, Destruction. My work here is done.

          realJSOPR Offline
          realJSOPR Offline
          realJSOP
          wrote on last edited by
          #5

          Well, being the programmer that write the code, you certainly don't want to be the one testing it. Besides, the description of the problems above would most certainly not be an issue with modern compilers and IDEs. Missing functions? Not possible to compile, much less test.

          .45 ACP - because shooting twice is just silly
          -----
          "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
          -----
          "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

          N 1 Reply Last reply
          0
          • realJSOPR realJSOP

            Well, being the programmer that write the code, you certainly don't want to be the one testing it. Besides, the description of the problems above would most certainly not be an issue with modern compilers and IDEs. Missing functions? Not possible to compile, much less test.

            .45 ACP - because shooting twice is just silly
            -----
            "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
            -----
            "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

            N Offline
            N Offline
            Nagy Vilmos
            wrote on last edited by
            #6

            John, it's three something after lunch here the day before the night before Christmas. Right now I'm screaming #bad# words because the frakin eejits at M$ think it's a good idea to overwrite my code because the IDE thinks its kack is better. I will be drinking, heavily, tonight.


            Panic, Chaos, Destruction. My work here is done.

            K 1 Reply Last reply
            0
            • N Nagy Vilmos

              On the first day of testing my software gave to me a crash on exit at the end. On the second day of testing my software gave to me two runtime errors and a crash on exit at the end. On the third day of testing my software gave to me three missing functions, two runtime errors and a crash on exit at the end. On the forth day of testing my software gave to me four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the fifth day of testing my software gave to me five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the sixth day of testing my software gave to me six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the seventh day of testing my software gave to me seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eighth day of testing my software gave to me eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the ninth day of testing my software gave to me nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the tenth day of testing my software gave to me ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eleventh day of testing my software gave to me eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the twelfth day of testing my software gave to me twelve pages hanging, eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end.


              L Offline
              L Offline
              Lost User
              wrote on last edited by
              #7

              *applause* :-D

              L u n a t i c F r i n g e

              1 Reply Last reply
              0
              • N Nagy Vilmos

                On the first day of testing my software gave to me a crash on exit at the end. On the second day of testing my software gave to me two runtime errors and a crash on exit at the end. On the third day of testing my software gave to me three missing functions, two runtime errors and a crash on exit at the end. On the forth day of testing my software gave to me four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the fifth day of testing my software gave to me five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the sixth day of testing my software gave to me six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the seventh day of testing my software gave to me seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eighth day of testing my software gave to me eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the ninth day of testing my software gave to me nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the tenth day of testing my software gave to me ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eleventh day of testing my software gave to me eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the twelfth day of testing my software gave to me twelve pages hanging, eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end.


                C Offline
                C Offline
                Caslen
                wrote on last edited by
                #8

                You got bored with testing then...

                1 Reply Last reply
                0
                • N Nagy Vilmos

                  John, it's three something after lunch here the day before the night before Christmas. Right now I'm screaming #bad# words because the frakin eejits at M$ think it's a good idea to overwrite my code because the IDE thinks its kack is better. I will be drinking, heavily, tonight.


                  Panic, Chaos, Destruction. My work here is done.

                  K Offline
                  K Offline
                  KungFuCoder
                  wrote on last edited by
                  #9

                  Boy do I know that one! It could at least give a "It looks like you have a working program. Would you like me to add the bugs in for you ? Yes / No" popup

                  1 Reply Last reply
                  0
                  • N Nagy Vilmos

                    On the first day of testing my software gave to me a crash on exit at the end. On the second day of testing my software gave to me two runtime errors and a crash on exit at the end. On the third day of testing my software gave to me three missing functions, two runtime errors and a crash on exit at the end. On the forth day of testing my software gave to me four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the fifth day of testing my software gave to me five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the sixth day of testing my software gave to me six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the seventh day of testing my software gave to me seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eighth day of testing my software gave to me eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the ninth day of testing my software gave to me nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the tenth day of testing my software gave to me ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eleventh day of testing my software gave to me eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the twelfth day of testing my software gave to me twelve pages hanging, eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end.


                    P Offline
                    P Offline
                    Plamen Dragiyski
                    wrote on last edited by
                    #10

                    Your software get better, now you must add paid online support and you will have "enterprise product". :laugh:

                    1 Reply Last reply
                    0
                    • N Nagy Vilmos

                      On the first day of testing my software gave to me a crash on exit at the end. On the second day of testing my software gave to me two runtime errors and a crash on exit at the end. On the third day of testing my software gave to me three missing functions, two runtime errors and a crash on exit at the end. On the forth day of testing my software gave to me four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the fifth day of testing my software gave to me five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the sixth day of testing my software gave to me six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the seventh day of testing my software gave to me seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eighth day of testing my software gave to me eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the ninth day of testing my software gave to me nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the tenth day of testing my software gave to me ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eleventh day of testing my software gave to me eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the twelfth day of testing my software gave to me twelve pages hanging, eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end.


                      Y Offline
                      Y Offline
                      Yusubov E
                      wrote on last edited by
                      #11

                      It proves that you are a good tester !!! Switch your title on a NEW Year ;)

                      1 Reply Last reply
                      0
                      • N Nagy Vilmos

                        On the first day of testing my software gave to me a crash on exit at the end. On the second day of testing my software gave to me two runtime errors and a crash on exit at the end. On the third day of testing my software gave to me three missing functions, two runtime errors and a crash on exit at the end. On the forth day of testing my software gave to me four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the fifth day of testing my software gave to me five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the sixth day of testing my software gave to me six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the seventh day of testing my software gave to me seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eighth day of testing my software gave to me eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the ninth day of testing my software gave to me nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the tenth day of testing my software gave to me ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the eleventh day of testing my software gave to me eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end. On the twelfth day of testing my software gave to me twelve pages hanging, eleven colours clashing, ten loops a thrashing, nine backups failing, eight networks stopping, seven servers faulting, six clients hanging, five test script errors, four logic blunders, three missing functions, two runtime errors and a crash on exit at the end.


                        T Offline
                        T Offline
                        Trevortni
                        wrote on last edited by
                        #12

                        Eh, call them all "features" and ship it.

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups