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. Testing old code in a new products can give unexpected results...

Testing old code in a new products can give unexpected results...

Scheduled Pinned Locked Moved The Lounge
testingbeta-testingquestionannouncement
16 Posts 10 Posters 1 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.
  • L Lost User

    If it doesn't smoke, ship it.

    M Offline
    M Offline
    megaadam
    wrote on last edited by
    #5

    If it is good stuff, smoke it.

    ... such stuff as dreams are made on

    G 1 Reply Last reply
    0
    • M megaadam

      It is finally happening! Your code has become self-aware and has fixed itself.

      ... such stuff as dreams are made on

      G Offline
      G Offline
      glennPattonWork3
      wrote on last edited by
      #6

      NOT my code! I'm testing it :sigh:

      1 Reply Last reply
      0
      • M megaadam

        If it is good stuff, smoke it.

        ... such stuff as dreams are made on

        G Offline
        G Offline
        glennPattonWork3
        wrote on last edited by
        #7

        Hmmm, Silicon Oxide and Carbide, Umm no thanks!:cool:

        1 Reply Last reply
        0
        • G glennPattonWork3

          Hi All, I am testing some code in a new version of an old product. It has suddenly started to pass a test it shouldn't. Time to dig deeper or time to report it and pass it on? I'm think its time to go deeper but am not sure?

          T Offline
          T Offline
          Tim Carmichael
          wrote on last edited by
          #8

          Since it isn't your code, dig deeper... find out what is wrong. Document what you are seeing, what you find, and what you do to resolve the issue.

          1 Reply Last reply
          0
          • G glennPattonWork3

            Hi All, I am testing some code in a new version of an old product. It has suddenly started to pass a test it shouldn't. Time to dig deeper or time to report it and pass it on? I'm think its time to go deeper but am not sure?

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

            If you know that the conditions are so that a test should fail, yet it doesn't fail, then there must be something wrong with your code! (Saym your code actually fails the test, but immediately thereafter, a write through a stray pointer changes the verdict from 'fail' to 'pass' ... Certainly not very likely, but not failing when you know that it should is not very likely either.) Gererally speaking: Failing to fail may indicate a failure.

            W 1 Reply Last reply
            0
            • G glennPattonWork3

              Hi All, I am testing some code in a new version of an old product. It has suddenly started to pass a test it shouldn't. Time to dig deeper or time to report it and pass it on? I'm think its time to go deeper but am not sure?

              M Offline
              M Offline
              Marc Clifton
              wrote on last edited by
              #10

              It used to be we would just test our code, usually by walking through it line by line (though maybe that's being optimistic) or, even more "archaic", we would write up acceptance test procedures and walk the application through the steps in the ATP. Now, with the advent of unit tests, what do we end up doing? Testing our tests! :rolleyes:

              Latest Article - Code Review - What You Can Learn From a Single Line of Code Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802

              1 Reply Last reply
              0
              • K kalberts

                If you know that the conditions are so that a test should fail, yet it doesn't fail, then there must be something wrong with your code! (Saym your code actually fails the test, but immediately thereafter, a write through a stray pointer changes the verdict from 'fail' to 'pass' ... Certainly not very likely, but not failing when you know that it should is not very likely either.) Gererally speaking: Failing to fail may indicate a failure.

                W Offline
                W Offline
                W Balboos GHB
                wrote on last edited by
                #11

                Member 7989122 wrote:

                Gererally speaking: Failing to fail may indicate a failure.

                I fail to see your point.

                Ravings en masse^

                "The difference between genius and stupidity is that genius has its limits." - Albert Einstein

                "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010

                1 Reply Last reply
                0
                • G glennPattonWork3

                  Hi All, I am testing some code in a new version of an old product. It has suddenly started to pass a test it shouldn't. Time to dig deeper or time to report it and pass it on? I'm think its time to go deeper but am not sure?

                  D Offline
                  D Offline
                  DerekT P
                  wrote on last edited by
                  #12

                  Depends - what's your job? Do you have access to the source? What did your boss ask you to do? What's your skillset? Is this a wind-up question? Asking daft questions can often give unexpected results too...

                  G 1 Reply Last reply
                  0
                  • D DerekT P

                    Depends - what's your job? Do you have access to the source? What did your boss ask you to do? What's your skillset? Is this a wind-up question? Asking daft questions can often give unexpected results too...

                    G Offline
                    G Offline
                    glennPattonWork3
                    wrote on last edited by
                    #13

                    My job is to test it. Not really specific its hardware or software 'it' being the metal box. Wasn't really a question to which I was expecting an answer more opions. :-D The person to ask daft question of was around but busy today (read don't bother him!) As for the source I am not touching it (safety critical system)... ;)

                    J 1 Reply Last reply
                    0
                    • G glennPattonWork3

                      My job is to test it. Not really specific its hardware or software 'it' being the metal box. Wasn't really a question to which I was expecting an answer more opions. :-D The person to ask daft question of was around but busy today (read don't bother him!) As for the source I am not touching it (safety critical system)... ;)

                      J Offline
                      J Offline
                      Jan Holst Jensen2
                      wrote on last edited by
                      #14

                      glennPattonWork wrote:

                      (safety critical system)

                      In that case it is easy: If it passes a test that previously failed, you need to raise it as an issue. In general: Passing a test that is supposed to fail is of course a failure. Doubly so in safety critical systems.

                      G 1 Reply Last reply
                      0
                      • J Jan Holst Jensen2

                        glennPattonWork wrote:

                        (safety critical system)

                        In that case it is easy: If it passes a test that previously failed, you need to raise it as an issue. In general: Passing a test that is supposed to fail is of course a failure. Doubly so in safety critical systems.

                        G Offline
                        G Offline
                        glennPattonWork3
                        wrote on last edited by
                        #15

                        Not to worry it was bounced back to those who can. Just the Monday mutters :)

                        J 1 Reply Last reply
                        0
                        • G glennPattonWork3

                          Not to worry it was bounced back to those who can. Just the Monday mutters :)

                          J Offline
                          J Offline
                          Jan Holst Jensen2
                          wrote on last edited by
                          #16

                          :thumbsup: :)

                          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