shame to my tester or me?
-
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
-
Oh, you're gonna discuss date preferences now?! Then what ... coding style? How about favorite colour?
-
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 was merely, sarcastically, suggesting that such things will never be agreed upon. Heck, I live in a country [US] that uses pounds and inches to measure things. We also use a format for our dates that, as far as I can tell, is not used outside the US.
-
Oh, that's definitely true. And it sounds like it was a relatively low tariff place to make the mistake (easy to notice, easy to find the cause and fix, not a critical system), so all's good in the end. But it is more a tester mistake than a dev mistake, in my opinion.
-
Doesn't sound like it's anything the tester could have tested if it's a system date related issue. If the date was data the tester entered I agree, but that's not how I read it.
I agree. Testers cannot test -everything- ... That is like expecting a coder to produce bug free code. In my experience, testers test functions against spec, and then test data/input (boundary conditions, extremes, absence, ridiculous) and call it a day. Unfortunately, this low hanging fruit approach leaves sneaky, subtle bugs like this undetected.
-
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
That sounds like exactly the sort of bug which would be preempted by a good set of unit tests. Test Driven Development takes some time to get used to doing, but it definitely works.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
why all over the world, everyone not following the same date time format, they should think about poor programmers like me :confused:
No - see - it's actually done to give us a boost in morale by allowing us to feel superior!!
-
Oh, you're gonna discuss date preferences now?! Then what ... coding style? How about favorite colour?
Maybe we can throw in a favorite editor discussion, and for bonus points debate newline characters!
-
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 you, and your tester too. We should follow the system when using date and time. The display format is only for presentation. If your code is going to send data all over the world, what is the right format?
-
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
First shame on you. When transfer any data over the wire, you should it do it in a system independent format. When for some reason it is impossible to do that, you should take system differences in account. That is: verify what differences there are and (unit)test you're code against the whole valid range and handle invalid data. Shame on the tester to, he also should be aware of difficulties in the domain he is testing. But most of all shame on you. A developer never can hide behind the the tester (or even the architect). He has it's own responsibility to make the software work, without errors.
-
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
My vote is for the tester. You're a programmer, you're expected to screw up. :laugh: The tester passed your code in one day. You might have 100 more bugs lurking in your code. (Which could still be true after 100 days of testing.) Just think about sending yy-mm-dd, your code could still be humming along fine for 19 years. (I'm guessing someone might eventually notice the dates don't match/make sense.)