Abstract
Non-Functional Characteristics and NFT Testing of Container Applications
Highlights
Application development has been transitioning to container-based architecture from Virtual Machines
Functional testing of any application refers to the feature set of the application that it intends to provide to the end user of the application
Taking similar example of the railway reservation application, the nonfunctional behavior is bound to change based on the surrounding eco-system it is built upon
Summary
Application development has been transitioning to container-based architecture from Virtual Machines. Irrespective of the platform, environment or other external variables, these feature sets or the functional part of the application remains constant To illustrate it with an example, a railway reservation application’s primary functionality of booking tickets remains constant irrespective of whether the application is mobile, cloud or traditional. This stands true for all applications and the intended functionality is always rigorously tested and it is a continuous process where even after the application is in production we see number of new releases which could include patches to fix existing bugs application supporting new functionality. Taking similar example of the railway reservation application, the nonfunctional behavior is bound to change based on the surrounding eco-system it is built upon
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
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
