Software testing using context maps test cases

In software industry the greatest amount of expenditure is in maintaining software developed poorly or specifications not met properly, this result in failures, budget overruns and unmet timelines. Software testing, if carried out properly, could actually resolve or mitigate these issues. However, i...

Full description

Bibliographic Details
Main Author: Khan, Farooq Ali
Format: Others
Published: 2007
Online Access:http://spectrum.library.concordia.ca/975715/1/MR40942.pdf
Khan, Farooq Ali <http://spectrum.library.concordia.ca/view/creators/Khan=3AFarooq_Ali=3A=3A.html> (2007) Software testing using context maps test cases. Masters thesis, Concordia University.
id ndltd-LACETR-oai-collectionscanada.gc.ca-QMG.975715
record_format oai_dc
spelling ndltd-LACETR-oai-collectionscanada.gc.ca-QMG.9757152013-10-22T03:47:25Z Software testing using context maps test cases Khan, Farooq Ali In software industry the greatest amount of expenditure is in maintaining software developed poorly or specifications not met properly, this result in failures, budget overruns and unmet timelines. Software testing, if carried out properly, could actually resolve or mitigate these issues. However, in many cases the testing methodologies as well as the testing tools consider testing as a post development effort, which is conducted in isolation of the analysis and worse still, development itself. The efficacy of the testing as a guard against software and project failure is therefore not always realized, partly because of the absence of a tool based support for test cases, a tool which could be simple and yet effective. We propose that contexts should be considered for testing and as such testing should not be considered as an isolated activity, but an umbrella or integrated activity, intrinsically linked and uses the output from different phases of software development lifecycle. For instance, the fact that context for testing is present in the test case would only make the testing easy and will help in creating a role for non testing teams including the users to participate in the success of the tests and a better product. We use Context Maps to create Context Maps Test Cases (CMTC), for User Acceptance Testing in small customization projects to test defect fixes and enhancements in already developed software. CMTC helped in contriving the test case artifacts like test data, expected and actual output not just by testing team on the basis of documents, but also provide a role or channel for the end users as well as other stakeholders to share their thoughts, as to what constitute the best data to test the product with 2007 Thesis NonPeerReviewed application/pdf http://spectrum.library.concordia.ca/975715/1/MR40942.pdf Khan, Farooq Ali <http://spectrum.library.concordia.ca/view/creators/Khan=3AFarooq_Ali=3A=3A.html> (2007) Software testing using context maps test cases. Masters thesis, Concordia University. http://spectrum.library.concordia.ca/975715/
collection NDLTD
format Others
sources NDLTD
description In software industry the greatest amount of expenditure is in maintaining software developed poorly or specifications not met properly, this result in failures, budget overruns and unmet timelines. Software testing, if carried out properly, could actually resolve or mitigate these issues. However, in many cases the testing methodologies as well as the testing tools consider testing as a post development effort, which is conducted in isolation of the analysis and worse still, development itself. The efficacy of the testing as a guard against software and project failure is therefore not always realized, partly because of the absence of a tool based support for test cases, a tool which could be simple and yet effective. We propose that contexts should be considered for testing and as such testing should not be considered as an isolated activity, but an umbrella or integrated activity, intrinsically linked and uses the output from different phases of software development lifecycle. For instance, the fact that context for testing is present in the test case would only make the testing easy and will help in creating a role for non testing teams including the users to participate in the success of the tests and a better product. We use Context Maps to create Context Maps Test Cases (CMTC), for User Acceptance Testing in small customization projects to test defect fixes and enhancements in already developed software. CMTC helped in contriving the test case artifacts like test data, expected and actual output not just by testing team on the basis of documents, but also provide a role or channel for the end users as well as other stakeholders to share their thoughts, as to what constitute the best data to test the product with
author Khan, Farooq Ali
spellingShingle Khan, Farooq Ali
Software testing using context maps test cases
author_facet Khan, Farooq Ali
author_sort Khan, Farooq Ali
title Software testing using context maps test cases
title_short Software testing using context maps test cases
title_full Software testing using context maps test cases
title_fullStr Software testing using context maps test cases
title_full_unstemmed Software testing using context maps test cases
title_sort software testing using context maps test cases
publishDate 2007
url http://spectrum.library.concordia.ca/975715/1/MR40942.pdf
Khan, Farooq Ali <http://spectrum.library.concordia.ca/view/creators/Khan=3AFarooq_Ali=3A=3A.html> (2007) Software testing using context maps test cases. Masters thesis, Concordia University.
work_keys_str_mv AT khanfarooqali softwaretestingusingcontextmapstestcases
_version_ 1716607978263543808