Release: Silk Central 20.0

Micro Focus Expert
Micro Focus Expert
1 0 809

Micro Focus proudly announces the general availability of Silk Central 20.0! If you already use Silk Central and you have a maintenance contract, you can upgrade to Silk Central 20.0 for free.

Silk Central is an innovative and open test-management solution that aids collaboration and control for all testing-related activities. Silk Central allows users to unify all assets of the testing life-cycle in a central location for planning, execution (manual & automated), and reporting, by integrating with various requirements management, test automation, defect tracking, and source control tools, giving users full traceability of their software quality at all stages.

Business Process Testing

Silk Central 20.0 extends the Business Process Testing (BPT) capability by allowing the definition of input and output parameters for business components, therefore allowing an information flow between the business components to mimic the information flow between the actual business units. An example for such an information could be some OrderID that is the result of placing an order in the system. This OrderID is then given as input to the subsequent business component/unit for continuing the business process.BPT_inclInformation.jpg

The information flow is achieved by the introduction of so called input- and output-parameters for business components. This means you can define what information goes into a business component and which information is the result of a business component, that is then passed on to the next business component in the business process.

The following screenshot shows how parameters can be created for a business component:

ParamComponents.jpg

Once you have defined input- and/or output-parameters for business components you can easily assign values to them when creating the business process test in Silk Centra's Tests area.

BPTwParam.jpg

The sample above starts with a flow (combination of several business components) that takes user credentials as input and has the OrderID as output. The parameters Benutzername and Kennwort are defined on test level. The flow takes them as input and passes them on to the first business component of the flow where they result in a SessionID which is passed on as input for the subsequent components of the flow. The last business component of the flow generates the OrderID which is also the output of the entire flow, and can then be used by any subsequent business component after the flow.

Parameters are matched via their name - in the sample above the flow returns the OrderID. Therefore in subsequent business components that have OrderID as input the OrderID of the flow is automatically mapped.

This can lead to conflicts in cases where several components return the same output. For example you could have a business process where several orders are created - in that case the flow in the sample above is added several times to your test. However when executing the test the business components after the flows will have the last OrderID available only. The OrderIDs of the previous flows is overwritten. To prevent this you will have to store the OrderIDs in temporary parameters which you can simply create by writing them into the cell of the grid - e.g. ${OrderIDNo1}.

Parameters are contextual - this means they are available within a specific context. For example the SessionID in above sample is available in the flow but not outside of the flow. To make it available for subsequent business components it would have to be an output parameter of the flow.

During test execution the input- and output-parameters are available in the business component section of the manual testing window:

BPTParamMTWin.jpg

And of course the input- and output-parameters are also part of the manual testing results:

BPTParamResults.jpg

Usage Data Collection

With Silk Central 20.0 or later, you can join the Silk Central Improvement Program and help us improve your test management experience.You can choose to participate in Silk Central's System Administration:

CustomerFeedback.png

When you participate information on Silk Central's usage is tracked based on certain events - like starting executions, synchronizing requirements, and creating new issues. 


Customer Driven Innovation
Administration

  • Increased security for JMX access for Application-, Frontend-, and Chart-server.
  • Increased security for RMI communication between Application- and Execution-server.

Tests

  • Business Process Testing Office (Excel) Import

Execution Planning

  • Business Process Testing - Tracking Progress

Activities

  • Re-running multiple execution plans from the Last Executions grid.

Integrations

  • Atlassian JIRA 8 Support
  • AccuRev 7.2 Support
  • QC Migration enhancements

Currency

  • Microsoft Windows Server 2019 Support
  • Microsoft SQL Server 2014 SP3 and Microsoft SQL Server 2016 SP2 support

More information

  • For more information on all new features of Silk Central 20.0, you can also refer to the Online Help.
  • Another valuable source of information: the Silk Central 20.0 Release Notes.
  • If you are already convinced and want to buy Silk Central, do not hesitate to contact us: Go to www.microfocus.com and click Contact Us on the top right.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.