Quantcast
Channel: Silk Central Blog
Viewing all 43 articles
Browse latest View live

Released: Silk Central 18.5 Hotfix 2

$
0
0

Silk Central 18.5 Hotfix 2 Readme

Software requirements:

Silk Central version 18.5.0, Build 7703

Resolved Issues in Hotfix 2:

The following issues have been resolved in Silk Central 18.5 Hotfix 2:

RPI #1113078 JIRA issue types are now sorted in ascending alphabetical order (case insensitive) in Silk Central's New Issue dialog
RPI #1113109 General stop of automated execution deployment when deleting execution plan that has a run in Waiting state.
RPI #1113260 Silk Performer integration: Fix store of PQuantile data.
RPI #1113513 Configurations List Issue: "Unexpected error persisting data."
RPI #1113590 Dataset is not synchronized after importing large project.
RPI #1113720 Test cases are not available in the Manual Execution Planning view and Testing Cycle Timeline panel OOM if span over DST.
RPI #1114066 Silk Central freezes when trying to create Git integration.
RPI #1114156 Failed to synchronize Epics from JIRA to Silk Central.
RPI #1114159 Synopsis not respecting mode and group permissions.
RPI #1114238 Run automated tests manually with a setup results in "No execution tree context".
RPI #1114554 Report on requirement properties: ORA-22835 - Buffer too small for CLOB to CHAR or BLOB to RAW.
RPI #1114568 Project owners sorted by login instead of username.
 
Fix Restrict authenticated session cookie to specific paths and httpOnly.
 

If you have any questions on this you can also log a case directly by using the following link: Log Support Incident.

You can download the hotfix from Micro Focus SupportLine


Released: Silk Central 19.0 Hotfix 1

$
0
0

Silk Central 19.0 Hotfix 1 Readme

Software requirements:

Silk Central version 19.0.0, Build 8086

Resolved Issues in Hotfix 1:

The following issues have been resolved in Silk Central 19.0 Hotfix 1:

RPI #1115923 LDAP configuration not working.
RPI #1115875 Not possible to generate a baseline.
RPI #1114632 BIRT Report Corrupted.
RPI #1115136 Issue Manager description edit lost when attach file.
RPI #1114977 Runs duplicated in Tracking window.
RPI #1114554 Report on requirement properties: ORA-22835 - Buffer too small for CLOB to CHAR or BLOB to RAW.
RPI #1114900 Fixed ThreadConnectionLimitException on viewing or creating an issue.
RPI #1115490 Running TestNG tests from Process Executor - Unable to parse JUnit results.
RPI #1115415 Custom roles issue Silk Central - Issue Manager.
RPI #1115960 Inactive test attributes can be assigned in GRID view
RPI #1115400 KDT - Screencast of mobile device does not work in Chrome, Edge, and Firefox.
RPI #1114608 Clearquest 8.0.17 integration with Silk central 18.0
RPI #1115427 Test Container properties view: Swapped values for custom data directory and custom include directory.
RPI #1115584 Performance issue when editing test attributes.
RPI #1115844 Execution Status Overview report fails for projects with ID > 1000.
RPI #1115924 Project import: Don't duplicate test parameters if a parameter with the same name and type already exists.
RPI #1115963 Fixed test results for finished testing cycles: Include test runs of deleted tests in Manual Test Results view.
RPI #1116106 Cannot filter on any attributes in a test.
RPI #1114568 Project owners sorted by login instead of username.
 
- CheckDB: Check Data Source Attributes - Exception.
- Fix download of metrics in SystemDiagnostics.
- Update to jQuery 3.3.1 and jQuery UI 1.12.1.
- Add rel="noopener noreferrer" for external links. Changed nginx.conf.template to include examples for secure configuration.
- Creating project baselines: Improve error logging on data-driven table import.
- Support OrderedTests in MSTest plugin. Adding tests to the orderedtest file more than once is not supported.
 

If you have any questions on this you can also log a case directly by using the following link: Log Support Incident.

You can download the hotfix from Micro Focus SupportLine

Released: Silk Central 19.5

$
0
0

Micro Focus proudly announces the general availability of Silk Central 19.5! If you already use Silk Central and you have a maintenance contract, you can upgrade to Silk Central 19.5 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.

Self-registering Execution Server

Silk Central now enables the registration, which means the creation and the assignment to a location and therefore to a project, of new execution servers through command line.

Just download the new Execution Server Launcher from Help/Tools and start-up the Execution Server via command line - e.g. java -jar sc-execserverlauncher.jar -u http://scserver:19120 -t dd31f14d-443b-4494-821b-2a6aa22609bd -l mylocation -k Commandline,Windows - to assign it to the location "mylocation" and use it in any project that has this location assigned.



This gives you the flexibility to use your execution resources when and where you need them, without any manual overhead. Additionally, the Execution Server Launcher keeps the execution server on the most current version and will attempt to re-start the execution server in case of an unintended termination.

Business Process Testing

Silk Central 19.5 introduces business process testing (BPT) with the intention to help customers address the challenges of validating end-to-end business transactions. Typically such an end-to-end business transaction represents a sequence of actions that are conducted by several business units in collaboration to achieve a certain goal/result.

For example buying some goods in a web-shop will trigger an end-to-end transaction which might involve different business units like sales, manufacturing, quality assurance, shipping, and accounting.






Business Process Testing in Silk Central allows the modelling of such end-to-end business transactions with the help of following newly introduced assets types:

  • Business Component - Set of actions for one business unit (sequence of manual steps and shared steps)
  • Flow - Part of an end-to-end transaction with the purpose of re-using it in different business process tests (sequence of business components)
  • Business Process Test - Representation of the entire end-to-end business transaction (sequence of business components and/or flows)

 

 

The assigned business components and/or flows are later executed in sequential order - therefore their sequence should match the sequence in the end-to-end business transaction.

For modelling the responsibility and collaboration of certain business units it is possible to assign user groups to each business component of a business process test or flow. The users of these groups will later execute the manual test steps of the currently executed business component.

Further it is possible to define an exit criteria (continue/stop on failure) for each assigned business component to prevent the execution of business components of an already failed - due to a preceding failed business component(s) - business process test. This is in accordance to the nature of end-to-end business transactions where the success/quality is also determined incrementally by the success/quality of each business unit.

Business process testing is an extension to Silk Central's manual testing - therefore the execution happens via the same manual testing interface which opens up when clicking the "Continue Manual Test" icon in the Manual Tests Assigned to Me panel, or the Current Runs tab of your execution plan, or in the Current Executions of the Activities.

Manual tests and business process tests are shown together in the same list of tests that have to be executed. The difference is that business process tests have an additional section where the currently executed business component is shown.


The steps at the bottom are consequently for the currently executed business component of the business process test. Once all steps are executed clicking "Finish Component" will trigger following things:

  1. set the status for the current business component
  2. evaluate the exit criteria for the business component (continue or stop the business process test execution)
  3. pass the test on to the next business unit (assigned user group) that executes the next business component

Hence one business component after the other is executed by the responsible business unit (assigned user group) till one result for the entire business process test is created.




Customer Driven Innovation

Administration

  • User management - Quick-navigation link between users and groups
  • Permission for changing the test run status
  • Permission for importing/updating tests from Excel

Requirements

  •  Full path information for tests in the Assigned Tests tab

Tests

  •  Ability to re-create requirements assignment for shared tests when requirements have been imported from Excel

Execution Planning

  • Manual Execution Planning - Multi-selection for filtering matching tests by several test containers and/or test folders.
  • Manual Execution Planning - Show TestId in Test Assignment grid for easier identification
  • Manual Execution Planning - Notification (eMail) when reassigning tests in an already running testing cycle
  • Manual Test Results - Ability to hide issues based on their status for better readability
  • Result cleanup rules - Ability to trigger them manually via the "Delete Runs or Result Files" dialog
  • Result cleanup rules - Extended Delete after setting (18 and 24 months)
  • Result file size limit for automated test executions

Activities

  •  Show project name in Cross-Project Activities

Issue Manager

  • Full change history for all fields involved in the issue tracking workflow
  • Ability to add attachments when creating new issues

API Enhancements

  •  Ability to re-run failed and not executed tests of an Execution Plan

 

Integrations

IBM Rational Doors

  • Ability to filter requirements that should be synchronized to Silk Central

Atlassian Jira and Jira Agile

  • Support for field types Epic Status and Label

StarTeam

  • Ability to create issues in StarTeam with an existing type that is different to the default Change Request type

Silk Test

  • Support for new HTML result format

HP Quality Center Migration

  • Migration of requirements, tests, design steps, test sets, issues, their attachments, and traces to each other


AdoptOpen JDK

Silk Central 19.5 now internally uses the libraries of the AdoptOpenJDK instead of the Oracle JRE. This change affects all servers, which means the application server, the front-end servers, the chart server, and the execution server, as well as the communication and interaction between all servers.

There is no dependency between any installed JRE and Silk Central's internally used JRE libraries, except if you require an execution server to run in 32bit mode. For this you will need to use the Execution Server Launcher (or the Execution Server Package) and your own installed 32-bit JRE.

 

More information

  • For more information on all new features of Silk Central 19.5, you can also refer to the Online Help.
  • Another valuable source of information: the Silk Central 19.5 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.
Viewing all 43 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>