The Risk profiles of a project or programme of work constantly change over the system development life-cycle. We all know that occasionally a swerve ball is thrown and we must react and adapt accordingly. Usually the project informs testing of the change and in return testing informs the project of the associated risk and details the probability of the risk involved. Testing then needs to be flexible and responsive to these changes to adapt, and to find a suitable solution to offer the best probability of success without compromising quality.
Software Development and Testing can use lots of different methodologies and models, but for this paper we will stick to those that are most commonly used and current in today's market place. Overall the common goal of all testing methodologies is to ensure a bug free product that meets the Users requirements.
STLC - Software Testing Life Cycle, simply put, refers to a testing process regardless of which testing methodology you use (Agile, Scrum or Waterfall etc.), each process will have specific steps to be executed in a predefined sequence, thus ensuring that both the entry and exit criteria have been met through each stage of a project.
In the STLC process, every activity and testing task is carried out in a planned way, regardless of whether you are in a short sprint or a large waterfall project. Each project phase will naturally have different goals and deliverables but the principals of each objectives remains the same – delivering software that is bug-free and meets the Users requirements.
Within each project, there will be a level of detail that naturally alters dependant on the testing methodology, but the key features of the STLC will remain the same whether written into a formal document or scribbled on a post-it note. Here are the key (and not limited too) features of the STLC:
- Everyone in the DevOps team is stressed, or worse still burnt out.
- Releases mainly happen out of core hours and often on weekends and Bank Holiday.
- Your team relies on a single ‘Go To’ person, the only one who knows how to get the code deployed.
- Users are often negatively affected by new releases – bugs in live.
- You might not be superstitious, but your project manager brings into work a lucky black cat, a rabbit’s foot and hangs a horse shoe above the server room door for every software release…!
By the time you have read to the end of this article you can be very assured that someone somewhere has either launched a new app, created a new phone, put their services into the Cloud or Internet enabled a ‘Thing’. This gives us a problem; an advancement of digital tech is forcing every company to rethink their testing strategies, leave it too late to change and you risk being left behind in the market place and that’s not a place you want to be, nor does the board and shareholders…
Customers and End Users alike want high quality applications that seamlessly integrate first time. Testing was once a project supporter, now it’s the driving force of key strategies and the way in which projects are delivered. Ask yourself the following three questions, and if you have one moment of doubt then you need to rethink the way you address this digital disruption:
Topics: Software Testing
Adoption of new working practices and methodologies has meant that organisations are constantly challenging themselves to get products and services to market faster than ever and in doing so are now having to think very hard how this can be achieved. We all know that first to market get the spoils, so there is a lot at stake getting the delivery model right. Test Automation is just one way of speeding up your project delivery and in doing so building up a regression pack of test scripts that can be run with little effort in little time.
Firstly, a Test Plan, in simple terms, is a testing project plan for all the testing works that need to be achieved during any of the test phases; the test plan will not address test design, nor detail the low-level details of say a Test Case or Test Script. It is however vital that you have a good test plan template so that you always start right and have the required sections in the template to allow you to:
- Be thorough
- Use the latest version of the document thus giving you the best opportunity to cover of all the details required for that Testing Phase.
My 70-year young Father entered the digital world for the first time last year; he had managed to successfully swerve the internet and associated technology for most of his life, but the closure of his local bank meant he had to become a Silver Surfer and transact online. Now here’s the funny thing, having missed 20 years of painfully developed, lack lustre devices and poor internet speeds, he’s straight into augmented reality, surfing the virtual world like a 13-year-old pimply teenager. Voice browsing was his latest trick, however I did notice he ended each voice search command with a – please and thank you…
Over the past twelve months the IoT has been one of the world's most searched and researched topics. This article will give an insight in to what it might mean for you and your company. We all know, and most of us will probably have, a smart phone that is continuously connected to the Internet. In the background every movement, payment and internet search is being monitored and data being assessed (somewhere) to help improve your life and the way that you work and play. It is said some organisations know from your work's security pass when you take a comfort, coffee or cigarette break based purely on your location in the building, also the duration you take. If they were clever then there would be a cup of tea waiting for me in the reception area next time I visit… milk, no sugar please...!
For many of you reading this article, you will be sitting down with your peers working out the 2017 budget, considering the change of IT landscape, new applications being developed and of course upgrades to existing functionality. Doing so by employing ROM (Rough Order of Magnitude) and WAG (Wild Arse Guess) techniques to come up with a suitable budget to deliver IT to your organisation.