mopdf.com

Concept Manual vTESTstudioOverview2.4.3 Re-Use of FilesLinking of filesFiles can easily be re-used by linking them to other test units. This is done by movingthem from the source to the destination using a drag & drop operation. Thus, forexample, the same test sequence can be re-used in multiple test units, e.g. with onlyusing different parameter files for parameterizing the test sequence.Figure 5: Project view with re-used file Main.vtt2.4.4 Home Directory and LibrariesHome directoryThe directory where the project file is located is called the Home Directory. Filesfrom the root directory and files from specially defined Libraries can be used in theproject.LibrariesThe Libraries view provides a filtered view of the file system. A library represents onlya folder on the file system that is made known in the project. Files from libraries canalso be linked to test units using a drag & drop operation.If a library folder is moved on the file system, in vTESTstudio only the link to thelibrary has to be updated. The paths of the linked files in the test units are updatedautomatically. Vector Informatik GmbHVersion 7- 12 -

Concept Manual vTESTstudioOverview2.4.5 Storage Location of Files on the File SystemStorage of filesIf a file is created in the context of a test unit, it is automatically created on the filesystem under the path Home Directory \ Test Unit Name .If the files are to be organized differently on the file system, this can be done usingthe Home Directory view. This view shows the file system located underneath theproject directory. If a file is moved in this view, possible links to this file in the testunits will be automatically updated.2.4.6 Structuring Using (Shareable) FoldersRe-use of foldersIn order to structure the contents of test units more clearly, folders can be createdwithin a test unit (as many folders, including nested folders, as required). This has noeffect on the content of the test and is only used to organize files.In addition to re-use individual files, the re-use of whole folders is also possible. Forexample, if a folder contains a test sequence description and an associatedparameter file, these two files can be re-used together by linking the whole folder toanother test unit.If a folder with files is created underneath a test unit and then linked to another testunit, the folder with the original files is located on the file system underneath the firsttest unit. If such a "master test unit" is not desired, the folder can be created as ashareable folder instead. This is done by the project's shortcut menu command NewShareable Folder. Folders and files created by this are created on the file systemunder the path Home directory \ Shareable Folders . From there they canalso be linked to the test units using a drag & drop operation.2.5Concepts for High Test CoverageParameterized testcase listsFor high test coverage without significant programming effort, so-calledparameterized test case and test sequence lists are supported.To defined a test case list, a test case with input parameters must be defined, forexample, in C#:[Export][TestCase]public static void CheckMotor(int temperature, double voltage){// .}The test case list for this can be defined in the Test Table Editor, for example. Thecommand selection contains a CheckMotor [list] entry for this purpose. If this entryis chosen, an editor appears that can be used to assign multiple values for each testcase parameter: Vector Informatik GmbHVersion 7- 13 -

Concept Manual vTESTstudioOverviewFigure 6: Parameterized test case list in the Test Table EditorIn addition to the input of individual values or a range, the use of list parameters andstruct list parameters from parameter files is supported as well (also see sectionParameters):Figure 7: Using list parameters in test case listsBy a sequential combination, a number of test case calls are now generatedautomatically so that each parameter values is used at least once: Vector Informatik GmbHVersion 7- 14 -

Concept Manual vTESTstudioOverviewFigure 8: Generated test case list using SequentialIf a higher test coverage is to be achieved by testing pairwise or every combination ofparameter values, the Combinatorics property must be changed from Sequential toPairwise or Combinatorial: Vector Informatik GmbHVersion 7- 15 -

Concept Manual vTESTstudioOverviewFigure 9: Generated test case list using CombinatorialFor the definition of a test case list in the Test Table Editor or in C#, all languagecombinations or crossovers listed in Language Interaction are supported. Vector Informatik GmbHVersion 7- 16 -

Concept Manual vTESTstudio2.6OverviewTraceability by the Connection of REQM/TDM ToolsConceptYou can use vTESTstudio to trace externally defined requirements and testdescriptions during test implementation and in the test report (traceability). This isdone using exchange files in an open XML format. As a result, any REQM/TDMsystem can be used coupled with vTESTstudio.SchemaFigure 10: Traceability workflow Vector Informatik GmbHVersion 7- 17 -

Concept Manual vTESTstudioOverviewImport ofrequirements or testdescriptions invTESTstudioThe information exported from the REQM/TDM system is imported into vTESTstudioand can be linked there to test cases. The linked elements can be requirements ortest descriptions. Because these elements are used to achieve traceability, they aredesignated as trace items.Trace Item ExplorerAll trace items imported into a vTESTstudio project are available via the Trace ItemExplorer. From there, they can be easily linked to test cases using drag & drop.In the REQM/TDM system, requirements and test descriptions might be structured inhierarchical folders or comparable elements. These folders are displayed in the TraceItem Explorer in the same hierarchy. However, folders cannot be directly linked to testcases.Traceability MatrixThe Traceability Matrix in vTESTstudio gives an overview over all trace items of theproject and their test case links. By this overview of test design coverage you caneasily see, for example which trace items are not covered yet by any test caseimplementation. Furthermore, from within the traceability matrix comfortablenavigation from a trace item to linked test cases is possible. For documentationpurposes the traceability matrix can be exported to Excel.Figure 11: TraceabilityImport of designtraceability inREQM/TDM systemFor synchronization with the REQM/TDM system an export of the traceability matrixto XML is supported. This enables importing the information about implemented testcases and linked requirements or test descriptions to the REQM/TDM system.Planning of testexecutionBased on this information test case execution can be planned, i.e. which test casesshall be executed. With the help of a so-called “test execution plan” the selection andexecution of test cases in CANoe can be automated.Test reportFor each trace item linked to a test case, the test report contains a correspondingreference at the test case. This enables traceability from the test case result back tothe requirement or test description.Import of test resultsThe test report can be played back to the REQM/TDM system to be able to analyze Vector Informatik GmbHVersion 7- 18 -

Concept Manual vTESTstudioin REQM/TDMsystemOverviewtest results within this system.SupportedThe connection of the following systems is supported out-of-the-box:REQM/TDM systems Vector PREEvision TDM Squore / Software Analytics IBM DOORS (classic) IBM DOOR NG und Rational Quality Manager Siemens Polarion ALM PTC Integrity Lifecycle Manager Jama Connect Intland codeBeamer ALMSo-called “Connection Utilities” are available for free. By a command line interface,they can be used for continuous integration and continuous testing as well (e.g. withJenkins).Further REQM/TDM systems can be connected by the use of the open interfaces. Vector Informatik GmbHVersion 7- 19 -

Concept Manual vTESTstudio2.7OverviewTest Design DocumentationConceptFor a test unit in vTESTstudio a test design documentation in PDF format can begenerated automatically. This test design documentation provides an overview of allimplemented test cases and test steps. Beyond the documentation it can be used forinternal and external reviews of the test design.Figure 12: Automatically generated test design documentation as PDF Vector Informatik GmbHVersion 7- 20 -

Concept Manual vTESTstudioTest Design Editors3 Test Design EditorsIn this chapter you find the following information:3.1CAPL Editorpage 223.2C# Editorpage 233.3Test Table Editorpage 243.4Test Diagram Editorpage 253.5State Diagram Editorpage 26 Vector Informatik GmbHVersion 7- 21 -

Concept Manual vTESTstudio3.1Test Design EditorsCAPL EditorFeaturesThe CAPL Editor integrated in vTESTstudio provides the functions of a moderndevelopment environment such as Code completion and syntax checking while writing Configurable syntax highlighting Syntax-sensitive indentation Expandable function blocks and function reference in a tree structure for fasternavigation Hierarchical function list with search function for direct transfer to the source text Direct transfer of network symbols, environment data, diagnostic symbols, andparameters from the Symbol ExplorerUser interfaceFigure 13: CAPL EditorAccess to symbolsDirect access to signals, frames and environment data is possible by the CAPL API.This enables e.g. read and write access to signal values in the CANoe runtimeenvironment. Example: Velocity 100;Event proceduresIn addition to the programming of sequential test sequences, test cases, andfunctions, the programming of event procedures is possible. In order to react toevents (e.g., a signal change) in CANoe, event handlers can be defined. Themethods are then called as soon as the event occurs during the test. Vector Informatik GmbHVersion 7- 22 -

Concept Manual vTESTstudio3.2Test Design EditorsC# EditorFeaturesSimilar to the CAPL Editor, the C# Editor integrated in vTESTstudio provides thefunctions of a modern development environment such as Code completion and syntax checking while writing Configurable syntax highlighting Syntax-sensitive indentation Expandable function blocks Hierarchical function list with search function for direct transfer to the source text Direct transfer of network symbols, environment data, diagnostic symbols, andparameters from the Symbol ExplorerUser interfaceFigure 14: C# EditorAccess to symbolsAutomatically generated .NET classes are available for accessing signals andenvironment data as well as CAN frames. These enable access to the values in theCANoe runtime environment. Example:Velocity.Value 100;Event proceduresIn addition to the programming of sequential test sequences, test cases, andfunctions, the programming of event procedures is also possible with the C# Editor. Inorder to react to events (e.g., a signal change) in CANoe, event handlers can bedefined by the use of a special C# attribute. The methods are then called as soon asthe event occurs during the test (exactly the same as in CAPL).Connection to MSVisual StudioBy an integrated connection it’s also possible to use Microsoft Visual Studio for thedevelopment of tests in C# as an alternative to the C# editor in vTESTstudio. Vector Informatik GmbHVersion 7- 23 -

Concept Manual vTESTstudio3.3Test Design EditorsTest Table EditorOverviewThe Test Table Editor allows users to easily define test sequences in tabular formwithout the need for programming expertise. Special commands are available forstimulating and testing the system under test.FeaturesTo make work easy, the following features are available: Command and symbol completion while writing Direct transfer of network symbols, environment data, diagnostic symbols, andparameters from the Symbol Explorer Symbol and value type checks while editing Access to user-defined functions and test cases in other languages Ease of operation using both the keyboard and the mouseUser interfaceFigure 15: Test Table Editor Vector Informatik GmbHVersion 7- 24 -

Concept Manual vTESTstudio3.4Test Design EditorsTest Diagram EditorOverviewThe Test Diagram Editor can be used to define tests in a graphical way. Thegraphical notation is particularly suitable for reviews. Test code in tabular notation islocated behind each graphical element. By default one test case is generated foreach path through the diagram; a more fine-grained test case definition is possible aswell.FeaturesTo make work easy, the following features are available: Easy configuration through the insertion of graphic elements into the graphicinterface using a drag & drop operation Command and symbol completion while writing Direct transfer of network symbols, environment data, diagnostic symbols, andparameters from the Symbol Explorer Symbol and value type checks while editing Access to user-defined functions and test cases in other languages Usage and re-use of sub-diagrams possible Display and preview of generated test cases and their content in table formUser interfaceFigure 16: Test Diagram EditorNote: The Test Diagram Editor is only available with the option Graphical TestDesign. Vector Informatik GmbHVersion 7- 25 -

Concept Manual vTESTstudio3.5Test Design EditorsState Diagram EditorOverviewThe State Diagram Editor can be used to model the expected behavior of the systemunder test as state model. Test code in tabular notation is located behind eachgraphical element. Based on transition coverage test cases are automaticallygenerated out of the model. Different generation algorithms are supported, e.g.Chinese Postman algorithm and a breadth search based algorithm.FeaturesTo make work easy, the following features are available: Easy configuration through the insertion of graphic elements into the graphicinterface using a drag & drop operation Command and symbol completion while writing Direct transfer of network symbols, environment data, diagnostic symbols, andparameters from the Symbol Explorer Symbol and value type checks while editing Access to user-defined functions and test cases in other languages Display and preview of generated test cases and their content in table formUser interfaceFigure 17: State Diagram EditorNote: The State Diagram Editor is only available with the option Graphical TestDesign. Vector Informatik GmbHVersion 7- 26 -

Concept Manual vTESTstudioInteraction with CANoe4 Interaction with CANoeIn this chapter you find the following information:4.1CANoe System Environmentpage 284.2Execution in CANoepage 304.3Reportingpage 32 Vector Informatik GmbHVersion 7- 27 -

Concept Manual vTESTstudio4.1AccessInteraction with CANoeCANoe System EnvironmentThe integration of description files for the system environment (databases, diagnosticdescriptions ) enables easy direct access to symbols of the CANoe systemenvironment. The database symbols, system variables, etc., contained in the systemenvironment are available for use in the test coding. The symbols can be inserted intothe test sequences in two different ways: via text completion in the individual editorsor using a drag & drop operation from the Symbol Explorer.Figure 18: Symbol completion in the programming editorsFigure 19: Symbol completion in the Test Table Editor Vector Informatik GmbHVersion 7- 28 -

Concept Manual vTESTstudioInteraction with CANoeFigure 20: Symbol Explorer for inserting symbols using drag & drop Vector Informatik GmbHVersion 7- 29 -

Concept Manual vTESTstudio4.2Interaction with CANoeExecution in CANoeCreating a test unitIn vTESTstudio an executable test unit can be created. An executable test unit hasthe extension *. VTUEXE and contains all necessary data for the test (source files,parameter files ).Configuring andexecuting a test unitin CANoeThe executable test unit can be configured and executed in CANoe.For the execution in CANoe in the CANoe configuration any number of testconfigurations can be created. A test configuration can again contain any number ofexecutable test units that will be executed in sequential order.Figure 21: Test execution in CANoe Vector Informatik GmbHVersion 7- 30 -

Concept Manual vTESTstudioTest Trace WindowInteraction with CANoeDetails of the test run are visualized in the Test Trace Window already during the testexecution.Figure 22: Test Trace Window in CANoeDebuggingCANoe also supports debugging of CAPL and C# code that is part of a test unit. Vector Informatik GmbHVersion 7- 31 -

Concept Manual vTESTstudio4.3Interaction with CANoeReportingCANoe Test ReportViewerDuring the execution of a test unit in CANoe a detailed test report is createdautomatically. The CANoe Test Report Viewer supports a lot of filter and groupingfunctionality as well as user defined queries for a comfortable and comprehensiveanalysis of the test report.Figure 23: CANoe Test Report Viewer Vector Informatik GmbHVersion 7- 32 -

Concept Manual vTESTstudioLanguage Interaction5 Language InteractionIn this chapter you find the following information:5.1Interface Functions Vector Informatik GmbHpage 34Version 7- 33 -

Concept Manual vTESTstudio5.1Language InteractionInterface FunctionsOverviewInterface functions allow for functions of one language to be used in another one. Aninterface function can be a test case, a test sequence, a test function, or a simplefunction. Other than the test function the simple function is not represented as a blockin the report.DefinitionsAn interface function can be defined as follows in the respective languages: C#:Attribute [Export] on test cases, test sequences, test functions or simplefunctions. CAPL:Keyword export ahead of test cases, test sequences, test functions or functions. Test Table Editor:Export setting on test cases, test sequences or functions which are defined in thefunctions view.All interface functions which are available within a test unit are displayed in anexplorer.ExplorerFigure 24: Explorer for interface functionsOut of the explorer, the functions can be added to the respective editors using drag &drop. Alternatively the functions can be added to the editors by the use of the textinput completion feature. Vector Informatik GmbHVersion 7- 34 -

Concept Manual vTESTstudioLanguage InteractionLanguage interaction The following language interaction is supported:Defining LanguageCalling LanguageCAPL C# Test Table Test Sequence StateDiagramDiagramCAPL—————C# ———Test Table ——Test Sequence Diagram ——State Diagram —— Vector Informatik GmbHVersion 7- 35 -

Concept Manual vTESTstudioParameters, Curves and Variants6 Parameters, Curves and VariantsIn this chapter you find the following information:6.1ParametersConceptFind Test Case Data by the Classification Tree Methodpage 386.2Curvespage 416.3Variantspage 42 Vector Informatik GmbHVersion 7- 37 -

Concept Manual vTESTstudio6.1Parameters, Curves and VariantsParameters6.1.1 ConceptDefinitionThe ter

2.6 Traceability by the Connection of REQM/TDM Tools 17 2.7 Test Design Documentation 20 3 Test Design Editors 21 3.1 CAPL Editor 22 3.2 C# Editor 23 3.3 Test Table Editor 24 3.4 Test Diagram Editor 25 3.5 State Diagram Editor 26 4 Interaction with CANoe 27 4.1 CANoe System