NVP Software Solutions

Month: December 2019

  • Quality Assurance 2020

    We received an interesting article last week from a friend about Technology Trends.

    The 10 Best Tech Products of the 2010s were listed. It was surprising how old some of them were. Some technology has been around a lot longer than was remembered!

    Of course, the 10 best had to be followed up with the worst failures. Only 5 of those, but they still resonate for the amount of money sunk into them and the scale of the failure in some cases.

    The next section was a prediction of the Five technologies for the next decade. A decade seems like a long time for some of these. We expect them to be mainstream within a year or two in some cases. Some are used already.

    They are:

    • Artificial Intelligence (AI)
    • Blockchain
    • Augmented Reality and Virtual Reality (AR/VR)
    • Big Data
    • Internet of Things (IoT)

    So what is the impact on Software Testing? Some of these will be a huge challenge for those who are used to dealing with static inputs and static results. Most of these technologies will not work on that principle. The Test Environment will have to change also. We have already had test environments change in the last few years to accomodate many external feeds and applications. Now the test environment will have to expand further in order to accomodate inputs we don’t use now and also the volumes of data needed for the testing.

    So what is the impact on Quality Assurance (Process Improvement)? There may be an even bigger impact on how we work. In the past, we could retrieve some mistakes by adding items late in the process. That will no longer be possible with some of the technologies. Failure to consider all items at the beginning of a project could have much larger costs later on. We cannot afford that type of omission in 2020 and beyond.

    Photo by Alex Kotliarskyi on Unsplash

  • Quality Assurance 2019 Review

    Quality Assurance is, as usual, up and down. Some organisations are buying in to Process Improvement, looking long term, and many are realizing that the solutions are not necessarily more testing or another test tool. They understand that the problems lie in how things are done rather than the tools used.

    However, many organizations are still adding test tools or adding test phases and layers without adding value to the Software or the Product.

    We completed several assessments over the past year and provided seminars aimed at process improvement. We are now up to the stage of implementing the process improvements identified. These organizations are moving ahead and planning for the long term. They can see the value of improvement.

    However, on the other hand, some of the people we are dealing with are struggling to complete the necessary testing without considering the long term improvement. They are challenged by the necessity of getting testing done for clients and do not think they have the time for process improvement.

    So will this change in the 2020? It seems unlikely in view of the above unless we consider the following:

    1. Calculate the real benefit of implementation of process improvement over multiple projects. This is the long term, high level, view of how process improvement benefits multiple projects.
    2. Define and gather the appropriate measurements and metrics to determine whether the process improvement is having the desired effect and also to identify further process improvement opportunities.
    3. Select and acquire the appropriate technology to support the process improvement effort. Talk to us about a well tested methodology for QA technology acquisition.

    Photo by Bekir Dönmez on Unsplash

  • Automated Testing

    Judging from what we have heard, AI seems to be the favourite flavour for Automated Testing in 2019. Many of the tools are stating that they are AI enabled or AI enhanced and claiming massive productivity gains as a result.

    We are still seeing tools that require a lot of technical knowledge and other ones that have hidden the actual scripting from the users.

    One other major change is that most tools are now automatically offering either a cloud based or an on-premise solution to suit every client’s wishes and, more importantly, their security needs.

    Tools go through a cycle every few years. For a while we get a different test tool for every possible situation, then someone comes and consolidates a large number of tools into one tool that addresses most situations. Then the cycle starts again. Obviously this cycle is driven by the technology used to build applications and what level of testing is needed.

    In addition to the technology that is used to build any particular product, the methodology also impacts the way automation is applied. Any iterative methodology has vastly different needs from a standard Waterfall methodology.

    What we are not seeing, is much initial analysis to select the best test tool for an organisation. We are still seeing selection based on features and not necessarily on functionality that is applicable throughout the organisation. We are seeing some ROI for individual automation efforts but that is after the tool is selected and implemented. However, as discussed last week, that calculation is not over the entire organisation or over an extended time period. This means we are losing out on some automation opportunities and completing some based on a false calculation.

    So will this change in the 2020? It seems unlikely in view of the above unless we consider the following:

    1. Calculate the real benefit of implementation of automation over multiple projects and years.
    2. Find an automation tool that suits your situation. There are many good ones around; you just need to find the appropriate one. Talk to us about a well tested methodology for test tool acquisition.

    Photo by Franck V. on Unsplash

  • Manual Testing

    This year is the n’th time we have heard about the demise of Manual testing and the n+1’st time it has not occurred.To paraphrase Mark Twain “Rumours of the death of Manual Testing have been greatly exaggerated”.

    Why does this keep coming up year after year:

    1. We keep inventing new items that are not amenable to being automated.
    2. New startups have neither the time or the budget to worry about automating testing. Their emphasis is on getting the product out the door and into the hands of their customers.
    3. Some organisations have a great deal invested in an old automated tool. They are not maintaining the existing scripts or adding new but no one is willing to throw them out.
    4. Some testing tools have not lived up to their promises and people are unwilling to try again with a new test tool.
    5. Most project managers do not have budget for automation of testing and since they do not benefit from it (the next project benefits) they see little reason to add it to their project.
    6. If it becomes a corporate or central responsibility to automate, then the question of funding it becomes awkward. Who is responsible for the cost fo the tool and the automation effort? How is that cost amortized and apportioned?
    7. It appears cheaper to get Manual Testers.

    So will this change in the 2020? It seems unlikely in view of the above unless we consider the following:

    1. Calculate the real cost of repeatedly executing the same testcases manually.
    2. Calculate the real benefit of implementation of automation over multiple projects and years.
    3. See whether the automation will pay for itself using the above two figures.
    4. Find an automation tool that suits your situation. There are many good ones around; you just need to find the appropriate one. Talk to us about a well tested methodology for test tool acquisition.

    Photo by Hunter Haley on Unsplash