Hooray, I found the bug

Detalhes bibliográficos
Autor(a) principal: João Filipe Vieira Nadais
Data de Publicação: 2016
Tipo de documento: Dissertação
Idioma: eng
Título da fonte: Repositórios Científicos de Acesso Aberto de Portugal (RCAAP)
Texto Completo: https://hdl.handle.net/10216/85732
Resumo: Debugging has been a process that is causing various headaches to a large of programmers along time.Sometimes, the error is found at a very late stage of development, leading to added high costs for its correction. Other times, a function is not contemplating all the cases it should, specially some that are not easily perceptible, which lead to an indication by debugging tools that the fault is on related parts, since this function is seen as executed successfully. Some tools like Crowbar give us, from a set of tests, the possibility of having a more visual perception of the project that is being analyzed, as well as the probability of finding the error in certain parts of the code. Having its base on algorithms that strive for efficiency, such as Spectrum-based fault localization, and being integrated in the IDE, the user has the possibility of having a new approach to the fault localization problem. However, so far it is still not possible to state the real impact that having this kind of tool in the general user experience. Therefore, a user study was done to compare not only the fact of having or not a performance improvement by the users on locating faults, but also the importance of having this tool integrated in the IDE, the ease of use of the tool and finally obstacles that the user had due to the need of using a specific IDE. For those who will test the opposite case (the usual process with no tool), we aim to evaluate the approach used by the developer to find the error as well as the difficulty on finding it. By comparing these two experiences, with a relevant number of cases in each, it will be possible to conclude wether or not tools like Crowbar make users better.
id RCAP_d6fb4e988a697651a62d2362e7418a4f
oai_identifier_str oai:repositorio-aberto.up.pt:10216/85732
network_acronym_str RCAP
network_name_str Repositórios Científicos de Acesso Aberto de Portugal (RCAAP)
repository_id_str https://opendoar.ac.uk/repository/7160
spelling Hooray, I found the bugEngenharia electrotécnica, electrónica e informáticaElectrical engineering, Electronic engineering, Information engineeringDebugging has been a process that is causing various headaches to a large of programmers along time.Sometimes, the error is found at a very late stage of development, leading to added high costs for its correction. Other times, a function is not contemplating all the cases it should, specially some that are not easily perceptible, which lead to an indication by debugging tools that the fault is on related parts, since this function is seen as executed successfully. Some tools like Crowbar give us, from a set of tests, the possibility of having a more visual perception of the project that is being analyzed, as well as the probability of finding the error in certain parts of the code. Having its base on algorithms that strive for efficiency, such as Spectrum-based fault localization, and being integrated in the IDE, the user has the possibility of having a new approach to the fault localization problem. However, so far it is still not possible to state the real impact that having this kind of tool in the general user experience. Therefore, a user study was done to compare not only the fact of having or not a performance improvement by the users on locating faults, but also the importance of having this tool integrated in the IDE, the ease of use of the tool and finally obstacles that the user had due to the need of using a specific IDE. For those who will test the opposite case (the usual process with no tool), we aim to evaluate the approach used by the developer to find the error as well as the difficulty on finding it. By comparing these two experiences, with a relevant number of cases in each, it will be possible to conclude wether or not tools like Crowbar make users better.2016-07-082016-07-08T00:00:00Zinfo:eu-repo/semantics/publishedVersioninfo:eu-repo/semantics/masterThesisapplication/pdfhttps://hdl.handle.net/10216/85732TID:201307332engJoão Filipe Vieira Nadaisinfo:eu-repo/semantics/openAccessreponame:Repositórios Científicos de Acesso Aberto de Portugal (RCAAP)instname:FCCN, serviços digitais da FCT – Fundação para a Ciência e a Tecnologiainstacron:RCAAP2025-02-27T19:57:32Zoai:repositorio-aberto.up.pt:10216/85732Portal AgregadorONGhttps://www.rcaap.pt/oai/openaireinfo@rcaap.ptopendoar:https://opendoar.ac.uk/repository/71602025-05-28T23:40:47.065838Repositórios Científicos de Acesso Aberto de Portugal (RCAAP) - FCCN, serviços digitais da FCT – Fundação para a Ciência e a Tecnologiafalse
dc.title.none.fl_str_mv Hooray, I found the bug
title Hooray, I found the bug
spellingShingle Hooray, I found the bug
João Filipe Vieira Nadais
Engenharia electrotécnica, electrónica e informática
Electrical engineering, Electronic engineering, Information engineering
title_short Hooray, I found the bug
title_full Hooray, I found the bug
title_fullStr Hooray, I found the bug
title_full_unstemmed Hooray, I found the bug
title_sort Hooray, I found the bug
author João Filipe Vieira Nadais
author_facet João Filipe Vieira Nadais
author_role author
dc.contributor.author.fl_str_mv João Filipe Vieira Nadais
dc.subject.por.fl_str_mv Engenharia electrotécnica, electrónica e informática
Electrical engineering, Electronic engineering, Information engineering
topic Engenharia electrotécnica, electrónica e informática
Electrical engineering, Electronic engineering, Information engineering
description Debugging has been a process that is causing various headaches to a large of programmers along time.Sometimes, the error is found at a very late stage of development, leading to added high costs for its correction. Other times, a function is not contemplating all the cases it should, specially some that are not easily perceptible, which lead to an indication by debugging tools that the fault is on related parts, since this function is seen as executed successfully. Some tools like Crowbar give us, from a set of tests, the possibility of having a more visual perception of the project that is being analyzed, as well as the probability of finding the error in certain parts of the code. Having its base on algorithms that strive for efficiency, such as Spectrum-based fault localization, and being integrated in the IDE, the user has the possibility of having a new approach to the fault localization problem. However, so far it is still not possible to state the real impact that having this kind of tool in the general user experience. Therefore, a user study was done to compare not only the fact of having or not a performance improvement by the users on locating faults, but also the importance of having this tool integrated in the IDE, the ease of use of the tool and finally obstacles that the user had due to the need of using a specific IDE. For those who will test the opposite case (the usual process with no tool), we aim to evaluate the approach used by the developer to find the error as well as the difficulty on finding it. By comparing these two experiences, with a relevant number of cases in each, it will be possible to conclude wether or not tools like Crowbar make users better.
publishDate 2016
dc.date.none.fl_str_mv 2016-07-08
2016-07-08T00:00:00Z
dc.type.status.fl_str_mv info:eu-repo/semantics/publishedVersion
dc.type.driver.fl_str_mv info:eu-repo/semantics/masterThesis
format masterThesis
status_str publishedVersion
dc.identifier.uri.fl_str_mv https://hdl.handle.net/10216/85732
TID:201307332
url https://hdl.handle.net/10216/85732
identifier_str_mv TID:201307332
dc.language.iso.fl_str_mv eng
language eng
dc.rights.driver.fl_str_mv info:eu-repo/semantics/openAccess
eu_rights_str_mv openAccess
dc.format.none.fl_str_mv application/pdf
dc.source.none.fl_str_mv reponame:Repositórios Científicos de Acesso Aberto de Portugal (RCAAP)
instname:FCCN, serviços digitais da FCT – Fundação para a Ciência e a Tecnologia
instacron:RCAAP
instname_str FCCN, serviços digitais da FCT – Fundação para a Ciência e a Tecnologia
instacron_str RCAAP
institution RCAAP
reponame_str Repositórios Científicos de Acesso Aberto de Portugal (RCAAP)
collection Repositórios Científicos de Acesso Aberto de Portugal (RCAAP)
repository.name.fl_str_mv Repositórios Científicos de Acesso Aberto de Portugal (RCAAP) - FCCN, serviços digitais da FCT – Fundação para a Ciência e a Tecnologia
repository.mail.fl_str_mv info@rcaap.pt
_version_ 1833600250838777856