Information
  • Author: Appian Corporation
  • Type: Utility
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Industry: All Industries
  • Compatible Version(s): 22.3
  • First Released:
  • Last Updated:
  • Cost: Free
Share
Home » AppMarket » AQuAMan

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

Anonymous
Parents

  • I try AquAMan with the version 23.1 and it doesn't work properly. Problem is due to XPath for object type and object attribute for interface. Previously the tag bname was rule but now interface.

    To solve this issue, it is necessary to update some rows of the SQL script by changing:

    /*[name()=\'contentHaul\']/*[name()=\'rule\'] => /*[name()=\'contentHaul\']/*[name()=\'interface\']

Comment

  • I try AquAMan with the version 23.1 and it doesn't work properly. Problem is due to XPath for object type and object attribute for interface. Previously the tag bname was rule but now interface.

    To solve this issue, it is necessary to update some rows of the SQL script by changing:

    /*[name()=\'contentHaul\']/*[name()=\'rule\'] => /*[name()=\'contentHaul\']/*[name()=\'interface\']

Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.