All

What are you looking for?

All
Projects
Results
Organizations

Quick search

  • Projects supported by TA ČR
  • Excellent projects
  • Projects with the highest public support
  • Current projects

Smart search

  • That is how I find a specific +word
  • That is how I leave the -word out of the results
  • “That is how I can find the whole phrase”

Model–Based Testing and Exploratory Testing: Is Synergy Possible?

The result's identifiers

  • Result code in IS VaVaI

    <a href="https://www.isvavai.cz/riv?ss=detail&h=RIV%2F68407700%3A21230%2F16%3A00301251" target="_blank" >RIV/68407700:21230/16:00301251 - isvavai.cz</a>

  • Result on the web

    <a href="http://ieeexplore.ieee.org/document/7740354/" target="_blank" >http://ieeexplore.ieee.org/document/7740354/</a>

  • DOI - Digital Object Identifier

    <a href="http://dx.doi.org/10.1109/ICITCS.2016.7740354" target="_blank" >10.1109/ICITCS.2016.7740354</a>

Alternative languages

  • Result language

    angličtina

  • Original language name

    Model–Based Testing and Exploratory Testing: Is Synergy Possible?

  • Original language description

    Model–based testing represents an efficient method to detect software defects. This approach has a limitation, when the model of the system under test is inconsistent, incomplete, or, does not exist at all. An exploratory testing approach represents an alternative for such situations: initially it does not require a model of the tested system. The testers are using their skills and intuition to explore the system. Nevertheless, this technique has also its disadvantages. For example, it is hard to measure the effectiveness of the testing or to re–evaluate certain test when the explored path and exercised test cases are not being documented properly. In this paper, we are proposing a technique that utilizes advantages of the both model–based testing and exploratory testing and tries to eliminate their issues. The model of the application is dynamically created and updated in the exploratory stage when state data (the page user is currently on, all input, action and link elements) and every step that was taken is recorded. This structure documents what parts of the tested system were explored and what parts has to be explored later on. Recorded steps are also converted to test case scenario that can be reused later in the testing process.

  • Czech name

  • Czech description

Classification

  • Type

    D - Article in proceedings

  • CEP classification

    JC - Computer hardware and software

  • OECD FORD branch

Result continuities

  • Project

  • Continuities

    S - Specificky vyzkum na vysokych skolach

Others

  • Publication year

    2016

  • Confidentiality

    S - Úplné a pravdivé údaje o projektu nepodléhají ochraně podle zvláštních právních předpisů

Data specific for result type

  • Article name in the collection

    Proceedings of the 6th International Conference on IT Convergence and Security (ICITCS 2016)

  • ISBN

    978-1-5090-3765-0

  • ISSN

    2473-0122

  • e-ISSN

  • Number of pages

    6

  • Pages from-to

    329-334

  • Publisher name

    Curran Associates, Inc.

  • Place of publication

    Red Hook

  • Event location

    Prague

  • Event date

    Sep 26, 2016

  • Type of event by nationality

    WRD - Celosvětová akce

  • UT code for WoS article

    000388730200071