Detecting Issues

  • Comments posted to this topic are about the item Detecting Issues

  • I guess it was always going to be difficult to collect statistics on the early captured defects. Especially when a fair number of them are communicated verbally and/or form part of a manual activity.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Those potential issues that never get to the customer are wins for me, and I think this is something we should be proud of as software engineers and testers.

    Software engineers are paid for fixing issues, and never - for absence of them.
    And being proud - is not something what will pay your bill.

    _____________
    Code for TallyGenerator

  • Sergiy - Wednesday, March 1, 2017 12:34 AM

    ...Software engineers are paid for fixing issues, and never - for absence of them...

    Not in my experience. Sounds like you need to experience better management.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Gary Varga - Wednesday, March 1, 2017 4:06 AM

    Sergiy - Wednesday, March 1, 2017 12:34 AM

    ...Software engineers are paid for fixing issues, and never - for absence of them...

    Not in my experience. Sounds like you need to experience better management.

    This did make me think a bit though - we'll be applauded for getting stuff out the door on time even if there are a few minor issues that need correction, often inevitable in any software release. I'm going to say there is perhaps less appreciation for the boring developers whose software doesn't ever create any kind of fuss, who can easily accommodate upgrade requirements etc. Having said that, it is my mantle and I wear it well!

  • Oh, really?

    How much did they pay you, say last month, for the software which you developed 5 years ago and which is working since then with no issues?

    Ah, you probably never came across such software.

    In hour experience.

    🙂

    _____________
    Code for TallyGenerator

  • Sergiy - Wednesday, March 1, 2017 4:43 AM

    Oh, really?How much did they pay you, say last month, for the software which you developed 5 years ago and which is working since then with no issues?Ah, you probably never came across such software.In hour experience.:-)

    Hey, I get paid the same whatever work there is to be done. It's just that by not being embroiled in old issues and having happy customers, you're more likely to be elevated and be able to work on new and bigger projects.

  • Measuring the number of defects where I work is fairly easy. Not so easy is to know how to compare those levels across projects, and how to measure technical debt.

    There are some interesting thoughts here: https://techbeacon.com/what-makes-good-qa-tester-4-kpis-essential-software-testing

    412-977-3526 call/text

  • Sergiy - Wednesday, March 1, 2017 4:43 AM

    Oh, really?How much did they pay you, say last month, for the software which you developed 5 years ago and which is working since then with no issues?Ah, you probably never came across such software.In hour experience.:-)

    I am paid to deliver quality software. They wouldn't have me here, where I currently am, if I didn't.

    I am just saying that my experience is different. It happens.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Ironically, the very techniques talked about in this article apparently haven't been exercised for the recent forum update and one of the most important parts of this site, the SQL Code windows, still doesn't work correctly.  They still double-space and delete leading spaces if you copy and paste from SSMS.  They still come up with all sorts of wonky colorization if you make a trip through NotePad (for example) to preserve the spaced indentation.  What happened to test and UAT?

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden - Wednesday, March 1, 2017 8:36 AM

    Ironically, the very techniques talked about in this article apparently haven't been exercised for the recent forum update and one of the most important parts of this site, the SQL Code windows, still doesn't work correctly.  They still double-space and delete leading spaces if you copy and paste from SSMS.  They still come up with all sorts of wonky colorization if you make a trip through NotePad (for example) to preserve the spaced indentation.  What happened to test and UAT?

    [/quote]

    That's not remotely true. Things were tested and users worked with them. That didn't guarentee there were fixes, and for a number of items, there aren't good fixes with rewriting lots of code. Which means we're either in the business of full time forum development or we must redo all that work with every software upgrade.

    We are working with the vendor to try and incorporate some fixes into their codebase to handle some issues, but some don't have good solutions that we can easily implement.

  • I think Jeff's point is very valid. Figuring out who your users are is critical for testing.

    412-977-3526 call/text

  • Man, Steve, you covered a lot with this article. I want to address just one thing you mentioned; that's getting people, especially users, to test changes. In my experience that has led to very little results. For example, in my previous job we never got anyone to test our changes. In my current job the organization is much larger, so there are a few who are willing to give some new feature or app a try. But really, not much participation. Its like pulling teeth. I honestly think it would be easier if we offered some user cold, hard cash to test something new.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • Steve Jones - SSC Editor - Wednesday, March 1, 2017 9:01 AM

    Jeff Moden - Wednesday, March 1, 2017 8:36 AM

    Ironically, the very techniques talked about in this article apparently haven't been exercised for the recent forum update and one of the most important parts of this site, the SQL Code windows, still doesn't work correctly.  They still double-space and delete leading spaces if you copy and paste from SSMS.  They still come up with all sorts of wonky colorization if you make a trip through NotePad (for example) to preserve the spaced indentation.  What happened to test and UAT?

    That's not remotely true. Things were tested and users worked with them. That didn't guarentee there were fixes, and for a number of items, there aren't good fixes with rewriting lots of code. Which means we're either in the business of full time forum development or we must redo all that work with every software upgrade.

    We are working with the vendor to try and incorporate some fixes into their codebase to handle some issues, but some don't have good solutions that we can easily implement.

    [/quote]
    Better than before but a few niggles. As a user I generally feel positive about the forum upgrades. As an IT professional I understand the difficulties of the situation. To be honest, if it was bad in my opinion then I would have found the appropriate forum and said something. I haven't. Extensive customisation through code, as opposed to configuration, is a long term headache.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Steve Jones - SSC Editor - Wednesday, March 1, 2017 9:01 AM

    Jeff Moden - Wednesday, March 1, 2017 8:36 AM

    Ironically, the very techniques talked about in this article apparently haven't been exercised for the recent forum update and one of the most important parts of this site, the SQL Code windows, still doesn't work correctly.  They still double-space and delete leading spaces if you copy and paste from SSMS.  They still come up with all sorts of wonky colorization if you make a trip through NotePad (for example) to preserve the spaced indentation.  What happened to test and UAT?

    That's not remotely true. Things were tested and users worked with them. That didn't guarentee there were fixes, and for a number of items, there aren't good fixes with rewriting lots of code. Which means we're either in the business of full time forum development or we must redo all that work with every software upgrade.

    We are working with the vendor to try and incorporate some fixes into their codebase to handle some issues, but some don't have good solutions that we can easily implement.

    [/quote]
    Glad to hear you're working with the vendor but, what I said is true or not in your opinion, the results still speak for themselves, Steve.  It's difficult for me to understand why probably the most popular SQL Server forum in the world, which is owned by a company that makes some of the most popular software in the world, allowed for such a thing to happen.  I'm not going to bail or anything like that because of it but it does make your good article extremely ironic.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 15 posts - 1 through 15 (of 36 total)

You must be logged in to reply to this topic. Login to reply