Our world is moving quickly and therefore, short time to market is more important than ever before. Everyone who is working in the software testing business is constantly challenged with reduction of testing time and shorter release sprints.

There are some who tend to cut quality assurance to the absolute minimum, and in some cases, the customers are assessing their products. I understand this trend to some extends but we need to keep in mind that our end user cannot test non-functional requirements.

While your end user community can conduct some functional tests, non-functional requirements must be verified in your test labor as early as possible in the lifecycle. Late detected performance or security faults would be expensive, result in frustrated user, or in worst cases, in critical outages or data loss.

However, make testing of non-functional requirements, namely, security and performance testing, part of your development pipeline. Also, NFR testing will reduce risks and gives you the opportunity proactively solve issues before they affect your user community.




Posted by JM

Resourceful, solution-focused and intuitive reliability engineer with over 15 years of demonstrated success in architecting, developing and maintaining effective testing and monitoring solutions. Offers a wealth of knowledge and experience surrounding modern application architecture and development of best practices.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s