SDLC Analytics with Extension DesignerExtension Designer provides an interface for creating and managing standalone snippets of data processing logic, called “workflows” or “slices”, that provide visibility into potential problem areas within the code, as well as potential problematic processes. Extension Designer 5.3.2 leverages the latest Development Testing Platform APIs, as well as APIs from third-party systems (e.g., JIRA), to query data for processing and generate reports. This release also features a consolidated interface for Enterprise Pack extensions (PIE Slices, DTP Workflows, and Policy Center practices) and simpler integration with Policy Center and DTP. See Extension Designer for additional information. New and Updated ExtensionsThis release includes updates to the following artifacts: PIE Slices- Change Based Testing: Enables organizations to efficiently reduce risk by focusing on the tests that need to be re-executed due to changes in the code base, rather than the whole test suite.
- Risky Code Changes: When code changes it represents risk, this slice analyzes the changes in the code by looking at how maintainable the code is versus how well it is tested. The slice then assigns a risk level and shows the end-user how much "quality debt" exists.
- Modified Coverage: Getting 100% coverage on the entire code base is impossible when you have a large legacy code base. But it is the new or modified code that represents the risk. By focusing on the changing code, this slice enables you to efficiently eliminate the risk associated with change.
- Test Stability Index: Test stability is an ongoing issue for many organizations. Developers and tester know that unstable tests are going to fail from time to time, so they are ignored. But when there are thousands of tests, determining a failure associated with a legitimate problem is difficult. This slice helps remove the noise by scoring each test to categorize it’s stability. This allows teams to focus in two ways:
- Fix the "real failures" now, because this usually indicates you have an immediate problem/regression.
- Quantify which tests need to be stabilized.
- Key Performance Indicator: The volume of static analysis violations is not always the best indicator of team performance. The KPI slice enables you to define multiple custom profiles that weight static analysis rules differently and calculate an overall score for that KPI.
DTP Workflows- Traceability Report: Provides a customizable Test Traceability widget and Requirement Traceability widget. Each widget drills down into interactive reports that help you understand how well requirements are being implemented and tested.
- Static Analysis Violation Reporter for Atlassian JIRA: Provides an example of how to use the Atlassian JIRA importer to create and manage JIRA bugs and/or tasks for problems (e.g., static analysis violations or unit test failures) found during test and analysis.
- Test Failures by Build: Creates a widget that lists DTP build IDs with dynamic analysis test failures.
- DTP Build Review Workflow: Provides an example of how to automate the creation of Change Reviews (see Change Explorer for more details), as well as specify a user who will receive automated email notifications about the reviews created.
- Export DTP Explorer Data to CSV: This workflow accepts any parameter URL from DTP's Test Explorer and Violations Explorer and generate a CSV output.
- DTP File Based Licensing Report: If you are using a file-based DTP license, this workflow provides detailed information about your Parasoft DTP license consumption/usage.
Policy Center Practices- Code Coverage: Defines expectations around code coverage and ensures that an acceptable level of coverage is achieved.
- Defects for JIRA: Defines expectations around the number of Bugs present in a JIRA project to ensure that large numbers of bugs are not left unattended.
- Metrics: Allows you to monitor various code metric values by defining thresholds and aggregators.
- Regression Test: Ensures that the number of acceptable regression test failures is within the specified threshold for the project.
- Static Analysis: Ensures that static analysis violations that are considered high severity are remediated within an acceptable period of time.
See Extensions for DTP Enterprise Pack for additional information. Enterprise Pack Node ChangesUpgrading from PIE 1.x to newer versions of Extension Designer requires a manual migration for its database and flows. Endpoint NodeThe Endpoint Node is new in this release. It exposes a service endpoint that encapsulates all the functionality necessary to create a full-stack web component. The node acts as an "http in" node, but the actual endpoint is abstracted from the user in place of a UUID. Instead the user focuses on choosing, or creating, the front end UI component that should be tied to the endpoint, as well as implementing the flow that will generate the data to drive the component. This abstracts the integration details away from the user and allows them to focus solely on the business logic. Capability: - DTP Custom Widget: The node is used in this widget to automatically deploy to the DTP dashboard.
- DTP Custom Report: The node is used in custom widgets that drill down into a DTP report or custom report. See Risky Code Changes for an example.
- Policy Center Practice: The node is used to enable Policy Center practices.
- General: The node can be used as a general REST API endpoint for third-party integration, CLI calls to export data, etc.
PIE Event InReplaced by the Event In node in this release. PIE Event OutReplace by the Event Out node in this release. DTP MQTTReplaced by theEvent In and Event Out nodes in this release. Event InThe Event In/Out nodes are new in this release. They connect to Extension Designer’s own MQTT Event Broker and manage events between services or external components. It also subscribes to DTP’s event broker at startup, so you don’t need a separate DTP connection for subscribing to a DTP Event. With architectural changes, internal PIE events are all replaced with custom events in the Extension Designer Event Broker. Any DTP events can be used with the “DTP” group. Please refer to node info documentation for more information. See Subscribing To DTP Events for details about DTP events. Built-in PIE Events are no longer available. New and fixed violation event are deployable from the Extension Designer menu by choosing Import> Library> Common> Violation Events. Starting with DTP 5.3.0, the recurring violation event is no longer supported as a result of updates to the API. Event OutSee Event In. PC REST API (New)This node is new in this release. It is used by Policy Center Practices (such as Policy Center Practice - Code Coverage) to enable interaction with Policy Center via the Policy Center REST API. Model SettingsReplaced by the Profile Search node in this release. Profile SearchThe Profile Search node replaces Model Settings node. The properties did not change, but importing old flows from PIE Slice Designer (version 1.x) will cause an error. Re-configure any flows that use the Model Settings node to use the Profile Search node. Project FilterRemoved in this release. Use the lodash library in the function node to filter payloads. See The Function Node for additional information about the lodash library. See How to Update Violations Metadata for an example of lodash usage. Violation FilterRemoved in this release. See Project Filter for additional information. Violation GrouperRemoved in this release. See Project Filter for additional information. Prioritization ViewRemoved in this release. This node is only compatible with the DTP REST API version 1.2 or older. See the REST API documentation for additional information. For additional information on how to set metadata, choose Import> Library> Examples> Static Analysis Prioritization and view the documentation. Removed in this release.This node is only compatible with the DTP REST API version 1.2 or older. See the REST API documentation for additional information. For additional information on how to set metadata, choose Import> Library> Examples> Dynamic Analysis Metadata and view the documentation. PIE MailReplaced by the Mail node in this release. MailReplaces PIE Mail node. Additional Updates for Enterprise Pack |