Category: Software Testing

  • 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

  • Quantifying Intangibles – 3

    Quantifying Intangibles – 3

    Last week we gave a partial list of intangibles: Better Quality; Strategic decisions; Opportunity and Innovation; Flexibility and Information and Decisions. We recommended setting a base level cost so they had some value. It should not start out too high but as you gain information over the projects, it should be possible to refine the benefit and get a more accurate benefit figure.

  • Are your Product Issues Worrying You?

    Are your Product Issues Worrying You?

    Possibly your customers will not like the User eXperience.

    They may use your product in unexpected ways and break it.

    OR

    They may love it and ask for further functionality.

    Any one of the above scenarios can cause problems for a product. Some may arise within hours of release and others may appear over time. Regardless,you need to be prepared.

    • Align your Product Assurance with your clients.
    • Incorporate Product Assurance and Testing to catch issues early while they are cheap to fix
    • Lay the groundwork for future success.

    NVP Software Solutions

    • NVP Software Solutions provides industry-leading software product assurance and testing services, customized to address client’s business requirements. 

    Schedule a no-charge one hour consultation with a senior Product Assurance consultant for an initial assessment/problem solving session.

    Contact us: Nvp.ca

  • TASSQ March 2025 Talk

    TASSQ March 2025 Talk

    Toronto Association of System and Software Quality -TASSQ is pleased to announce our Webinar for March 2025.

    Topic: Back to Basics

    Presenter: Huib Schoots

    Location: Online/Zoom

    When: Tuesday March 25 at 6:15 p.m. until 7:30 p.m. EST

    Cost: $14.00 CAD

    Register at: TASSQ

    Presentation Abstract:

    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!

  • Are your Quality Assurance Issues Worrying You?

    Are your Quality Assurance Issues Worrying You?

    Schedule a no-charge one hour consultation with a senior Quality Assurance consultant for an initial assessment/problem solving session.

    • Align your Quality Assurance Practices with your client’s needs before they ask.
    • Incorporate Quality Assurance and Testing to catch issues early while they are cheap to fix
    • Lay the groundwork for future success.

    NVP Software Solutions

    • NVP Software Solutions provides industry-leading software quality assurance and testing services, customized to address client’s business requirements. 

    Contact us: Nvp.ca

  • Get a Consistent Reporting Format

    Get a Consistent Reporting Format

    Reporting results is one of the bigger aspects of testing that is often overlooked in the beginning of a project.  The initial efforts are aimed at getting the testing environment established and the test cases written and approved.  Then the launch into testing occupies a lot of time ironing out the minor irritants to test execution.  At that point the request for reports comes up and the test lead is frequently left scrambling for data to report what is requested.  Failure to anticipate the reporting requirements can lead to a lot of manual work.

    Lessons Learned:  A few hours defining results reporting formats can save hours later in the project.

  • Too Many Disparate Pieces of Software (What Happens When One Fails or Goes Out of Business)

    Too Many Disparate Pieces of Software (What Happens When One Fails or Goes Out of Business)

    An assessment of an existing and successful system showed a lot of disparate pieces of software hooked together in various ways.  An inability to properly define and build effective QA environments for testing meant that some testing was not done and taken on faith that it worked or was tested in production (and fixed).  No API testing was completed so any failure of any piece of the solution had immediate repercussions throughout the product and had to be fixed on the fly.

    Lessons Learned:  A proper environment and knowledge and testing of the APIs would have solved a lot of the issues that showed in production.