Where Can Testers Get Information?

TestFortExpert by TestFortExpert on 03/1/2013

Where Can Testers Get Information?

Where Can Testers Get Information?Testers often have to look for different sources of information that can replace or complete a specification. There are different sources at different stages. Let’s take a closer look.

So which sources can be used before changes in the code are made?

  1. Specification. Testing can be carried out using a specification, a text file with a description of what needs to be tested and results, which the program should reach.
  2. Project Manager. As a rule, a project manager sets up tasks for developers. It is highly desirable to duplicate the task for a tester. This will save tester’s time.
  3. Similar applications. One can use the products of the leading software developers as standards. For example, you can target the MS Office for Windows-based applications.
  4. Domain knowledge and understanding of the ongoing use-cases.
    Understanding and selection of the main and secondary functional. Understanding what features will be the most important for the customer, you can set testing priorities right.
    The expected behavior of the application. Knowing, for what range of users an application is created, one can offer the most suitable organization of the interface or on the contrary, identify disadvantages in using the application.

Which sources can be used after changes are coded?

  1. Developer. Sometimes developers have difficulties with the implementation of a function. If he shares this information with a tester, a tester will be able to focus on the “problem” function and test it more thoroughly.
  2. The application itself. When there is a lack of any documentation and nobody wants to share information one has no choice but to investigate the application.
  3. Release notes. Release notes mean comments on each version being tested.

Release notes help to determine the order of testing. It is logical foremost to test those parts of the program that have been changed in the latest version.
Release notes also help to support the documentation of testing up to date. Knowing which parts of the program have been changed, you can update the test cases in accordance with the changes immediately after a new release.

We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy