NVP Software Solutions

Blog

  • TASSQ Webinar for October 2025

    TASSQ Webinar for October 2025

    Topic: Enough is Enough – When is enough visual test coverage?

    Presenter: Derek Choy

    Location: Online, Zoom

    When: Tuesday, October 21at at 6:15 p.m. (until 7:30 p.m.) EST

    Cost: $10.00 CAD

    Register at: https://tassq.org/events

    Abstract:

    Enough is Enough – When is enough visual test coverage?

    The session will focus on how QA teams can accurately assess whether their applications have sufficient visual test coverage using modern tools and best practices. The presentation will introduce the concept of visual coverage, which goes beyond code coverage to reveal untested, under-tested, and high-risk areas of your user interfaces. We will explore technologies like visual heatmaps and intuitive gap analysis to instantly identify missing or redundant tests, helping teams streamline their QA processes and maintain consistent quality.

    Presenter Bio:

    Derek Choy is a seasoned technology executive with extensive experience in quality assurance (QA) and engineering leadership within fast-growing SaaS and enterprise software organizations. As CTO and previously COOr at Rainforest QA, Derek has been instrumental in driving product and technical innovation for one of the leading platforms in on-demand QA, scaling globally distributed engineering and product teams, and helping companies achieve robust, automated software testing processes. Derek holds degrees from Imperial College London and Stanford University and has served as a strategic advisor in cloud testing and machine learning QA initiatives. He is widely recognized for advancing scalable QA strategies.

    Register at: https://tassq.org/events

  • QA – Why Bother?

    QA – Why Bother?

    If you get the feeling that this is a question you encounter a lot, you are not alone. We get a lot of calls and emails asking us to explain this question. Of course, the answer is dependent on who is asking the question.

    People want to know why they should consider it and, more importantly, the benefit. Sometimes they are simply looking for something to carry back to the project or department.

    In order to answer the question, we need to appeal to the broader costs calculated over multiple projects.

    We define QA as Process Improvement and processes generally apply to multiple projects (or at least can be applied to multiple projects). Hence the need for long term measurements and metrics.

    The simplest example is Defect Management. A simple process to ensure all defects are addressed and handled only once by each member of the team would remove a lot of redundancy.

    Other examples include Testcase creation; Testing; Summary reporting; Development; and Requirements management.  With the advent of AI, this has become much more critical to get right. The chances of going off track at high speed have increased substantially.

  • Are you satisfied with your testing?

    Are you satisfied with your testing?

    Most people we speak to answer that question with a resounding NO; they are not satisfied with their testing. The answer may vary from stakeholder to stakeholder, and the intensity and source of the dissatisfaction may be different.  However, doing something about it is a different matter.    The most recent of many examples involved someone who complained about the testing and was promptly put in charge.  Not the result they were aiming for at the time!

    Solving the dissatisfaction is very difficult. Process improvement is resisted on many levels and there is usually a large number of potential improvements that may impact the perception.  The starting point is with a stakeholder survey and process assessment; this gives the basis for supportable incremental changes to improve satisfaction. 

    Take a look at Assessments for a starting point on what to include.

  • TASSQ 2025 – 2026 Schedule

    TASSQ 2025 – 2026 Schedule

    TASSQ is pleased to announce their September 2025 through February 2026 schedule.

  • Isn’t there a better way to Test?

    Isn’t there a better way to Test?

    This is a question that gets asked very frequently especially at the end of projects that have not gone well.

    While there are many people who will advocate one methodology or another for testing and tell you their way is the only way, every method must adapt to the project at hand, the risks and the desired outcomes.  There is no one way to test but there are ways to improve the testing.

    The first need is time at the end of the project to evaluate what went right and wrong before people forget.

    Some common concerns:

    1. Too much documentation:  It is acceptable to reduce documentation if the same testers will be available for the next project but not so effective if the next project will be staffed with new people unfamiliar with the project.
    2. Too little documentation:  This can be solved but it takes time or can be fed through AI to generate the complete documentation.  Always review anything produced by AI.
    3. Too much repetition:  This is a process error that can be solved by RCA and then implemented but is not likely to have much effect for at least a project or two.
    4. Unused testcases:  This is a classification issue that can be solved with AI at this point.
    5. Too many escaped defects:  Again RCA with the aid of AI can address this but it is too late to implement the solution for the existing project.
  • Is your testing Ad hoc?

    Is your testing Ad hoc?

    While most people won’t come out and say that their testing is Ad Hoc, it can usually be inferred from some of the following comments:

    1. We keep redoing things.

    2. We seem to lose everything with every iteration.

    3. We keep re-inventing the wheel.

    4. We have thousands of testcases and most of them have not been looked at in years.

    5. We miss things in every release even though we saw them in the past.

    6. We keep solving the same problems in development.

    And on the list goes.

    If you feel you are stuck in this rut, it is time to break out

    .

    But that requires a fresh look at the following items:

    * Current assets

    * Current processes

    * Missing pieces

    * Left over items and problems. Breaking out of Ad Hoc testing is very difficult. Process improvement is resisted on many levels.

  • What do Test Managers do in a project?

    What do Test Managers do in a project?

    There would be an obvious answer to that question if one replaced the word Test with the word Project. So, if we transfer in reverse the answer is the same. Since we had to answer this question …

    Please take a look at Case Study 11: https://nvp.ca/wp-content/uploads/2025/05/Case Study 12.pdf  for an answer to this question.

  • Mentoring

    Mentoring

    Frequently organizations encounter a roadblock on their Quality Assurance Processes. Most tasks are progressing well but there is a hitch or a stumble somewhere. The problem is not large enough to warrant a full consulting contract but it needs to be resolved. This is where Mentoring helps.

    Issue: A client, who creates websites for government departments and high profile clients, was having trouble with their Quality Assurance process.

    Please take a look at Case Study 11: https://nvp.ca/wp-content/uploads/2021/10/Case-Study-11-Mentoring.pdf to see how this was solved quickly and cheaply.