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
Anonymous
Parents
  • v7.0.0 Release Notes
    • This release augments the existing 'Code Complexity' report to include a report on any 'Magic Numbers' that the SAIL code might contain (numeric literals that probably should be encapsulated in a constant or dynamically retrieved from a data source rather than embedded in the code with no accompanying context.
Comment
  • v7.0.0 Release Notes
    • This release augments the existing 'Code Complexity' report to include a report on any 'Magic Numbers' that the SAIL code might contain (numeric literals that probably should be encapsulated in a constant or dynamically retrieved from a data source rather than embedded in the code with no accompanying context.
Children
No Data