Abstract
Günümüz dünyasında hızla büyümekte olan
teknoloji sistemleri hayatımıza hızlıca yerleşmiş ve yaşamımızın her alanında
yerini almıştır. Teknoloji firmaları ürünlerinin pazarlanması ve piyasa
içerisinde kalabilmeleri için büyük bir rekabetin içerisinde bulunmaktadırlar.
Özellikle yazılım şirketlerinin piyasa içerisinde var olabilmek ve sunduğu
hizmetlerle müşterilerinin memnuniyetini kazanabilmek için ürün ve hizmetlerinin
iyi bir test sürecinden geçirmeleri önem taşımaktadır. Bir yazılım projesinin
kalitesi müşteriye sunulmadan önce en erken test aşamasında görülebilmektedir.
Test sürecinde projenin ne kalitede olduğu, projenin istenilen gereksinimleri
karşılayıp karşılamadığı ve bulunan hataların durumlarıyla ilgili bilgiler test
durum raporlamalarıyla görüntülenebilmektedir. Bu çalışmada yazılım test süreci
boyunca yapılacak sürekli raporlamalar ve raporlamaların önemine değinilmekte,
raporlamalara dair önerilerde bulunulmaktadır.
References
- Ammann, P., ve Offutt, J. (2016). Introduction to software testing. Cambridge University Press.
- Black, R. (2002). Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing. USA: Wiley Publishing, Inc.
- Bourque, P. ve Fairley, R.E. (2014). Guide to the Software Engineering Body of Knowledge (SWEBOK (R)): Version 3.0. IEEE Computer Society Press.
- Calleam Consulting Ltd. (2008). “Case Study – Denver International Airport Baggage Handling System – An illustration of ineffectual decision making”. https://www5.in.tum.de/persons/huckle/DIABaggage.pdf, (30.04.2018).
- Graham, D., Van Veenendaal, E. ve Evans, I. (2008). Foundations of software testing: ISTQB certification. Cengage Learning EMEA.
- Johnson, P. (2012). Mariner 1's $135 Million Software Bug. https://www.itwo-rld.com/article/2717299/mariner-1-s--135-million-software-bug.html, (06.05.2018)
- Jones, C. (2008). Applied Software Measurement: Global Analysis of Productivity and Quality. McGraw-Hill Education Group.
- Lazic, L. ve Mastorakis, N. (2008). Cost effective software test metrics. WSEAS Transactions on Computers, 7(6): 599-619.
- Lewis, W. E. (2017). Software testing and continuous quality improvement. Auerbach publications.
- Naik, K. ve Tripathy, P. (2008). Software Testing and Quality Assurance: Theory and Practice. USA: John Wiley & Sons, Inc.
- Patton, R. (2006). Software Testing. India: Pearson Education.
- Rational Software Corporation (2001). Test Evaluation Summary for the Architectural Prototype. https://sceweb.uhcl.edu/helm/RUP_course_example/courseregistrationproject/artifacts/test/results/test_report_arch.htm, (29.04.2019).
- Software Testing Fundementals (bt.). Defect Severity. http://softwaretestingfundamentals.com/defect-severity/, (18.05.2018).
Abstract
Rapidly growing technology systems in today's
world have quickly settled in our lives and have taken its place in every
aspect of our lives. Technology companies are in a big competition to market
their products and stay strong in the market. It is especially important for
software companies to have a good testing process in order to secure their
place in the market and gain the satisfaction of their customers with the
services they provide. The quality of a software project is provided first in
the testing stage. The quality of the project, whether meet the requirements or
not, the information about bugs found during testing process could be viewed in
the test reports. In this study continuous reporting during testing process are
discussed and also recommendations about reporting are made.
References
- Ammann, P., ve Offutt, J. (2016). Introduction to software testing. Cambridge University Press.
- Black, R. (2002). Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing. USA: Wiley Publishing, Inc.
- Bourque, P. ve Fairley, R.E. (2014). Guide to the Software Engineering Body of Knowledge (SWEBOK (R)): Version 3.0. IEEE Computer Society Press.
- Calleam Consulting Ltd. (2008). “Case Study – Denver International Airport Baggage Handling System – An illustration of ineffectual decision making”. https://www5.in.tum.de/persons/huckle/DIABaggage.pdf, (30.04.2018).
- Graham, D., Van Veenendaal, E. ve Evans, I. (2008). Foundations of software testing: ISTQB certification. Cengage Learning EMEA.
- Johnson, P. (2012). Mariner 1's $135 Million Software Bug. https://www.itwo-rld.com/article/2717299/mariner-1-s--135-million-software-bug.html, (06.05.2018)
- Jones, C. (2008). Applied Software Measurement: Global Analysis of Productivity and Quality. McGraw-Hill Education Group.
- Lazic, L. ve Mastorakis, N. (2008). Cost effective software test metrics. WSEAS Transactions on Computers, 7(6): 599-619.
- Lewis, W. E. (2017). Software testing and continuous quality improvement. Auerbach publications.
- Naik, K. ve Tripathy, P. (2008). Software Testing and Quality Assurance: Theory and Practice. USA: John Wiley & Sons, Inc.
- Patton, R. (2006). Software Testing. India: Pearson Education.
- Rational Software Corporation (2001). Test Evaluation Summary for the Architectural Prototype. https://sceweb.uhcl.edu/helm/RUP_course_example/courseregistrationproject/artifacts/test/results/test_report_arch.htm, (29.04.2019).
- Software Testing Fundementals (bt.). Defect Severity. http://softwaretestingfundamentals.com/defect-severity/, (18.05.2018).
Details
| Primary Language | Turkish |
|---|---|
| Journal Section | Articles |
| Authors | |
| Publication Date | December 6, 2019 |
| Published in Issue | Year 2019 Volume: 5 Issue: 1 |