NVP Software Solutions

Tag: software testing

  • Quality Assurance

    Quality Assurance

    During the past year, we gathered up some articles and LinkedIn posts indicating a desire to improve Quality Assurance. Most people seemed to feel that this needed to be a country lead initiative or at least a consortium of several large companies along with educational institutions. While that might be a laudable aim, it is unlikely to occur.


    Most governments have other things to do and a lack of understanding about quality. Large companies have other priorities and Quality Assurance is just one of many items that need to be addressed.

    This initiative will need to be lead by individuals who have a vested interest in Quality Assurance and a willingness to involve other parties in IT (almost everyone) who would benefit.

    We will be launching this in October.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    @Neil Price-Jones

    https://www.linkedin.com/newsletters/7399187902221443072

    Home
  • Quality Assurance – Testing

    Quality Assurance – Testing

    We are continuing our series on quality assurance. We have deliberately left out the coding piece of this because that is the piece that is changing the most frequently and processes that we had in the past have been superseded considerably by the advent of AI and the ability to grab code from certain repositories.

    We’re still looking at the testing, however, from the point of view of process improvement, because not only is testing lagging somewhat behind in terms of. AI implementation but the insecurity around code developed by AI is leading to an increased emphasis on testing.

    So the processes revolving around testing are even more crucial than they were before. Ensuring that we are:

    1. testing what we should be
    2. not over testing
    3. having the confidence at the end to state that the release can go forward.

    This is definitely critical when you consider our two other posts which came out last month and two more this month about having confidence in your release delivery and ensuring that it can go ahead.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072

    Home
  • End of Month -August 2026

    End of Month -August 2026

    Are we now immune to the surprise caused by failures in computer systems?

    At one time, there was always a reaction to computer failures (including data breaches).  People expressed shock, or at least indignation, especially if the outage was widespread and had bad effects.  Other people were happy if the problem impacted their competitors and not them. 

    Only yesterday the online and mobile apps for my bank were down for several hours.  The system recovered; no explanation was offered.

    Over time, most people had their own share of failures (which put an end to the snide remarks).  But it also seemed that it stopped being news.  Too commonplace and too frequent. 

    Are we missing opportunities to rectify this situation?  The answer is yes and later in the year, we will be running a series of posts on some methods of avoiding these errors

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072

  • Does your Software Testing Pay – Part 3

    Does your Software Testing Pay – Part 3

    “Does your Software Testing Pay” is the question we posted. We then posted a simple calculation for a ROI.
    After we posted the second blog we had a couple of comments to the effect that concentrating on defects was a very narrow focus in terms of cost recovery and benefits. This was certainly a valid criticism; we had concentrated on something that could be answered and calculated without too much effort.

    Some of the suggestions that came back were as follows:

    1. Contributing to a better product using the information gleaned from testing
    2. Enhanced knowledge of the product for both testers and developers.
    3. Future design improvements.
    4. A better quality product.

    No doubt more items could be added to the above list

    Now we just need to cost them

    Since some of these are subjective benefits, it is suggested that they be documented and then all stakeholders can assign them to a value bucket (independently). As a starting point we can use an averaged value for each benefit and then convert that into a dollar value to determine the benefit.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072

  • The AI Testing Landscape: Where Testers Create Value in the AI Era

    The AI Testing Landscape: Where Testers Create Value in the AI Era

    Artificial Intelligence is everywhere in software testing right now.

    Testers are experimenting with tools, generating test cases, writing automation scripts, and even reviewing code with AI. On the surface, it feels like a massive leap forward.

    The session introduces a practical framework for understanding the different domains of AI testing and the evolving role of software testers

    Register for this Free Webinar.

    Biography

    Swati Seela is a Principal SQA Engineer, author, and speaker with 20+ years of experience in software testing, automation, and quality engineering. She has built scalable test frameworks, authored 100+ widely read articles, and trained testers globally. Her work focuses on practical, high-impact testing and real-world applications of AI in quality engineering.

    Register for this Free Webinar.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072
  • Testing for System Integrators – Part 2

    Testing for System Integrators – Part 2

    Two days ago we asked two $10,000 dollar questions and this week we promised the possible answers. Unlike the questions, which are specific to the final client and the suppliers, the answers are more general and apply to both.

    1. The contracts state the following specifically about Quality Assurance and everyone is in agreement
    2. The contracts says nothing about it so far but we have Quality Assurance as a topic and the contract will not be finalised without this discussion
    3. The contracts says nothing about Quality Assurance so far but now that you have brought it up we will add it.
    4. There is something in the contracts about Quality Assurance and we can look it up for you (contracts are signed).
    5. There is nothing in the contracts (contracts are signed) and there is no intention of putting anything in the contracts about Quality Assurance
    6. We don’t know (but that is a good question)
    7. We don’t know (and we don’t care)

    Suffice to say the items in the above list have an obvious gradation from good to terrible in the order they are presented. If you get the first answer, you’re well on your way. If you get some of the middle answers you have some work to do, but you may be in time to effect some change. If you get the last few answers, you are in trouble!

    Next: What to do with the answers.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072
  • Quality Management

    Quality Management

    Is there any difference between software and manufacturing?

    We recently participated in a preparation session for an upcoming webinar. The person we will be presenting with is involved Quality Management for Products while I was representing Software.

    It was quite surprising how similar we sounded in terms of what we do:

    1. Product Planning Phase turning into Requirements.
    2. Design Phase
    3. Testing Phase
    4. Production Phase
    5. End-of-Life
    • We both wanted measurements and opportunity to institute process improvement.
    • We both looked at the entire lifecycle.
    • We both looked at training as a method of attaining Quality objectives.
    • We both end up with a product.
    • We both wanted to add process improvement at all stages.

    There does not seem to be a lot of difference. But, then again, we took our Quality Assurance from Crosby, Deming and Juran.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072
  • The purpose of Meetings

    The purpose of Meetings

    Recently I was asked to provide a short history of a local Quality Assurance organization.

    Starting with the previous organization, I went through the 25-year history in about 5 minutes. The one major overriding change in those 25 years was the advent of the internet that created a vast information trove that is free to all. Prior to that, people were isolated within their organizations with limited contact with people with the same interests in other organizations. Solutions to problems were generally home-grown.

    Having provided that very brief synopsis we were left with three questions about the purpose of the organization:

    1. Are we an organization dedicated to networking?
    2. Are we an education organization?
    3. Are we a social organization?

    Unfortunately we do not have enough of the history documented to determine what has been the best use of the time. Clearly my synopsis was based on what I remembered and I was not always in attendance at all the meetings or always on the board. So the question is still open.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP