NVP Software Solutions

Category: Software Testing

  • 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.

  • Resources

    Resources

    Resources are always a problem in projects. You may have too many at one point, too few at another point and the skills may be mismatched even if the number matches to what you estimated. Issue The client was expanding rapidly in a new industry. Two large organizations in a related industry had already started divisions to address this market but we were dealing with a new and much younger company.

    Please take a look at Case Study 9: https://nvp.ca/wp-content/uploads/2021/06/Case-Study-9-Resources.pdf to see how the process was managed.

  • Designing Testing

    Designing Testing

    Frequently organizations grow concerned about their Quality Assurance Processes. They are not sure if they are using the best processes for their testing. Everything has been internally built with little input from outside the organization. Over time the isolation may lead to inefficient processes. There may not be an awareness of what has changed and how it might impact their work habits.

    Please take a look at Case Study 7: https://nvp.ca/wp-content/uploads/2021/06/Case-Study-7-Consulting.pdf to see how the process was redesigned.

  • Test Leadership

    The role of a Test Lead varies widely between organisations and even within some large organisations. Some test leads execute a plan, other build and manage and some run multiple projects with other test leads running particular aspects.  If you are in this position, you may be wondering what to do. 

    Please take a look at Case Study 2: https://nvp.ca/wp-content/uploads/2019/06/Case-Study-2.pdf for how training was organised in one particular example.

  • Requirements

    Requirements

    While iterative methodologies do not expect full requirements at the beginning of a project, it may still be critical to eventually capture the entire set of requirements. Traceability between testing and requirements has become popular recently to provide auditability.

    Please see https://nvp.ca/wp-content/uploads/2021/06/Case-Study-8-Requirements.pdf for an example Case Study.

  • Test Tool Selection

    Test Tool Selection

    Test Automation is critical to any ongoing test efforts. Without automation., there is no way that testing can keep up and it is almost impossible to complete regression testing or any sort of Performance Testing. Tracking current status is also difficult. With AI coming into the mix in both the product and the test tool, the need is greater than ever to understand what is available and how it works.

    Please take a look at the Case Study 5: https://nvp.ca/wp-content/uploads/2019/07/Case-Study-5.pdf for more information

  • Bridging the Gap

    Bridging the Gap

    Bridging the Gap between vendors and the final client can be difficult for a System Integrator. It is one thing to actually make the decision, purchase the software, integrate the software and deliver it. It is very much another situation when you come to the various levels of testing and need to coordinate multiple vendors, one System Integrator, and a client with multiple departments with differing needs.

    Please take a look at the Case Study 1 : https://nvp.ca/wp-content/uploads/2019/06/Case-Study-1.pdf for one occurrence.

  • TASSQ May 2025 Webinar

    Toronto Association of Systems and Software Quality (TASSQ) is pleased to announce our Webinar for May 2025.

    Topic: Back to Basics

    Presenter: Huib Schoots

    Location: Online, Zoom

    When: Tuesday May 27 at 6:15 p.m. (EDT)

    Cost: $14.00 CAD

    Register at https://tassq.org/events

    Presentation Abstract:

    Back to Basics

    Organizations are often concerned that testing is not sufficiently focused on finding the problems that really matter. Testers often don’t know how to determine when they’ve tested enough. Testers are naturally inclined to test too much. So we test too much and probably regularly test the wrong things… The solution is simple: back to basics!

    Presenter Bio:

    My personal mission is to improve software quality by shaping better people by connecting, innovating, facilitating, coaching, enabling, and teaching. I’m fascinated by mindset, thinking, behaviour, communication, and collaboration. I’m active in many communities. Some keywords about me: humanist, servant leader, open, direct, creative, idea generator, result-driven, humorous, problem solver, curious, confronting, critical thinker, passionate and energetic, lifelong learner, entrepreneurial, analytic, and continuous (world) improver. I like hanging out with friends, singing in a rock band, playing trombone in a brass band, board & computer games, LEGO, photography, running, beer brewing, magic tricks, travelling, and reading. I work as a quality & test consultant, trainer & coach.

    Plenty of reasons to Attend TASSQ Webinars:

    As a professional involved in QA you will:
    Get prompt information on topics and thought leadership affecting the QA community