Copyright © 2025 Authors retain the copyright of this article. This article is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

@article{147338,
        author = {Shivani Dave and Hitesh Patel and Ashvin Prajapati},
        title = {NON-FUNCTIONAL TESTING IN AGILE DEVELOPMENT},
        journal = {International Journal of Innovative Research in Technology},
        year = {},
        volume = {5},
        number = {7},
        pages = {159-162},
        issn = {2349-6002},
        url = {https://ijirt.org/article?manuscript=147338},
        abstract = {Non-functional requirements define the overall qualities or attributes of a system. Although important, they are often neglected for many reasons, such as pressure of time and budget. In agile software development, there is a focus on the feature implementation and delivery of value to the customer and, as such, non-functional aspects of a system should also be of attention. Non-functional requirements testing is challenging due its cross-functional aspects and lack of clarity of their needs by business in the most part of projects. The goal of this paper is to empirically investigate how do agile team members handle non-functional testing in their projects, aiming to identify preliminary factors influencing the testing of non-functional requirements, specifically performance and security in agile development. Also, work with the high-quality perception is crucial in accordance the participants.},
        keywords = {},
        month = {},
        }