ColdBox HMVC Documentation
Master ClassVideo TrainingCommunityVegas Training
Search…
6.x
Introduction
Intro
Release History
About This Book
Author
For Newbies
60 Minute Quick Start
Getting Started
Getting Started Guide
Installation
Conventions
Configuration
The Basics
Request Context
Routing
Event Handlers
Layouts & Views
Models
Interceptors
HMVC
Modules
Testing
Testing Quick Start
Testing ColdBox Applications
Digging Deeper
Async Programming
ColdBox Proxy
Controller Decorator
Flash RAM
HTML Helper
REST Handler
Request Context Decorator
Recipes
Scheduled Tasks
Architecture Concepts
What is MVC
What is ColdBox
How ColdBox Works
Testing Concepts
Functional Testing
Non-Functional Testing
Bugs Cost Money
Static Testing
Dynamic Testing
Developer Focus
Testing Vocabulary
External links
Source code
Issue tracker
LogBox
CacheBox
WireBox
Powered By GitBook
Non-Functional Testing
​Non Functional Testing are testing aspects that are not related to our specific requirements but more of the quality of our software.
  • Can our software scale?
  • Is our software performant?
  • Can it sustain load? What is the maximum load it can sustain?
  • What do we do to extend our security? Are our servers secure?
As developers, we sometimes forget the importance of non-functional testing, but what good is an application that meets the requirements but cannot be online for more than an hour? Both are extremely important and we must dedicate time to each area of testing so our software not only meets the requirements, but has great quality!
Previous
Functional Testing
Next
Bugs Cost Money
Last modified 4yr ago
Copy link
Edit on GitHub