Well, thats a supprise...
-
Hi All, I am being called by my Boss & HR to a meeting tomorrow, for raising faults, in the system I am testing, JIRA I fear. So I was told by my boss to test, identify and not fix faults, raise the faults as defects. I have being doing this I raised Faults as Defects, I first get a talking to as I am causing too much on the back log. If I am to test this 'thing' properly a bug will display in more than one area. If I am not allowed to poke around the fault or ask others what other sections that could be affected, I am going to raise faults the fault is linked to a test ticket (right?) the issue appears to be the Dev team have identified the fault and then fixed but haven't gone through the ticket back log to link all the tickets that are linked. These tickets stay active and then someone who has permissions takes it off the back log, right? I notification that a ticket has been cancelled by not my boss. I am now lost, sorry for the rant! Glenn
similar to what Greg said perhaps your function was not to find the faults, but rather to prove the correctness. ... as to any potentially significant technical issues perhaps at most check they're covered in the T&C / disclaimers / error margins.
<< Signature removed due to multiple copyright violations >>
-
Hi All, I am being called by my Boss & HR to a meeting tomorrow, for raising faults, in the system I am testing, JIRA I fear. So I was told by my boss to test, identify and not fix faults, raise the faults as defects. I have being doing this I raised Faults as Defects, I first get a talking to as I am causing too much on the back log. If I am to test this 'thing' properly a bug will display in more than one area. If I am not allowed to poke around the fault or ask others what other sections that could be affected, I am going to raise faults the fault is linked to a test ticket (right?) the issue appears to be the Dev team have identified the fault and then fixed but haven't gone through the ticket back log to link all the tickets that are linked. These tickets stay active and then someone who has permissions takes it off the back log, right? I notification that a ticket has been cancelled by not my boss. I am now lost, sorry for the rant! Glenn
In the good old days of raising bugs on paper forms, I was sent to test a new application and given 150 sheets for the bug reports. On the second day I was severely told off for being at the photocopier instead of looking at their new application. It never occurred to them that I had already found and documented 150 faults and needed more report logs to write on. So things do not change. Testers are there to confirm that the developers are right to congratulate themselves on a job well done, not to test things. "The purpose of testing is to find bugs, not to prove their absence" [I have yet to find the source of this quote - it is someone like C A R Hoare or Edgsar Dijkstra or Donald Knuth; if you know who originally said it, please let me know]
-
In the good old days of raising bugs on paper forms, I was sent to test a new application and given 150 sheets for the bug reports. On the second day I was severely told off for being at the photocopier instead of looking at their new application. It never occurred to them that I had already found and documented 150 faults and needed more report logs to write on. So things do not change. Testers are there to confirm that the developers are right to congratulate themselves on a job well done, not to test things. "The purpose of testing is to find bugs, not to prove their absence" [I have yet to find the source of this quote - it is someone like C A R Hoare or Edgsar Dijkstra or Donald Knuth; if you know who originally said it, please let me know]
-
similar to what Greg said perhaps your function was not to find the faults, but rather to prove the correctness. ... as to any potentially significant technical issues perhaps at most check they're covered in the T&C / disclaimers / error margins.
<< Signature removed due to multiple copyright violations >>
Well the company ethic is to 'Make Life Easier', Plus this is firmware in a critical infrastructure! I was under the impression finding and raising faults was a good thing? :omg:
-
"The purpose of testing is to find bugs, not to prove their absence." I don't know who said it, but I think we can rule out formal methods weenies.
Program testing can be used to show the presence of bugs, but never to show their absence!
Dijkstra (1970) "Notes On Structured Programming" (EWD249), Section 3 ("On The Reliability of Mechanisms"), corollary at the end.He's guilty of several different versions of that quote.
Wrong is evil and must be defeated. - Jeff Ello
-
Hi All, I am being called by my Boss & HR to a meeting tomorrow, for raising faults, in the system I am testing, JIRA I fear. So I was told by my boss to test, identify and not fix faults, raise the faults as defects. I have being doing this I raised Faults as Defects, I first get a talking to as I am causing too much on the back log. If I am to test this 'thing' properly a bug will display in more than one area. If I am not allowed to poke around the fault or ask others what other sections that could be affected, I am going to raise faults the fault is linked to a test ticket (right?) the issue appears to be the Dev team have identified the fault and then fixed but haven't gone through the ticket back log to link all the tickets that are linked. These tickets stay active and then someone who has permissions takes it off the back log, right? I notification that a ticket has been cancelled by not my boss. I am now lost, sorry for the rant! Glenn
I think somewhere it says that "always make the boss look good". Or at least, not bad (no matter how much you want to). But that reminds me: I went to a meeting once with users to discuss "enhancements" (to the software I wrote), while the little cretin I was with filed the requests as a "bug report". I told him what was on my mind.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
Hi All, I am being called by my Boss & HR to a meeting tomorrow, for raising faults, in the system I am testing, JIRA I fear. So I was told by my boss to test, identify and not fix faults, raise the faults as defects. I have being doing this I raised Faults as Defects, I first get a talking to as I am causing too much on the back log. If I am to test this 'thing' properly a bug will display in more than one area. If I am not allowed to poke around the fault or ask others what other sections that could be affected, I am going to raise faults the fault is linked to a test ticket (right?) the issue appears to be the Dev team have identified the fault and then fixed but haven't gone through the ticket back log to link all the tickets that are linked. These tickets stay active and then someone who has permissions takes it off the back log, right? I notification that a ticket has been cancelled by not my boss. I am now lost, sorry for the rant! Glenn
Good grief. Sounds like an exercise in petty mindedness from some Jira Ninja to me, and why would HR would need to be involved in such?
Regards, Rob Philpott.
-
Good grief. Sounds like an exercise in petty mindedness from some Jira Ninja to me, and why would HR would need to be involved in such?
Regards, Rob Philpott.
HR are involved as I had done this before (why wasn't the thing changed then?), I don't quite know what the outcome will be. Hope for the best, expect the worse!
-
Hi All, I am being called by my Boss & HR to a meeting tomorrow, for raising faults, in the system I am testing, JIRA I fear. So I was told by my boss to test, identify and not fix faults, raise the faults as defects. I have being doing this I raised Faults as Defects, I first get a talking to as I am causing too much on the back log. If I am to test this 'thing' properly a bug will display in more than one area. If I am not allowed to poke around the fault or ask others what other sections that could be affected, I am going to raise faults the fault is linked to a test ticket (right?) the issue appears to be the Dev team have identified the fault and then fixed but haven't gone through the ticket back log to link all the tickets that are linked. These tickets stay active and then someone who has permissions takes it off the back log, right? I notification that a ticket has been cancelled by not my boss. I am now lost, sorry for the rant! Glenn
I hate to be the bearer of bad news, but HR being involved is always a bad thing. If you are lucky, you will be put on a Performance Improvement Plan which is a very serious reprimand. If unlucky, it likely means you will be sacked. In either case, you should immediately be updating your CV/resume and visiting all of the relevant job boards.
-
I hate to be the bearer of bad news, but HR being involved is always a bad thing. If you are lucky, you will be put on a Performance Improvement Plan which is a very serious reprimand. If unlucky, it likely means you will be sacked. In either case, you should immediately be updating your CV/resume and visiting all of the relevant job boards.
Indeed. In these cases, HR represents the company's desire to be rid of an employee without repercussions to the company. Take vacation days now and get started looking. May I recommend a _sane_ workplace for a change?
