shame to my tester or me?
-
Ooh, painful. Did you feel guilty enough to fix it for them even though your contract was over?
Well, it kinda fixed itself...about midnight on that day as I recall. :laugh: I must not have made too bad of impression as I eventually received another contract to upgrade all of their software to use C# front-ends and SQL server back-ends, so the whole date thing was never an issue after that day.
-NP Never underestimate the creativity of the end-user.
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
Both. It isn't exactly hidden that people use different formats across the world - even some Americans are aware of it. It's not exactly difficult to work with different formats these days either. And are you saying that it took less that twelve days to develop the software? Or that you didn't test your own code at all for three weeks of each month? It's a rookie mistake, for both developer and the tester - it doesn't bode well for the long term reliabilty of the software from where I'm sitting.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Both. It isn't exactly hidden that people use different formats across the world - even some Americans are aware of it. It's not exactly difficult to work with different formats these days either. And are you saying that it took less that twelve days to develop the software? Or that you didn't test your own code at all for three weeks of each month? It's a rookie mistake, for both developer and the tester - it doesn't bode well for the long term reliabilty of the software from where I'm sitting.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
Shame on tester if the software requirement/design requirement mentioned the format of the date. Shame on you if it didn't. If your tester doesn't have an up to date requirement specification/design document he's not to blame, but you are. It's pointless having a tester if you don't give him something to test the software against. Sure, he might find some bugs but he'll miss most.
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
it was just a plugin in existing software. And yes its a very silly mistake by me(hope my boss will not see tht), but as long as i can pass responsibility to tester why i care :laugh: :laugh: :laugh:
And this is exactly where a lot of stuff goes wrong...
kdgupta87 wrote:
it was just a ...
and
kdgupta87 wrote:
but as long as i can pass responsibility to tester why i care
Take what you do seriously, and take the responsibilty for what you do. Those smily icons aside, with a mentality like yours you wouldn't last long if you were ever to work with me...
-
And this is exactly where a lot of stuff goes wrong...
kdgupta87 wrote:
it was just a ...
and
kdgupta87 wrote:
but as long as i can pass responsibility to tester why i care
Take what you do seriously, and take the responsibilty for what you do. Those smily icons aside, with a mentality like yours you wouldn't last long if you were ever to work with me...
:thumbsup:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
it was just a plugin in existing software. And yes its a very silly mistake by me(hope my boss will not see tht), but as long as i can pass responsibility to tester why i care :laugh: :laugh: :laugh:
I have to agree with cptKoala - take responsibility for your mistakes. If nothing else, you may want your tester on your side, rather than against you. If you blame him for your mistakes, you won't makes friends there...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
Well obviously its your fault! Testers are not there to test for programmer errors, they are there for testing whether or not the system meets the specification. And if you think you can get away with blaming the testers for your own lack of care and commitment, then you are horrendously wrong. Whenever writing date related code I always make sure I unit test for formats because the system can be used in any locale, I don't see how its the tester's fault. Its just common sense and its about sense of ownership for your work.
-
There's a lesson to learn here about using an unambiguous date format. If you have to use string date transfer at all, that is, but for passing data between applications that is often the case (e.g. if you're using web services or similar protocols). I use either 2012-05-02 or 2-May-2012, usually the former, if I'm saving or passing dates and need to be able to understand them at the other end. Your tester should have tested this, though. That's the point of having a tester.
-
And this is exactly where a lot of stuff goes wrong...
kdgupta87 wrote:
it was just a ...
and
kdgupta87 wrote:
but as long as i can pass responsibility to tester why i care
Take what you do seriously, and take the responsibilty for what you do. Those smily icons aside, with a mentality like yours you wouldn't last long if you were ever to work with me...
-
I have to agree with cptKoala - take responsibility for your mistakes. If nothing else, you may want your tester on your side, rather than against you. If you blame him for your mistakes, you won't makes friends there...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Well obviously its your fault! Testers are not there to test for programmer errors, they are there for testing whether or not the system meets the specification. And if you think you can get away with blaming the testers for your own lack of care and commitment, then you are horrendously wrong. Whenever writing date related code I always make sure I unit test for formats because the system can be used in any locale, I don't see how its the tester's fault. Its just common sense and its about sense of ownership for your work.
-
Shame on tester if the software requirement/design requirement mentioned the format of the date. Shame on you if it didn't. If your tester doesn't have an up to date requirement specification/design document he's not to blame, but you are. It's pointless having a tester if you don't give him something to test the software against. Sure, he might find some bugs but he'll miss most.
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
certainly u are right, i should more careful and serious next time, i know for sure that this way i cant last long, i am in learning phase still now .
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
I don't want to be mean, but, If I did that then I would shame me End If Testers never know what is really happening, however, they do find weird things sometimes. The best testers are the end users as they are so weird and inventive that they do things that no one would or almost could ever test for. Look at it this way, you most likely will never make this mistake again. We have all done something like this at some time. So just learn and grow. Maybe you should have started your project on the 1st of April instead of the 2nd. Then you could have blamed the tester.
-
When you want to say 10001 you say "ten thousand and one" and not "one ten thousand". I think it is a mark and as such it should start with the biggest aproach and then go refine to the day as you do with hour minute second...
Paulo Gomes Over and Out :D
-
When you want to say 10001 you say "ten thousand and one" and not "one ten thousand". I think it is a mark and as such it should start with the biggest aproach and then go refine to the day as you do with hour minute second...
Paulo Gomes Over and Out :D
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
You.
-
In dutch it is different. 62 you say " sixty two" but in dutch you say "twee en zestig" = "two and sixty" we also use the metric system :D
