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
  • Hi Team, 

    The client has asked us if it would be possible to export the Aquaman analyzes. I have seen that the application has this two web apis: 

    But it seems that none of them work for what the client is asking for.

    Is there a way to expose these analyzes in a web api so that they are consumed by a CI/CD tool?

    Thanks! 

  • Hi  - whilst you cannot export the whole of an analysis in a WebAPI the WebAPIs you mention can be used as part of a CI/CD pipeline.:

    • AQA_WA_analysePatch - you can use this WebAPI to trigger an analysis. You need to pass AQuAMan the patch you want to analyse as a zip document; and you need to pass it the target Application UUID so that AQuAMan knows which registered application you want to conduct the analysis under. This WebAPI will return the PatchId to be used in the other WebAPI
    • AQA_WA_getPatchAnalysisSummary - your CI/CD pipeline can call this WebAPI (using the PatchId value returned from the previous WebAPI) to determine if the analysis has completed or not; and it it has what the overall analysis result is (which will either be "Pass" or "Fail")

    Were you expecting/wanting a WebAPI to be able to do something else?

Comment
  • Hi  - whilst you cannot export the whole of an analysis in a WebAPI the WebAPIs you mention can be used as part of a CI/CD pipeline.:

    • AQA_WA_analysePatch - you can use this WebAPI to trigger an analysis. You need to pass AQuAMan the patch you want to analyse as a zip document; and you need to pass it the target Application UUID so that AQuAMan knows which registered application you want to conduct the analysis under. This WebAPI will return the PatchId to be used in the other WebAPI
    • AQA_WA_getPatchAnalysisSummary - your CI/CD pipeline can call this WebAPI (using the PatchId value returned from the previous WebAPI) to determine if the analysis has completed or not; and it it has what the overall analysis result is (which will either be "Pass" or "Fail")

    Were you expecting/wanting a WebAPI to be able to do something else?

Children
No Data