AQuAMan

Overview

As a Peer Reviewer I want to have a fast and predictable method of checking the quality of application patches so that I do not have to exert a lot of time and energy manually checking these against the application standards.

As a Lead Developer I want to define and manage the quality standards that comprise the 'Definition of Good' for my application so that they can be applied and reported on in a peer review against an application patch.

Key Features & Functionality

Automate 80% of the Peer Review checklist items
Register Appian applications and define common standards across that application
Run a suite of tests across an application patch
Report on failed tests
Copy tests between applications
Define new object/attribute tests (including database table and view objects) and apply within an application
Set the reported significance for a failed test (Fail/Warning/Information)
Report on unused variables in Expression Rules and Interfaces
Report on the complexity score for Expression Rules and Interfaces
Report on missing labels/accessibility text for Interface Object components

Parents

lokeshk0623 over 3 years ago

AQA_ER_getObjectAttributeValueByAttributeName--its failing here in this rule, every time, we run a patch
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Comment

lokeshk0623 over 3 years ago

AQA_ER_getObjectAttributeValueByAttributeName--its failing here in this rule, every time, we run a patch
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Children

edn0001 over 3 years ago in reply to lokeshk0623

If you just updated like we had done it seems that the file structure of the patch has changed. I made some changes to AQA_ER_getPatchObjects and we were back up running.

fn!reject( fn!isnull, a!forEach( items: ri!patchContent, expression: if( and( contains( rule!AQA_ER_allObjectFileExtensions(), document( fv!item, "extension" ) ), /*file not called patches*/ document(fv!item,"name")<>"patches.xml" ) , fv!item, null ) ) )
- Cancel
- Up 0 Down
- Reply
- More
- Cancel