Can I get my software developers to test their own code?

Can I get my software developers to test their own code?

Diagnostic people are the true genius team members on a software development team. The Product knowledge, technical understanding, insight and observation skills are critical to be able to spot and explain why software is not working as it should.

In my experience, developers do not test their code. Let me be a bit more harsh, in my experience, most developers do not even run the code before checking it in. It seems that they are in the BEST position to make sure the code is working as intended, but getting them to test - even a little bit - seems impossible.

Much of my hair loss can be attributed to the stress of having to worry that defects that so obvious make it into customers hands.

I recently was having a problem with a developer on the team and I asked him to make me a 3 minute video of testing the feature he has been working on for the last month. 5 seconds into this test, the first show stopper issue showed up ... with many of its friends following close behind. This made it clear to me that he was not testing at all.

All developers who work for us produce a daily status report. This report includes

  • list of what was done today
  • what is planned to be done for tomorrow
  • a video (if ui was affected)
  • a link to check-in

The reason for this it make them consider how they are progressing and give us the ability to spot people who are working on stuff that we don't want or doing it in the wrong way.

I am adding a requirement to this list. I am adding a 3 min test video to it. 3 mins is a reasonably long time to work over a feature or a set of the product. Along with this video a list of issues or undone features need to be submitted. It should take the developers about 15 mins of their day to do this. I get to watch how they test, what they test, what things they miss, etc.

I think this is going to work. We already have discipline or reporting every day, so its just another piece of that. Maybe will post a follow up in a few months to tell you all if experiment worked or not.

To view or add a comment, sign in

More articles by Carl Hewitt

  • Fractional CTO Service Coming...

    I wanted to give a preview for what is next for me :) I have taken a few years to recover from the trauma of being a…

    3 Comments
  • Building software without designing it!

    NO! NO! NO! But yet, most people do this. This is especially true with no and low code tools because they seem so fast…

  • ChatGPT: Part 1, limitations

    Having worked in software for 20+ years, I see very few things that strike me as being 'new' and 'different'. Most…

    1 Comment
  • How do you judge how capable a 'no code' tool is?

    I have spent my entire career building a variety of low and eventually no code platforms. As there are many 'no code'…

  • AppGlue: What does 'embeddable' mean?

    I wanted to explain a bit about what it means to have an embeddable rule/workflow engine. I came to the realization…

    1 Comment
  • AppGlue: Everything that is needed - and nothing more

    One of the things that happen over a long cycle of product and business evolution, is that you add things to the…

  • AppGlue: Designing a deployment strategy

    One of the things that separate prior generation systems from ones built using the new paradigm is how the software is…

  • AppGlue: New Technology Stack

    There is a constant parade of different software frameworks and approaches. I have been designing and building software…

  • AppGlue: Creative Destruction

    Improvements in products - actually improvements in the way a task is accomplished using a product - is a process of…

    4 Comments
  • AppGlue: Songwriter... not a pop star

    I have had a number of people contact me that seemed (mildly!) disappointed that not trying to make AppGlue the 'next…

    1 Comment

Others also viewed

Explore content categories