| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Halttunen, Veikko", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Timperi, Petri", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2015-08-17T19:48:40Z", "language": "", "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2015-08-17T19:48:40Z", "language": "", "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2015", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/46634", "language": "", "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Tutkielmassa k\u00e4sitell\u00e4\u00e4n ohjelmistojen toiminnallisen testauksen automaatiossa k\u00e4ytett\u00e4v\u00e4\u00e4 kehyst\u00e4 joka toteuttaa testiautomaation arkkitehtuurin ja sen peruspalvelut. Kehyksist\u00e4 tarkastellaan niiden toiminnallisuuksia, arkkitehtuuriratkaisuja ja suunnitteluperiaatteita sek\u00e4 listataan vaatimukset, joita kehyksen tulisi toteuttaa. Ty\u00f6ss\u00e4 perustellaan miksi testiautomaatio on t\u00e4rke\u00e4\u00e4 ketter\u00e4ss\u00e4 kehityksess\u00e4 ja listataan merkitt\u00e4vimm\u00e4t ongelmat, joita testiautomaation k\u00e4ytt\u00f6\u00f6notossa tyypillisesti kohdataan. Testiautomaatiokehyksen rooli ongelmien ratkaisemiseksi k\u00e4yd\u00e4\u00e4n l\u00e4pi ja perustellaan, miksi sen kehitykseen ja k\u00e4ytt\u00f6\u00f6nottoon kannattaa panostaa.\r\nTutkielma on tehty kirjallisuus- ja artikkelikatsauksena. Siin\u00e4 on pyritty l\u00f6yt\u00e4m\u00e4\u00e4n eri l\u00e4hteist\u00e4 ratkaisuja testiautomaation ongelmiin testiautomaa-tiokehyksen n\u00e4k\u00f6kulmasta sek\u00e4 l\u00f6yt\u00e4m\u00e4\u00e4n vaadittavat toiminnallisuudet ja vaatimukset jotka kehyksen tulee toteuttaa. \r\nTutkielmassa tarkastellaan toiminnallisten testien testiautomaatio-ratkaisuja, niiden suunnitteluperiaatteita ja arkkitehtuuri-ratkaisuja. Suunnitteluperiaatteista k\u00e4yd\u00e4\u00e4n l\u00e4pi modulaarisuus, kirjastojen k\u00e4ytt\u00f6, avainsana- ja datapohjaisuus, sek\u00e4 n\u00e4iden yhdistelm\u00e4 hybridi testiautomaatiokehys. Tapaustutkimusten pohjalta havaitaan ett\u00e4 t\u00e4m\u00e4n p\u00e4iv\u00e4n kehykset ovat tyypillisesti hybridi-kehyksi\u00e4 ja niiss\u00e4 erotellaan kehyksen ja testausv\u00e4lineen osuudet eri tasoille arkkitehtuurissa. Kehys toteuttaa tyypillisesti testien hallinnan, testidatan k\u00e4sittelyn, tulosten raportoinnin sek\u00e4 testiymp\u00e4rist\u00f6n alustuksen. Testausv\u00e4lineen rooli on toteuttaa testiskriptit, jotka ajetaan kehyksen toimesta testattavaa j\u00e4rjestelm\u00e4\u00e4 vasten.\r\nTutkielmaan on koottu testiautomaatiokehysten yleisi\u00e4 vaatimuksia joita voidaan hy\u00f6dynt\u00e4\u00e4 sovellusaluekohtaisten vaatimusten m\u00e4\u00e4rittelyss\u00e4. Arkki-tehtuurivaatimusten lis\u00e4ksi, kehyksen t\u00e4rkeimm\u00e4t vaatimukset olivat laaja r\u00e4\u00e4t\u00e4l\u00f6it\u00e4vyys, testausv\u00e4lineriippumattomuus, tuki hajautetuille testeille sek\u00e4 kattava testien hallinta niin raportoinnin kuin testien valinnan ja muokkauksen suhteen.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "The study goes through the functionalities, design principles and architecture solutions of test automation frameworks. It explains the principles behind frameworks and collects their generic requirements. The importance of test automation is elaborated especially in Agile environments. The typical adoption issues of test automation are covered and the solutions that test automation framework design can offer to solve those issues. The study is based on literature review where these issues are addressed.\r\nThe study walks through the solutions of test automation frameworks for functional testing. What are their design principles and architectural solutions. The modularity, library usage, keyword- and data-driven design principles are discussed as well as the combination of these, the hybrid design. Based on various case studies, the most common framework type today is hybrid. It implements the design principles mentioned and separates the testing tool and framework parts in the architecture. The framework\u2019s role is to implement test management, test data handling, results reporting and test configuration features. Testing tool\u2019s responsibility is to implement the actual test scripts executed against the system under test.\r\nThe generic requirements of test automation frameworks were collected in the study. In addition to architecture requirements, the most important re-quirements were full configurability, testing tool independency, support for distributed tests and extensive test management functionalities, including test selection, editing and reporting. Based on this study, application area specific requirements can be processed.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted using Plone Publishing form by Petri Timperi (pejutimp) on 2015-08-17 19:48:40.015297. Form: Kandidaatintutkielma -lomake (https://kirjasto.jyu.fi/julkaisut/julkaisulomakkeet/kandin-tutkielma-lomake). JyX data: [jyx_publishing-allowed (fi) =True]", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by jyx lomake-julkaisija (jyx-julkaisija.group@korppi.jyu.fi) on 2015-08-17T19:48:40Z\r\nNo. of bitstreams: 2\r\nURN:NBN:fi:jyu-201508172688.pdf: 741519 bytes, checksum: db17091343e25a539f989879ee1a4dc5 (MD5)\r\nlicense.html: 4810 bytes, checksum: f0b36b2debbc7c7bd1d854c5a650d63c (MD5)", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2015-08-17T19:48:40Z (GMT). No. of bitstreams: 2\r\nURN:NBN:fi:jyu-201508172688.pdf: 741519 bytes, checksum: db17091343e25a539f989879ee1a4dc5 (MD5)\r\nlicense.html: 4810 bytes, checksum: f0b36b2debbc7c7bd1d854c5a650d63c (MD5)\r\n Previous issue date: 2015", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "39", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.language.iso", "value": "fin", "language": "", "element": "language", "qualifier": "iso", "schema": "dc"}, {"key": "dc.rights", "value": "In Copyright", "language": "en", "element": "rights", "qualifier": null, "schema": "dc"}, {"key": "dc.subject.other", "value": "testiautomaatiokehys", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "testiautomaatio", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "toiminnallinen testaus", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "avain-sanapohjainen testaus", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Vaatimukset testiautomaatiokehitykselle toiminnallisessa testauksessa", "language": "", "element": "title", "qualifier": null, "schema": "dc"}, {"key": "dc.type", "value": "bachelor thesis", "language": null, "element": "type", "qualifier": null, "schema": "dc"}, {"key": "dc.identifier.urn", "value": "URN:NBN:fi:jyu-201508172688", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.dcmitype", "value": "Text", "language": "en", "element": "type", "qualifier": "dcmitype", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Kandidaatintutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Bachelor's thesis", "language": "en", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Informaatioteknologian tiedekunta", "language": "fi", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Faculty of Information Technology", "language": "en", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Informaatioteknologia", "language": "fi", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Information Technology", "language": "en", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "University of Jyv\u00e4skyl\u00e4", "language": "en", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "Jyv\u00e4skyl\u00e4n yliopisto", "language": "fi", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Tietoj\u00e4rjestelm\u00e4tiede", "language": "fi", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Information Systems Science", "language": "en", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.date.updated", "value": "2015-08-17T19:48:41Z", "language": "", "element": "date", "qualifier": "updated", "schema": "dc"}, {"key": "dc.type.coar", "value": "http://purl.org/coar/resource_type/c_7a1f", "language": null, "element": "type", "qualifier": "coar", "schema": "dc"}, {"key": "dc.rights.accesslevel", "value": "openAccess", "language": "fi", "element": "rights", "qualifier": "accesslevel", "schema": "dc"}, {"key": "dc.type.publication", "value": "bachelorThesis", "language": null, "element": "type", "qualifier": "publication", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}]
|