Skip to main content

Software Testing Life Cycle? Bleurgh!

I was recently updating my LinkedIn (Add me here if you like) and I was looking through the skills, something that I find as a bit of a pointless feature, well, the endorsing of skills is a bit pointless, as I have people who I've never worked with endorsing me for skills that they really don't know I have, it's nice that they feel they can endorse me but it happens so often, that it kind of makes endorsements pointless? Anyway, I digress...

There was a skill in there for the Software Testing Lifecycle, and I thought about it, and what it meant. It's saying that you can have a skill in just the software testing lifecycle, but in my opinion, we should be moving away from this, we shouldn't be focusing on just the testing phases, we as QA should be involved from the offset, and hence, we shouldn't just be having a Software Testing Lifecycle as a skill, we should be aiming for having the Software Development Lifecycle, as we are all (Devs and QAs) involved in the development and testing of a software product.

Maybe I'm being too cynical, but I really think that little things like this, don't help in a quest/vision to be seen as one.

Comments

  1. It's all bollocks really, I see it on job ads all the time "familiar with SDLC", totally meaningless so I dont think aiming for that is useful. What exactly does it mean??
    Yes I am skilled in the SLDC. Which one? the one in a textbook? the one at Acme Inc? The one at Google? The one at MS?

    ReplyDelete
    Replies
    1. It's more about being aware of the different types of development lifecycles, and the pros and cons of each I guess. I really disliked the Testing Lifecycle as I disagree that testing is a seperate process in the dev lifecycle. I see your point tho, there's such a variety of different SDLC that it in itself shouldn't really be part of a job desc or a skill as such.

      Delete
  2. I agree with this comment completely. You need to understand both concepts and not restrict youself to one..... if a tester understands the development life cyle then they will know when is best to engage the software test life cyle.

    ReplyDelete
  3. Software Development life cycle is the process which is followed to develop a software product. It is a structured way of building software applications. Most organizations have a process in place for developing software; this process may, at times, be customized based on the organizations requirement and framework followed by organization.

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)

What we (Asos Testers) are working towards this year...

At Asos we have a large testing team (30+ testers), they all work within their development teams, and the way development teams work can vary and understandably so. Helping the 30+ testers we have a number of Test Leads, of which I am one, recently we (the leads) all got together to come up with a plan of things that we feel we need to work on/define/have an idea of how to approach them for the next year to help improve our testing standards across the boards and improve the skillset of testers within the teams. To help with this we got together and came up with a mindmap, the plan going forward is for us to take ownership of one of the areas and come up with a strategy/approach/implement actions to help improve the areas and define whatever is needed. There's a lot there, and I'll probably write seperately about each one, and what we're doing, as it's always good to share ideas and get feedback... so watch this space!