NOTICE: Our Community is moving. Get more information.
Micro Focus proudly announces the general availability of Silk Central 19.0! If you already use Silk Central and you have a maintenance contract, you can upgrade to Silk Central 19.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.
In order to meet the accessibility requirements of blind or visually impaired users, Silk Central 19.0 focuses on enhancing the navigation of Silk Central through use of the keyboard and by facilitating audible feedback through use of screen readers.
Micro Focus recommends using NVDA in combination with Mozilla Firefox.
In order to support organizations in improving security, Silk Central 19.0 now allows using a web-service token for authentication through web services rather than user name and password.
Using such a web-service token increases security as your username and password are no longer sent over the network. Additionally, if you are using LDAP integration, using a web-service token makes the authentication independent of your password update policy and reduces the maintenance effort to keep integrations working. As long as a web-service token is not deleted or no new token is created for the same user, the token remains valid and grants access to Silk Central web services. Handle a web-service token with the same care that you would apply for any other authentication factor.
The Audit Log contains information about certain user actions, for example when users log on and log off. To protect this information, Silk Central 19.0 introduces an additional permission to allow organizations increased granularity on specifying which users have access to the Audit Log.
Depending on the log level, log files contain more or less information about certain processes of the system. Depending on the test environment, this can be sensitive information or a valuable documentation of error scenarios. To protect this information from unauthorized viewing and careless deletion, Silk Central 19.0 introduces new permissions for viewing and deleting such log files.
To enforce consistency and to prevent uncontrolled creation or customization across projects, Silk Central 19.0 introduces new permissions for managing and deleting status reasons.
One of the prime directives of baselines is that they must not be changed as they represent a certain state like a special checkpoint or a release. When using shared libraries with previous versions of Silk Central, it was not possible to prevent users from performing changes to shared test steps or keywords which might cause a change to a baseline. With Silk Central 19.0, this is solved as shared libraries now can be set to be read only. This functionality is controlled by the new Set libraries read-only permission.
In Silk Central 18.5, shared tests were consumed through a copy and paste approach. In Silk Central 19.0 this approach is replaced with a selection UI where tests can be selected from a dialog within the consuming project. Copy and paste between a sharing project and a consuming project no longer creates a reference.
Depending on the testing approach that is taken by an organization, projects may start by consuming tests from a central repository for consistent testing of a functionality across projects. When tests need to be customized due to variation in functionality in the context of the consuming project, the tests should be detached from the central repository - consequently becoming local to the project and no longer requiring change updates from the template. For this purpose it is now possible to simply delete the reference for tests in the consuming project. Such a removal is also tracked in the history to allow understanding who and when removed a reference.
Changing a test in the sharing project can have significant impact on all consuming projects. For that reason, each test in the sharing project now provides a Usages tab where all consuming tests are listed.
In the previous version of Silk Central, test type changes were not automatically consumed, which means you had to manually change the test type in the consumer project. With Silk Central 19.0, changes to the test type are consumed as any other change and you no longer need to perform such manual changes.
Silk Central further extends its ability to integrate with existing tooling ecosystems by providing functionality to consume results for automated tests without having those automated tests executed through Silk Central execution servers.
This allows users with existing proprietary execution environments, which are too complicated or special to be adopted to the execution environment of Silk Central, or users with automated test results from various sources, for example continuous integration (CI) systems, to still collect all results of their whole testing process in one central place and to associate these results with their requirements, versions, and builds for holistic reporting and decision making.
The whole process around test creation, which means the representation of the actual test in Silk Central, and around execution planning does not change. You create tests in Silk Central and assign these tests to execution plans to execute them.
The difference is in the deployment settings of the execution plan. Instead of specifying an execution server, you enable the so called External execution of assigned tests.
Running such an execution plan then results in an execution plan run that is visible like normal execution plan runs in the Silk Central UI, with the difference that this execution plan is waiting to receive results from the external execution environment.
To interact from external with such external execution plan runs, Silk Central 19.0 introduces a whole new REST API to query information around the execution plan run itself and its assigned test runs. Furthermore, the new REST API allows uploading result files and setting the status for single test runs as well as finishing the overall execution plan run. The REST API can be explored through an interactive documentation on the machine where Silk Central is installed by navigating to the URL [host]:[port][/ instance]/Services1.0/swagger-ui.html, for example http://localhost:19120/Services1.0/swagger-ui.html.
Custom step properties are now also included in the information which is made available in Excel for the purpose of manual offline testing.
To provide a better overview on currently running tests, the Current Executions view of the Activities page now shows the status of the execution plan.
When distributed test execution is activated, there is a different state for each test in an execution plan. Therefore the execution state information is made visible for each test execution in the execution plan run details. Each test is handled individually like an execution plan having one test assigned. For each assigned test, you can now see whether the test is waiting for an execution server, is currently executed, is fetching results, or is already finished.
Silk Central 19.0 offers a new REST API for triggering executions and getting results of finished runs. With this API it is also possible to pass parameters when starting a run.
Silk Central now allows access to mobile devices that are provided through Mobile Center for use in the manual testing process.
The JQL string can now have up to 1000 characters, instead of the 128 characters that were allowed in previous versions of Silk Central.
Silk Central 19.0 now supports Team Foundation Server 2017 for source control integration and issue tracking integration.
Silk Central 19.0 comes with a gradle script (in Help/Tools) that can be used in any CI solution that allows the execution of gradle scripts in their build process. Therefore the CI integration is no longer limited to Jenkins. This gradle script is based on the new REST API and provides more flexibility in terms of how executions can be started (all tests, failed test only, etc.) and what information is passed (build, source control branch, custom parameters, etc.).
The Silk Central Jenkins integration now supports the usage of pipelines, allowing a more efficient approach for continuous integration.
Silk Central 19.0 now supports SAP Solution Manager 7.2 for requirements integration and issue tracking integration.
Silk Central 19.0 now supports Microsoft SQL Server 2017.