- Bill Burlein
- Bryan Williams
- Celina Buczkowska
- Daniel Ryerson
- David Ensinger
- Fred Faulkner
- Jeff Brown
- Jennifer Daugherty
- John Kraus
- Josh Durbin
- Justin Pittman
- KC Dunstan
- Mark Daugherty
- Matt Van Bergen
- Matthew Young
- Melissa Geoffrion
- Michael Kang
- Michael Paull
- Michael Chan
- Michael Hodgdon
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Robb Winkle
- Rohit Srinath
- Tom Kelly
Invisible requirements within Business requirements
Wednesday, May 15, 2013
Testing in an author environment can have its own challenges. Component's configurations need to be tested at this level to achieve correct content authoring. So, when faced with fields upon fields of data for each component needing to be validated, more often than not we are left with little to no requirements to validate these fields.
Button component configuration consists of: Text field, Link field and Open link in new window checkbox
As a tester I start validating each field by using negative test cases:
· Leaving fields empty, will ‘error message: this is a required field’ be displayed?
· Are invalid links allowed in ‘Link Field’?
· Is there a character limit to the Text Field?
· Any limits set for each field?
Within AEM we need to start looking closely at these hidden requirements that are not brought up during Inception. Not validating these fields properly could have a huge impact on how the site is authored. Eliminating any and all ambiguities in components will give content authors a better understanding of how components are configured and how they act. Invisible requirements are not so invisible after all!
- Introducing Touch UI Support in the CQ Component Plugin
- The Top 3 Reasons to Attend CIRCUIT, Our AEM Developer Conference
- AEM 6.x mongo-backed clustered author setup
- 3 Cloud Paradigm Shifts
- Groovy Component Composition With Traits
- Adobe Summit - I Remember When Geometrixx was just a Shapes Company
- New Features for the venerable AEM Groovy Console
- Resolution Independence with SVG in Adobe AEM (formerly CQ)
- Five Good Reasons to Use Grunt for Front End CQ Development
- Creating a Custom Content Importer for AEM/CQ5