Experience-Based Test Techniques



20140708_0132Do you have experienced testers in your team? Why don’t you take advantage of their skills and intuition? Experienced-Based techniques can be a good choice if your project documentation is not detailed enough, your testing time is limited and you've a testing team that is experienced in that type of systems.

Experience-based techniques are not well structured approaches. Therefore, those techniques are not suitable when detailed test documentation is required and will not guarantee a high-level of repeatability.


Error guessing

The tester uses his experience to guess what areas are potentially affected. Then he selects and applies the best methods to uncover defects in those areas. This technique is especially useful during the integration and system testing, when testing a software's new release. It gives the best results when used by testers with a strong expertise in similar systems. Checklists and defect taxonomies  (categorized lists of defect types) can facilitate the error guessing testing process and assure some test documentation level.


Checklist-Based Testing

The tester verifies the product against a set of criteria and rules that's stored in a high-level checklist. Those checklists are built based on experience, standards and guidelines. This technique is most effective when used by testers familiar with the area covered by the checklist, they don't necessarily have to know the specific type of software (e.g. a tester familiar with user interface testing). Checklist testing may give different results as those are high-level and can be interpreted differently by several testers.


Exploratory Testing

The tester learns about the product, designs and executes tests and reports the results simultaneously. Good exploratory sessions are planned, the area to be covered is designated and the time frame is set. Capture/playback tools can be used to ensure the session reproducibility. This will help with recalling the steps to reproduce failure and may deliver some more system configuration information (depending on the selected tool capabilities).

Technology Technology

Op 12/09/2014 door Lukasz

How to do a Web Performance Test in Visual Studio


According to the ISTQB glossary of testing terms: Performance testing - The process of testing to determine the performance of a software product.
It is performed to determine how a system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.


Visual Studio capabilities

Only the Visual Studio Ultimate version offers ‘Perform web performance and load testing’ capabilities.

The performance testing process in Visual Studio basically works like below:

  • Record a web performance test by browsing a website as if you were the end user
  • Requests are recorded and added automatically to the test in Visual Studio Ultimate
  • Finish recording
  • Customize the test by editing its properties
  • Run test


Simple example

First of all you have to create a Web Performance and Load Test Project. You can find it under Test project templates.


The next step is to add the Web performance Test to the created project.


This step can automatically trigger the Web Test Recorder in your Internet Explorer browser.
NOTE: If something went wrong – check if the Web Test Recorder is enabled in your Internet Explorer add-ons. Try to trigger it manually from the View->Explorer Bars menu in the browser.


Now you can browse through your web application. While doing that – all the requests will be recorded. At the end - choose Stop on the test recorder.


Open request details to edit some request properties that are commonly modified in tests, including Reporting Name, Think Time and Response Time Goal. (You can also customize other request properties in the properties window.)

Technology Technology

Op 19/05/2014 door Lukasz