Abstract
Objectives: To propose a generic framework that would help in defining a process and an eco-system which could be used to thoroughly test the non-functional behavior of any container-based applications. Methods: A comprehensive study was conducted to investigate the available frameworks for testing non-functional characteristics. This was followed up by quantitative analysis to know containers, non-functional aspects, generic framework, and its usage requirement. The step-by-step method was used to design the framework, where first the sub-parts were designed and implemented. It was followed up by defining the integration points of all the sub-parts. Finally, a fully matured, functional, and integrated framework came into effect. Findings: There are no frameworks available to focus on the non-functional aspect of container-based applications. The proposed framework can be utilized by various entities, viz developers, testers, integrators, and system or application certification authorities. It can be used to determine the nature and behavior of containerized applications under the known and unknown factors of non-functional characteristics, which transcends the mere realm of application behavior but primarily delves into the surrounding actors for the proper functioning of the application. Novelty: A unique testing framework for container applications focusing on non-functional characteristics. Keywords: Framework, Capacity, Scalability, High Availability, NonFunctional Testing
Highlights
Applications that are built using a container-based framework are agnostic to the underlying hardware and the Operating system
We have identified four Non-functional characteristics of container-based applications that are of prime importance
A Non-Functional Requirement (NFR) Modelling framework has been proposed by Paradkar[8], which elaborates on key non-functional characteristics in businesscritical systems
Summary
Applications that are built using a container-based framework are agnostic to the underlying hardware and the Operating system. Non-Functional testing is an integral part of any software or application It reflects the application behavior based on the surrounding environment. We have identified four Non-functional characteristics of container-based applications that are of prime importance. The by-product of capacity testing is that the numeric result or the traffic carrying capacity of an instance of the application is further used to design and define the scalability criteria of the application to be tested. This is general, is quite helpful in dimensioning the application vis-a-vis the projected traffic of the application in production
Sign-in/Register to view highlights & summary 
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call