A test, or test case, is a set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement [after IEEE 610]. Silk Central supports various test types, and tests can be structured in several ways. | ||
Test types | ||
Manual tests are step-by-step instructions for testers. Silk Central provides a UI to efficiently execute manual tests, including the option to record videos and capture screen images during test execution. If desired, manual tests can later be converted to automated tests. |
||
A keyword-driven test is an executable collection of keywords. A keyword-driven test can be played back just like any other test. Silk Central and Silk Test support the keyword-driven testing methodology and allow a very close collaboration between automation engineers and business analysts by having automation engineers develop a maintainable automation framework consisting of shared assets in the form of keywords in Silk Test. These keywords can then be used by business analysts either in Silk Test to create new keyword-driven tests or in Silk Central to convert their existing manual test assets to automated tests or to create new keyword-driven tests. |
||
Unified Functional Testing (UFT) software, formerly known as HP QuickTest Professional (QTP), provides functional and regression test automation for software applications and environments. |
||
JUnit is a unit testing framework for the Java programming language. Use this test type for JUnit, Silk4J, and Selenium tests. |
||
NUnit is a unit testing framework for the Microsoft .NET programming language. |
||
MSTest is a command line utility from Microsoft that executes unit tests created in Visual Studio. Use this test type for MSTest and Silk4NET tests. |
||
The ProcessExecutor test type can be used to execute any command line. |
||
The Silk Performer .NET Explorer test type is used to execute .NET Explorer scripts or a specific test case of a script. |
||
Silk Performer projects can be integrated into Silk Central tests and directly executed through Silk Central. This allows for powerful test-result analysis and reporting. It also enables unattended testing, which means tests are run automatically by Silk Central based on pre-configured schedules. |
||
Silk Test Workbench is an automated testing tool that accelerates the functional testing of complex applications. Silk Test Workbench provides support for testing applications developed in a wide variety of development tools including Java, .NET, browser-based web applications, and COM components, including both ActiveX controls and automation objects. |
||
Silk Central’s Silk Test Classic interface offers a reliable means of automating Silk Test Classic users. Each test case of a Silk Test Classic script executes within its own test execution and produces its own results. |
||
The Silk Test Classic Plan test type is used for Silk Test Classic test plans. A test plan usually is a hierarchically-structured document that describes the test requirements and contains the statements, 4Test scripts, and test cases that implement the test requirements. |
||
TestPartner is a Micro Focus product that tests Web- and Microsoft Windows-based applications that use Microsoft technologies. |
||
Test structure | ||
Test containers are used to structure your test assets at the top level. Silk Central associates a defined source control profile and a product per container, which impacts what you can do with tests within a specific container. |
||
Use folders to structure your tests within a container. |
||
Test packages provide support for the structure of third-party test types in Silk Central, and consist of a package root as well as an arbitrary hierarchy of suite nodes and test nodes. |