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. about testing

about testing

Scheduled Pinned Locked Moved The Lounge
beta-testingquestiontesting
6 Posts 5 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.
  • I Offline
    I Offline
    Ingenius
    wrote on last edited by
    #1

    I hope it`s not a programming question. If it is then please make me aware of it. Here`s the question. I am having trouble with the testing phase. I`ve done the thing (say it`s something more complex), well, after considering all the cases and testing it, it should a phase in which you do an exhaustive test on the thing, I guess the thing that is called "beta-testing". Well, I don`t have the luxury of beta-testing (my bosses want it immediatly in the production) and the "final test" that I do to conclude it is always working very hard and, unfortunately, almost always leaves bugs on behind. How do you guys do it? ---------------------------- World could be better! Cornel Rebegea software developer Infodata SRL Bacau, Romania

    D 1 Reply Last reply
    0
    • I Ingenius

      I hope it`s not a programming question. If it is then please make me aware of it. Here`s the question. I am having trouble with the testing phase. I`ve done the thing (say it`s something more complex), well, after considering all the cases and testing it, it should a phase in which you do an exhaustive test on the thing, I guess the thing that is called "beta-testing". Well, I don`t have the luxury of beta-testing (my bosses want it immediatly in the production) and the "final test" that I do to conclude it is always working very hard and, unfortunately, almost always leaves bugs on behind. How do you guys do it? ---------------------------- World could be better! Cornel Rebegea software developer Infodata SRL Bacau, Romania

      D Offline
      D Offline
      Daniel Turini
      wrote on last edited by
      #2

      Ingenius wrote: How do you guys do it? I think that the main problem is with unreasonable deadlines. It doesn’t matter the project size or the deadline, you should always leave time (at least 5%~10% of the time) for testing and bug-fixing. As (most of) testing can only be done when the coding ends, it's always sacrified, along with the setup program. Never negotiate deadlines in a way that terminates with “Ok, I’ll sleep less”: (A) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, I’ll sleep less” (B) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, which features you think we should remove?” User: “None. I need it in 45 days” Programmer: “Ok, I’ll sleep less” (C) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “Ok, we’ll sleep less” This is how it should be done: Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “With that we can also deliver A” User: “Only that?” Programmer: “Nine women can’t make a baby in one month” User: “Ok” Due to technical difficulties my previous signature, "I see dumb people" will be off until further notice. Too many people were thinking I was talking about them... :sigh:

      M J A I 4 Replies Last reply
      0
      • D Daniel Turini

        Ingenius wrote: How do you guys do it? I think that the main problem is with unreasonable deadlines. It doesn’t matter the project size or the deadline, you should always leave time (at least 5%~10% of the time) for testing and bug-fixing. As (most of) testing can only be done when the coding ends, it's always sacrified, along with the setup program. Never negotiate deadlines in a way that terminates with “Ok, I’ll sleep less”: (A) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, I’ll sleep less” (B) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, which features you think we should remove?” User: “None. I need it in 45 days” Programmer: “Ok, I’ll sleep less” (C) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “Ok, we’ll sleep less” This is how it should be done: Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “With that we can also deliver A” User: “Only that?” Programmer: “Nine women can’t make a baby in one month” User: “Ok” Due to technical difficulties my previous signature, "I see dumb people" will be off until further notice. Too many people were thinking I was talking about them... :sigh:

        M Offline
        M Offline
        Maxwell Chen
        wrote on last edited by
        #3

        Cool. :cool::-D


        Maxwell Chen

        1 Reply Last reply
        0
        • D Daniel Turini

          Ingenius wrote: How do you guys do it? I think that the main problem is with unreasonable deadlines. It doesn’t matter the project size or the deadline, you should always leave time (at least 5%~10% of the time) for testing and bug-fixing. As (most of) testing can only be done when the coding ends, it's always sacrified, along with the setup program. Never negotiate deadlines in a way that terminates with “Ok, I’ll sleep less”: (A) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, I’ll sleep less” (B) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, which features you think we should remove?” User: “None. I need it in 45 days” Programmer: “Ok, I’ll sleep less” (C) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “Ok, we’ll sleep less” This is how it should be done: Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “With that we can also deliver A” User: “Only that?” Programmer: “Nine women can’t make a baby in one month” User: “Ok” Due to technical difficulties my previous signature, "I see dumb people" will be off until further notice. Too many people were thinking I was talking about them... :sigh:

          J Offline
          J Offline
          Jonathan de Halleux
          wrote on last edited by
          #4

          Daniel Turini wrote: “Nine women can’t make a baby in one month” Excellent :-D Jonathan de Halleux - My Blog - www.dotnetwiki.org - MbUnit - QuickGraph - NCollection

          1 Reply Last reply
          0
          • D Daniel Turini

            Ingenius wrote: How do you guys do it? I think that the main problem is with unreasonable deadlines. It doesn’t matter the project size or the deadline, you should always leave time (at least 5%~10% of the time) for testing and bug-fixing. As (most of) testing can only be done when the coding ends, it's always sacrified, along with the setup program. Never negotiate deadlines in a way that terminates with “Ok, I’ll sleep less”: (A) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, I’ll sleep less” (B) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, which features you think we should remove?” User: “None. I need it in 45 days” Programmer: “Ok, I’ll sleep less” (C) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “Ok, we’ll sleep less” This is how it should be done: Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “With that we can also deliver A” User: “Only that?” Programmer: “Nine women can’t make a baby in one month” User: “Ok” Due to technical difficulties my previous signature, "I see dumb people" will be off until further notice. Too many people were thinking I was talking about them... :sigh:

            A Offline
            A Offline
            Aryo Handono
            wrote on last edited by
            #5

            Excellent way of bargaining :-D "Courage choose who will follow, Fate choose who will lead" - Lord Gunner, Septerra Core "Press any key to continue, where's the ANY key ?" - Homer Simpsons Drinking gives me amazing powers of insight. I can solve all the worlds problems when drunk, but can never remember the solutions in the morning. - Michael P Butler to Paul Watson on 12/08/03

            1 Reply Last reply
            0
            • D Daniel Turini

              Ingenius wrote: How do you guys do it? I think that the main problem is with unreasonable deadlines. It doesn’t matter the project size or the deadline, you should always leave time (at least 5%~10% of the time) for testing and bug-fixing. As (most of) testing can only be done when the coding ends, it's always sacrified, along with the setup program. Never negotiate deadlines in a way that terminates with “Ok, I’ll sleep less”: (A) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, I’ll sleep less” (B) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, which features you think we should remove?” User: “None. I need it in 45 days” Programmer: “Ok, I’ll sleep less” (C) Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “Ok, we’ll sleep less” This is how it should be done: Programmer: “This project will take three months” User: “I need it in 45 days” Programmer: “Ok, we’ll remove the features A,B and C, deliver it in 45 days and deliver the rest on 45 days more” User: “Can’t you just add another programmer to the staff?” Programmer: “With that we can also deliver A” User: “Only that?” Programmer: “Nine women can’t make a baby in one month” User: “Ok” Due to technical difficulties my previous signature, "I see dumb people" will be off until further notice. Too many people were thinking I was talking about them... :sigh:

              I Offline
              I Offline
              Ingenius
              wrote on last edited by
              #6

              I guess you are right. I never thought it this way.:rolleyes: ---------------------------- World could be better! Cornel Rebegea software developer Infodata SRL Bacau, Romania

              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