Testing old code in a new products can give unexpected results...
-
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?
-
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?
I'd dig deeper - sound like the test is faulty, and that could impact current equipment.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
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?
-
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?
-
It is finally happening! Your code has become self-aware and has fixed itself.
... such stuff as dreams are made on
NOT my code! I'm testing it :sigh:
-
Hmmm, Silicon Oxide and Carbide, Umm no thanks!:cool:
-
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?
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.
-
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?
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.
-
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?
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
-
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.
Member 7989122 wrote:
Gererally speaking: Failing to fail may indicate a failure.
I fail to see your point.
"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
-
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?
-
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...
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)... ;)
-
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)... ;)
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.
-
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.
Not to worry it was bounced back to those who can. Just the Monday mutters :)
-
Not to worry it was bounced back to those who can. Just the Monday mutters :)
:thumbsup: :)
