NVP Software Solutions

Tag: software testing

  • Getting Value From Quality Management

    Getting Value From Quality Management

    Two weeks ago we provided A How to on Quality Management?  This week we want to look how you get Value from Quality Management.

    We often hear people questioning the value of Quality Management, and rarely hear the same question on the value of Software Testing. Testing has a tangible and more immediate outcome. Quality Management, on the other hand, doesn’t always show its value and activity immediately even though it provides longer term and larger rewards. The key to getting value from Quality Management and Quality Assurance activities is that all findings must be acted upon. If they aren’t, value isn’t achieved and efforts will be wasted. (more…)

  • Stress Testing

    Stress Testing

    Think of stress testing in software testing as the confirmation that any sudden increase in transactions per unit time can be accommodated by the program being tested and won’t cause the program to stop working or degrade its operation in any manner. i.e. a short sharp peak. (more…)

  • Upcoming Software Testing & Quality Assurance Events – October 2016

    NVP Software Solutions will be participating in the following two software testing and quality assurance events happening this October in Ontario, Canada. The events are located in Toronto, Kitchener-Waterloo and London in the coming two weeks. Check out the relevant websites for more information and to register. This is a great opportunity to connect with other software testing and quality assurance professionals. We hope to see you there! (more…)

  • Volume Testing

    Volume Testing

    Volume testing confirms that any values that may become large over time (such as accumulated counts, logs, and data files) can be accommodated by the program and won’t cause the program to stop working or degrade its operation in any manner.
    Risk if not completed – It may not be possible to operate the complete system with all data in place if the volume of expected records is not checked during testing and verified to work correctly and completely. (more…)

  • Negative Testing

    Negative Testing

    In many software testing scenarios, testers can use positive testing and/ or negative testing methods. Positive testing means that the item being tested reacts as expected when the expected input is entered. Negative testing typically means that the system can handle invalid input or unexpected user behaviour. However, if the system responds by rejecting the data and providing an error message, that is what was actually expected, meaning that was positive testing rather than negative testing. (more…)

  • System Boundary Diagram

    System Boundary Diagrams sometimes come up in the context of a Use Case and sometimes in the context of Software Testing. Either way they are a useful in the effort expended when determining what to test. While the ‘normal’ System Boundary Diagram shows the boundaries of the system and thus the boundaries of the testing, we try to use it only as a starting point for other diagrams that may also aid in defining the testing effort and scope. (more…)

  • How Do We Train Software Testers?

    Software tester training is something that appears to require a lot more attention, given the number of conversations we have on a regular basis. We get a surprising number of questions about software tester training and plans, so we’ve dedicated our next blog series on how to train software testers. (more…)

  • Testing Sources of Information

    Sources of information for testing tend to come from two extremes. In some cases you may have almost no information and find it difficult to start. In other cases you may have far too much information and not know what to do with it all or where to start or stop reading. The ‘happy medium’ or ‘just right’ amount is rarely the case when it comes to testing sources of information. (more…)