Home

Klaros-Testmanagement

1. B 2 1 3 2 execute KlarosContext public abstract void execute KlarosContext context This functions gets called by the seam pdf servlet to execute the script Parameters context The event context to provide all needed functions proper ties and objects B 2 2 de verit klaros scripting context B 2 2 1 IKlarosContext Describes the available actions in the scripting context B 2 2 1 1 Synopsis public interface IKlarosContext Public Methods public abstract public abstract public abstract public abstract public abstract public abstract public abstract public abstract public abstract public abstract public abstract void add String name Object value List lt gt executeParameterizedQuery String query List lt gt executeQuery String query KlarosIteration getActivelteration KlarosConfiguration getActiveProjectO String getAttachmentUrl String attachmentId String getAttachmentUrl UUID attachmentId String getBrowsePageUrl KlarosLabeledObject lt gt artifact Locale getLocaleQ Parameter getParameter String name Object getParameterValue String name 326 Model API Reference public abstract String getPrintPageUrl KlarosLabeledObject lt gt artifact public abstract void setLocale Locale locale B 2 2 1 2 add String Object public abstract void add String name Object value Add a new object with the give key to the event conte
2. Test proxy settings Figure 10 27 The Network Tab E Application URL must be set If Klaros Testmanagement is run behind a proxy the Application URL must be set in order to view some images within Klaros Testmanagement properly The Application URL can be set in the Miscellaneous tab of General Settings see Sec tion 10 5 1 Miscellaneous Settings The properties of a proxy are Proxy Host Port No Proxy for Type of Proxy Requires Authentication Username Password The network address or hostname of the proxy server The port that the proxy server is active on A separated list of domains which should bypass the proxy settings Whether the proxy is a HTTP proxy or a SOCKS proxy Whether or not the proxy requires authentication The username to use for username password authentica tion The password to use for username password authentica tion In addition proxy settings can be tested by clicking the sw icon 10 6 4 LDAP enterprise edition dl Feature only available in Klaros Testmanagement Enterprise Edition 180 Configure Note In order to access an LDAP or Active Directory server a rather large set of con figuration parameters is required Your system administrator should be able to help you by providing the correct values Plan TF Execute qa Evaluate E Configure Integration Overview Issue Management E Mail Network LDAP Report Templates
3. getKey UUID getName String getCreator KlarosUser getLast Editor KlarosUser getCreated Date getLast Updated Date isEnabled boolean aslterable Iterables T gt 4 4 B 1 1 46 KlarosNamedEntity This class encapsulates the dynamic properties of a klaros object B 1 1 46 1 Synopsis public abstract class KlarosNamedEntity lt T S extends NamedEntity gt extends KlarosLabeledObject lt T S gt implements IKlarosNamedEntity Public Methods public KlarosUser getAssignee public List lt IKlarosProperty gt getProperties public boolean isDefinedProperty String propertyName Direct known subclasses de verit klaros core model KlarosCategoryTree de ver it klaros core model KlarosIteration de verit klaros core model KlarosJob de ver it klaros core model KlarosRequirementGroup de verit klaros core model KlarosRevi sion de verit klaros core model KlarosSUTImplementation de verit klaros core mod el KlarosTestCaseResult de verit klaros core model KlarosTestCaseStepResult de 292 Model API Reference verit klaros core model KlarosTestEnvironment de verit klaros core model KlarosTest Run de verit klaros core model KlarosTestSuiteResult Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core mo
4. _ e KlarosCategoryNode lt KlarosRequirement KlarosRequirementCategoryTree KlarosRequirementCategoryNode RequirementCategoryNode gt A KlarosRequirementCategoryNode KlarosRequirementCategoryNode wrapped RequirementCategoryNode getReferences List lt KlarosRequirement gt B 1 1 49 2 KlarosRequirementCategoryNode RequirementCategoryNode public KlarosRequirementCategoryNode RequirementCategoryNode wrapped Instantiates a new klaros reduirement category node Parameters wrapped the wrapped class B 1 1 50 KlarosReduirementCategoryTree An category tree for Requirement implementations B 1 1 50 1 Synopsis public final class KlarosRequirementCategoryTree extends KlarosCategoryTree lt KlarosRequirement KlarosRequirementCategoryTree RequirementCategoryTree KlarosRequirementCategoryNode RequirementCategoryNode gt Methods inherited from de verit klaros core model KlarosCategoryTree getDescrip tion getRootNode getShortname 296 Model API Reference Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode not
5. Jobs by User E ID Summary Priority Status Progress Success Due Assignee Arrange Action JOB00008 3 Execution TS00001 Sprint Null y Major InProgress ME MRE 21 11 2015 14 00 ES izj P Zale Y JOBOOOOS Review Requirements a Y Major New MEE il v P 2 apg L E v0800001 5 Execution TS00001 Sprint Null v Major In Progress n A Harald Martens ly P Zale amp New Figure 7 1 The Maintain Jobs Screen The Maintain Jobs page shows all of the jobs defined for the current project Clicking on the table fields allows direct editing of the attributes The leftmost column allows jobs to be selected and bulk actions to be carried out The up permost checkbox is a global select button which allows bulk actions to be carried out for all jobs that match the current search criteria The Action column contains buttons for carrying out actions on individual jobs The icon opens the Job Details Page for the corresponding job described in Section 7 1 5 Job Details The duplicate icon duplicates the corresponding job optionally including its sub jobs The f delete icon removes the corresponding job The icon executes the corresponding job described in Section 7 1 4 Executing a Job The gt icon imports test results if the job references an automated test case Jobs may be viewed on a printer friendly page as described in Section 5 2 6 Print Pages 7 1 1 Bulk Actions Some bulk actions are avail
6. P00012 WebApp ate HE duer Iterations EE E Properties User Defined Copy Objects Access Results Changes Requirements Test Environments Disable anonymous project access aB 10 v Systems under Test HM UserName Full Name Role Project Role Test Cases ma Test Suites peter Peter Dev A Assign the role selected below to the following items Tester Tester Y susan Susan Dev Tester Test Manager v tester Erika Musteri 10 vw Tester Tester v manager Max Mustermann Test Manager Created by John Doe on 11 19 13 2 17 PM Last changed by John Doe on 11 20 13 7 54 PM Y tester2 Lisa Ricardi Tester Add O tester3 Harald Martens Tester Back O testManager Ted Steve Manager Test Manager Add users as Test Manager v OK Apply Cancel Figure 6 6 The Project Access Popup Every project needs at least one test manager A project needs at least one assigned test manager When trying to save a project which has no assigned test manager a warning message will be displayed in the log panel see Section 5 2 4 The Log Panel 6 1 6 5 Results The result tab is further divided into a Test Runs Test Case Results and a Test Suite Results tab showing the test results related to this project as described in Section 5 2 14 Related Test Runs and Results 6 2 Iterations enterprise Feature only available in Klaros Testmanagement Enterprise Edition edition Iterations represent a test
7. l Properties User Defined Copy Objects Access Results Changes Requirements Test Environments Disable anonymous project access M a 10 y M User Name Full Name Role Project Role Systems under Test Test Cases devManager Devon Manager Test Manager TestManager v Test Suites peter Peter Dev Tester Tester v susan Susan Dev Tester Test Manager v tester Erika Mustermann Tester Tester v torsten Torsten Divers Tester Tester v Created by John Doe on 11 19 13 2 17 PM Last changed by John Doe on 11 20 13 7 54 PM Add Back Figure 6 5 The Project Access tab Klaros Testmanagement Enterprise Edition integrates a rights and role system with its user management system see Section 10 3 Users In the Access tab administrators and test managers can assign and change project roles for individual users For example a user which has the global role tester can be assigned to one project as a tester and to another project as a test manager Initially every project can be accessed by every user If at least one tester or test manager has been assigned to a specific project access to this project is restricted for all other users without an assigned role Pressing the Assign button opens up a popup see Figure 6 6 The Project Access Pop up where new users can be added to the project 72 Define Plan e Execute Pl evaluate KN Configure S WebApp a
8. gt Note In contrast to the compliance rate the coverage rate considers only if a test case has been executed at least once in the iteration regardless of the result passed failed error s Health Matrix System under Test Developer local IDE integrated tomcat ad hoc 0 1 D AN 0 1 SNAPSHOT D D i 4 Success 100 Progress 80 Created 2 years ago by Ted Steve Manager Last changea y nours ayu vy sunn Doe Figure 6 11 The Iteration Health Matrix This matrix shows the success and progress rate of this iteration for every combination of test environment and system under test which have been configured for this iteration Both rates are combined to form a weather icon which shows a sun if both the success and progress rate are at 100 percent and a thundery cloud if both rates are below a ceratin 76 Define level Moving the mouse cursor over the weather icon displays the success and progress rate in detail Note Ea There are various gradations inbetween the sun and the thundery cloud which can be used to show the condition of the system under test and test environ mentin this iteration in finer granularity This can be configured via the health matrix on the reports dashboard 6 2 3 2 Iteration Properties This tab Figure 6 12 allows the user to view or change the following attributes of the selected iteration e ID Assigned automatically Name The editable name of the iteration Description A de
9. FP NO HOST C NO 16 Installation If the variable JAVA HOME is not listed press New Otherwise make sure the variable value of JAVA HOME is still correct If the name of the variable is JAVA HOME the value must be the absolute path of the Java JDK You can usually find the JDK in C Program Files Java jdk1 7 _nn where nn is the patch level of the JDK Java JREs can be found in C Program Files Java jre7 Add x86 to C Program Files if you use a 32bit Java on a 64bit operating system which is not recommended for production use T TN EE A Mew User Variable variable name JAY A HOME variable value C Program Files x86 Vavafjdk1 7 0 21 After pressing OK the Java variable is set In the end it should look something like this T Environment Variables User variables For Jim variable Value JAYA HOME C Program Files x86 Javaljdki 7 0 21 mah ommon rogram lest Microsoft Sh TEMF SLLISERPROFILESSIAppDatatLocalTemp TMP SLLISERPROFILESSIAppDatatLocalTemp System variables Fi E variable value CLASSPATH GC Program Files xB amp Javalire llibie ComSpec CA Windows system32icmd exe DEFLOGDIR CProgrambDataiMcAfeslDesktopProtec FP HO H ST Oo NO ES 3 2 2 3 Microsoft Windows To run Klaros Testmanagement on Microsoft Windows operating systems the following re guirements should be met 17 Installation Minimum requirements 2GB RAM 2GHz Single Core CPU s Reco
10. Installation The username and the password of the administrator account for managing the Tomcat server Username admin Password beSureNotToUseThisPassword Retype Password beSureNotToUseThisPassword x Launch Application Server Enter 1 to select 0 to deselect 0 x Launch Browser Enter 1 to select 0 to deselect Q Press 1 to continue 2 to quit 3 to redisplay 1 3 4 7 Step 7 Installation Packages are displayed as soon as they are installed Section 3 3 7 Step 7 Installation Starting to unpack Processing package Tomcat 7 Application Server 1 2 Processing package Klaros Testmanagement 2 2 Unpacking finished 3 4 8 Step 8 Perform External Processes This panel is skipped since we chose not to launch the server or a browser otherwise startup messages of the server could be seen here See Section 3 3 8 Step 8 Perform External Processes on how this is handled in GUI mode 3 4 9 Step 9 Setup Shortcuts In a GUI less environment we do not want any menu entries or icons on desktops thus we choose N See Section 3 3 9 Step 9 Setup Shortcuts for details on shortcut setup in windowed environments Create shortcuts in the Start Menu Enter Y for Yes N for No N 3 4 10 Step 10 Installation Finished The generation of an automatic installation scripts does not work in console mode so please choose N here Section 3 3 10 Step 10 Installation Finished shows how
11. Of course this is not the case To resolve this situation point the KLAROS HOME variable to the correct location and restart 3 7 1 Log Files The log files for Klaros Testmanagement can be found in the logs folder in the installation directory and also in condensed form the logs folder within the klaros directory Attaching the log files from these locations to a bug report helps the support team to quickly identify and fix any problems you encounter 36 Installation 3 7 2 The Hibernate Properties File The Hibernate properties file is located at klaros hibernate properties This file is used to specify the database to use for Klaros Testmanagement It contains the database type URI and the authentication information More information about changing the database can be found in Section 3 9 Changing the Default Database 3 7 3 Language Files Klaros Testmanagement may be customized to add new languages This process is de scribed in Section 4 1 1 Defining Language Files The file used to store the Quote of the Day entries is located at klaros resources quotes txt 3 7 4 The Ouotes File The file used to store the Quote of the Day entries is located at klaros resources quotes txt 3 7 5 The Derby Database If you are using the default Derby database this is located in the klaros KlarosDerby folder 3 7 6 The Attachment Repository All attachments are saved in the klaros repository folder If the Klaro
12. P1 2 3 1 0 0 2 years ago gt P00005 Test GPS Tracking 1 0 3 0 3 2yearsago ZA iterations Requirements TestCases Test Suites Test Runs Created Figure 6 1 The Projects Screen In order to use the test management functions of Klaros Testmanagement the user is re quired to select a project Projects are selected by clicking on the check box of the desired project in the leftmost or rightmost column 2 Choosing a project with the project quick select drop down field The header bar of Klaros Testmanagement contains a drop down field labeled Project With this drop down field the active project can be switched quickly on any Klaros Testmanagement page You will be directed to the top page of your current category Define Execute etc 68 Define If no projects have been created the user must create one before proceeding The process of creating a project is described in the next section After a project is selected the disabled functions in the navigation bar are made available 6 1 1 Creating a Project New projects may be created by clicking the New button Figure 6 1 An empty row is added at the beginning of the table The Project ID is automatically assigned by Klaros Testmanagement and the description can be specified 6 1 2 Deleting a Project When the Delete icon is clicked the project will be locked and removed from the list of selectable projects 00000000 gt Why is the Delete button somet
13. Test Suite Results Issues Figure 9 27 The Test Suite Results Screen Clicking the icon starts a retest of the test suite and clicking the 1 icon opens the Single Test Suite Results page 152 Evaluate 9 6 1 Single Test Suite Results This page shows individual executions of the selected test case The result of each execution is shown as well as the system under test and test environment used Figure 9 28 REN ICO SO Evaluate x Configure oe WebApp Aa B Test Suite Results TS00001 Sprint Null E Dashboard Fiter Sot 10 x ID Start Test Environment System under Test Executor Duration Result Action TSR0000003 11 20 13 8 03 30 PM tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 03 A Q METER TSR0000002 11 20 13 7 55 27 PM tomcat ad hoc 0 2 SNAPSHOT John Doe 8 Q Report Templates Test Run History IET TSRO000001 11 20 13 7 45 11 PM tomcat ad hoc 0 2 SNAPSHOT John Doe O Q Test Suite Results Back Issues Figure 9 28 The Test Suite Results Screen To get a better overview of the test suite results the sorting and filtering functionality of the Filter Sort panel can be used as described in Section 5 2 5 Filtering and Sorting Clicking the 1 opens the Test Suite Result Details page for the corresponding test suite result Figure 9 29 Plan po Execute FI Evaluate X Configure Test Suite Result TS00001 Sprint Null E i Dashboard Fiter Sort 10 f
14. public Set lt KlarosIterationCategoryNode gt getCategories public StateDef getCurrentState public String getDescription public Date getDueDate public Set lt KlarosTestEnvironment gt getEnvs 284 Model API Reference public Set lt KlarosJob gt getJobs public String getShortnameQ public Date getStartDate public String getSuccessCriteria public Set lt KlarosSUTImplementation gt getSutsO public Set lt KlarosTestRun gt getTestRuns public int hashCodeO Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait S Sextends LabeledObject KlarosLabeledObject lt T S gt T j S Sextends NamedEntity Iteration gt l ro KlarosNamedEntity lt Klaroslteratio Klaroslteration getShortname String getDescription String getStartDate Date getDueDate Date getSuccessCriteria String getCurrentState StateDef getbbs Set lt Klarosbb gt getSuts Set lt KlarosSUTImplementation gt getEnvs Set lt KlarosTestEnvironment gt get
15. 193 Custom Reports sp paragraph horizontalAlignment center gt lt p piechart title Testresults direction anticlockwise circular true startAngle 30 labelGap 0 1 labelLinkPaint black plotBackgroundPaint white labelBackgroundPaint white is3D true gt sp series key results gt lt p data key Error f error size value error size sectionPaint FFQAQA gt lt p data key Success success size value success size sectionPaint 33CC00 gt lt p data key Failure failure size value failure size sectionPaint FFCCQQ gt lt p series gt lt p piechart gt lt p paragraph gt The piechart element builds the frame for the chart by defining the main outlook of the chart For detailed information on different charts please check the SeamPDF documenta tion For a pie chart a series of data is required The data is retrieved from the lists stored in the context by the Groovy script lt p data key Error f error size value error size sectionPaint FFQAQA gt This code retrieves the list containing the error results from the context and calls its size method to determine the amount of erroneous test cases The pie chart is then rendered from the three datasections as seen in Figure 11 7 A Pie Chart Example 11 3 4 Including Images This section shows how to include an image into a report Since the report is rendered by Seam the image to be included m
16. Area Functional v Design Technique v O Variety vi Execution Manual v O Priority High vi O state Draft vo Team 2 Level y O Docbase Dependency O Evaluation Traceability O Created by John Doe on 10 29 13 10 35 AM Last changed by John Doe on 11 19 13 11 39 AM Back Figure 6 23 The Edit Test Cases Screen How to create a new revision of a test case Clicking the New Revision button creates a new revision of the test case This button is disabled if there are any unsaved changes to the test case 6 6 3 3 User Defined Properties EN enterprise edition dl Feature only available in Klaros Testmanagement Enterprise Edition User defined properties can be used to customize test cases within Klaros Testmanagement by adding custom fields This process is described in Section 5 2 11 User Defined Proper ties 96 Define 6 6 3 4 Edit Test Steps In the Steps tab Test steps may be added to or removed from the test case The following attributes of single test steps may also be changed Description The description of the action to take e g Enter name and password and click the Login button s Expected Result The visible behavior of the system predicted while carrying out the test step e g The user recieves a message that the login succeeded e Precondition Condition that must be fulfilled before the execution of the test step e g The user is not yet logged in e Postcond
17. Created By admin Assigned To hudson Priority Blocker Status Open System under Test v Add Link Comment Link Back Figure 9 35 The Link Issues Screen Pressing the si icon opens up the issue in the appertaining issue management systems in a new tab Pressing the icon removes the issue from the test case Important This does not delete the issue in the issue management system only the refer ence to the test case in Klaros Testmanagement 158 Evaluate System The issue management system from which issues are to be linked ID The id of the issue to be linked Pressing the i icon searches the issue management system for an issue which matches the entered id Upon a successful search pressing the Link button links the issue to the test case 9 8 Bookmarking Results Klaros Testmanagement allows the bookmarking of test run details test case result details and test suite result details The icon on these pages is a link to the persistent bookmark A Define Plan po Execute gal Evaluate y Configure Issue Management System Integration Test Case Result TCR0000009 TC00001 Testing the file upload of the ticket system amje Dashboard Repor Templates Properties Changes Test Run History Summary The Issue cannot be created Test Case Results Test Suite Results Description The window to putin the issue data does not open therefore no issues can be created Issues
18. Expected Result Pret Database Test Case Step Action Open Menu Precondition Postcondition Expected Result Test Case Step Action Navigate to Firmware Options Precondition Postcondition Expected Result Pos Test Case Step Action Choose Reset Precondition Postcondition Expected Result Save Discard Step 2 Navigate to Firmware Options Description Navigate to Firmware Options Exnartad Daecult Figure 5 16 The Conflict Resolution Dialog 59 Functional Overview For each conflict the user has the choice of saving the artifact with the value they previously Chose or the current value in the database In the case of lists e g the list of test steps in a test case the user has the option to Merge the changes or to use the version which is currently in the database This is to prevent the inadvertent loss of data through the deletion of objects which were added by other users The Merge option builds a list containing all of the elements of both lists user and database in an approximation of the correct order Clicking the Save button persists the chosen changes to the database and clicking the Discard button discards the user s changes 5 2 9 Deleting Objects Many objects in Klaros Testmanagement can be deleted by pressing the icon If the object to be deleted is linked to other objects e g a requirement which is linked to a test case or contained in other objects e g a test case which is i
19. In order to use a bulk action the user must first select one or more objects in the list using the check boxes to the left of the table The buttons above and to the left of the table then become active Figure 5 18 shows the bulk action buttons on the test case list page 60 Functional Overview Revision TC00003 a 10 Figure 5 18 The Bulk Actions on the Test Case List Page Before any bulk action is carried out all changes must be saved A save changes dialog ap pears if a bulk action button is pressed while there are unsaved changes A bulk action confirmation dialog is displayed once a bulk action button has been clicked and any changes have been saved These dialogs describe the action which will be carried out and sometimes contain input fields e g to enter the revision comment for the bulk new revision action All changes are written to the database as soon as this dialog is confirmed 5 2 10 1 Bulk Edit enterprise Feature only available in Klaros Testmanagement Enterprise Edition j edition It is possible to bulk edit objects in Klaros Testmanagement Pressingthe bulk action icon opens up a popup where fields of multiple objects can be edited at once See Figure 5 19 E Define Plan KLS Execute qa Evaluate E Configure WebApp A Users Overview Report Templates Fi Filter Sot 10 v Mobile Devices admin A John Doe doe company
20. String getExecutionTime long getAction String getExpectedResult String getPostcondition String getPrecondition String B 1 1 64 KlarosTestEnvironment This class provides access to the information stored for test environments B 1 1 64 1 Synopsis public final class KlarosTestEnvironment extends KlarosNamedEntity lt KlarosTestEnvironment TestEnvironment gt implements IKlarosTestEnvironment Comparable lt KlarosTestEnvironment gt Public Methods public int compareTo KlarosTestEnvironment o public boolean equals Object o public Set lt KlarosAttachment gt getAttachments public Set lt KlarosTestEnvironmentCategoryNode gt getCategories 311 Model API Reference public String getDescriptionQ public Set lt KlarosIteration gt getIterations public Set lt KlarosTestRun gt getTestRuns public int hashCode Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait Me S Sextends NamedEntity KlarosNamedEntity lt KlarosTestEnvironment TestEnvironment
21. The Java Runtime environment needs to be installed in order to execute applications programmed in the Java programming lan guage JavaScript is a scripting language most often used to add func tionality to web pages Most newer Web browsers can process JavaScript generated code See Java Runtime Environment 210 JIRA Job Jubula JUnit M Manager Mantis O Operating System OS P Postcondition Precondition Project Q QFTest Glossary JIRA is a bug tracking Issue tracking and project management sys tem by Atlassian Software Jobs may consist of the execution of Test Cases Test Suites or any other possible task Jobs can be nested and assigned to individual users The executions and results of jobs can be tracked by Klaros Testmanagement Jubula provides automated functional GUI testing for various types of applications JUnit is a unit testing framework for the Java programming lan guage User role that has access to create edit delete and search for ob jects run test cases and test suites show results and generate re ports Mantis MantisBT Mantis Bug Tracker is an open source bug tracking system An operating system commonly abbreviated to either OS or O S is an interface between hardware and applications It is responsible for the management and coordination of activities and the sharing of the limited resources of the computer Common contemporary operating systems
22. check if the URL is valid the Validate the URL button on the right of the URL field can be pressed If the URL to the issue management system is config ured correctly a confirmation message will be displayed in the message area e Trailing slashes in URLs In case of an authentication error first check whether the addi tion or deletion of a trailing slash resolves the issue Action The action column contains a button that can be used to delete an system from the configuration If the issue management system is unused i e it is not used in any project the configuration of the system can be deleted Project selection The valid project ID values can be found in the issue management systems at the following locations Bugzilla Project ID The Bugzilla Project ID consists of the Product field value as shown below Bugzilla Select product in classification Unclassified Home New Search i Find Reports Preferences Administration Help Log out admin verit de TestPraduct gt This is a test product This ought to be blown away and replaced with real stuff in a finished installation of bugzilla Redisplay table with bug counts slower Add a product to classification Unclassified Edit classification Unclassified Figure 10 22 The Bugzilla Project ID JIRA Project ID The JIRA Project ID consists of the Key field value as shown below 176 Configure PENT Dashboards Projec
23. duirements Klaros Testmanagement Enterprise Edition can authenti Cate users against an external LDAP Active Directory sys tem which contains the passwords of the users Klaros Testmanagement Enterprise Edition enables the quick export of data tables in excel format in order to un dertake further processing on demand All important test data in Klaros Testmanagement Enter prise Edition can be displayed on printer friendly pages Klaros Testmanagement Enterprise Edition enables bulk actions on objects on list pages Multiple objects may be deleted duplicated revisioned or displayed on a printer friendly page by selecting them and clicking a bulk action button 1 3 Klaros Testmanagement Mobile Edition Features mobile edition pr Additional features of Klaros Testmanagement Mobile Edition Mobile Test Execution Pausable Test Cases Extended Recording of Test Results Network Independence With Klaros Testmanagement Mobile Edition it is possible to execute manual tests on site making use of the extra input facilities of a modern mobile device smartphone or tablet Klaros Testmanagement Mobile Edition allows pausing and resuming of tests Klaros Testmanagement Mobile Edition can also use the sensors on a mobile device to record test results i e the camera microphone GPS The information captured with these sensors is linked to the test results and automatically saved on the server Klaros Testmanagement
24. lt print the frontpage gt lt p paragraph alignment center spacingAfter 100 gt lt p text value gt lt p paragraph gt lt p font style bold size 32 gt lt p paragraph alignment center spacingAfter 75 gt lt p text value Test Case Report gt lt p paragraph gt lt p font gt lt p font style normal size 12 gt lt p paragraph alignment center spacingAfter 5 gt lt p text value Created by gt lt p paragraph gt lt p font gt lt p font style bold size 16 gt lt p paragraph alignment center spacingAfter 5 gt lt p text value user name user email gt lt p paragraph gt lt p font gt lt p font style normal size 12 gt lt p paragraph alignment center spacingAfter 5 gt lt p text value at gt lt p paragraph gt lt p font gt lt p font style bold size 16 gt lt p paragraph alignment center spacingAfter 75 gt lt p text value datej gt lt p paragraph gt lt p font gt lt p newPage gt sui fragment rendered results null gt lt p font style normal size 12 gt lt p paragraph alignment left spacingAfter 10 gt lt p text value The testresults for gt lt p paragraph gt lt p font lt ui fragment lt Testresult table gt lt p table columns 4 widths 1 1 3 3 gt lt create the headline with bold characters gt lt p font size 10 style bold gt lt p ce
25. lt p text value date gt Note ZA user name and user username contain different values The first provides the user s real name while the latter provides the name the user is logged in with E 2 KlarosScript Interface package de verit klaros scripting VES Public interface that all seam pdf template scripts must implement be work properly public interface KlarosScript 1 VES This functions gets called by the seam pdf servlet to execute the script param context The event context to provide all needed functions properties and objects void execute KlarosContext context E 3 Example report template lt p document xmlns ui http java sun com jsf facelets xmlns f http java sun com jsf core xmlns p http jboss org schema seam pdf title Klaros Testmanagement Test Suite Report marginMirroring true author user name creator fuser name pageSize A4 gt 355 Reporting Resources lt f facet name header gt lt p font size 8 gt lt p header borderWidthBottom 0 1 borderColorBottom black borderWidthTop 0 alignment center gt lt p text value Example report generated date by user name gt lt p header gt lt p footer borderWidthTop 0 1 borderColorTop black borderWidthBottom 0 alignment center gt lt p text value Page gt lt p pageNumber gt lt p footer gt lt p font lt f facet gt
26. public String getChanges public String getDescription public int hashCode 290 Model API Reference Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait KlarosJobUpdateAction getDescription String getChanges String compareTo o KlarosbbUpdateAction int equals o Object boolean hashCode int B 1 1 45 KlarosLabeledObject This class encapsulates the dynamic properties of a klaros object B 1 1 45 1 Synopsis public abstract class KlarosLabeledObject lt T S extends LabeledObject gt extends KlarosWrapper lt T S gt implements IKlarosLabeledObject Public Methods public Iterable lt T gt asIterableQ public Date getCreated public KlarosUser getCreator public UUID getKeyO public KlarosUser getLastEditorO public Date getLastUpdated public String getName public boolean isEnabledO Direct known subclasses de verit klaros core model KlarosConfiguration de verit klaros core model KlarosNamedEntity de verit klaros core model KlarosUser Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 291 Model API Reference MEEN ER Eg T S Sextends LabeledObject KlarosLabeledObject
27. 52 9 Deletind Ob Ea 60 5 2 10 BUK FNS Se 60 5 2 11 User Defined Properties ssc eee de eee 61 IL ZA EN arie T A 63 5215 REVISIONS RR 64 5 2 14 Related Test Runs and Results iss ES rep OR oe de De 64 5215 CHange NON NE 65 52 VO DENN TADS TTT 66 HPS ES E 68 Os PEO SCS epi 68 bl Creating a Project st ee Ee illness 69 612 Beeni PrO Er 69 Vi Klaros Testmanagement User Manual 6 13 RESLOFING a eel SE a 69 6 14 PUTING a Proein lalala 69 6 1 5 Editing the Description of a Project esse ss eee 69 616 PET DES saa ae 69 62 erations PN 73 62 Bulk AN ns EE adds 74 6 22 Creating an eration Leve 74 62 3 erom Details avse 75 SE eUI nR n EE ss RR RR EE EE NE E 79 63 bk BIK AUTOS AN 80 63 2 Creatina d Re duitemer 445 80 6 3 3 Requirement Details Lee 81 6 4 TESE VON EN PS 83 GAl BUNCACIONS tradra 84 6 42 Creatingva Test Sy TR e ne 85 6 4 3 Test Environment Detalls av EN ED E EEA Ed ES 85 ESSENS inder Test EE GE ED Lo 87 6 5 1 Creating System Under Test TT 88 EST BUK ACION es Ee ee TE Ee eee 88 6 5 3 System Under Test Details usina ER NG RE AR RE GE Ge ER aii 88 BL besit ES RE DE GE ie EEE EEE RD NT ier ie 91 66 Bunk ACOSO E N 92 602 Cheating K Jr 93 663 Test Case Detalla ei iia 93 6 7 TESE SUE eee 99 67 1 BIK AUNG 99 64 2 trede Test SUES Ke 100 67 Te Suite Detall va 100 AT EE EER EA OE IN EE ET 104 Jeko MANGEN ODE Ve 104 PAS BUK ANN TTT 104 1 1 2 Great ng JODE ee 105 TS ANNIE GE 105 714 Ex
28. List lt KlarosTestEnvironment gt B 1 1 65 2 KlarosTestEnvironmentCategoryNode TestEnvironmentCategoryNode public KlarosTestEnvironmentCategoryNode TestEnvironmentCategoryNode wrapped Instantiates a new klaros test environment category node Parameters wrapped the wrapped class B 1 1 66 KlarosTestEnvironmentCategoryTree A category node for test environments B 1 1 66 1 Synopsis public final class KlarosTestEnvironmentCategoryTree extends KlarosCategoryTree lt KlarosTestEnvironment KlarosTestEnvironmentCategoryTree TestEnvironmentCategoryTree KlarosTestEnvironmentCategoryNode TestEnvironmentCategoryNode gt Methods inherited from de verit klaros core model KlarosCategoryTree getDescrip tion getRootNode getShortname Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled 313 Model API Reference Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait Object l TT SS extends LabeledObject KlarosLabeledObject lt T S gt i EET S Sextends NamedEntity KlarosNamedEntity lt W P gt I I W W exten
29. Project KLAROS TESTMANAGEMENT P00001 Author Felix Mustermann System Under Test SUTO0001 Date Dec 1 2009 2 29 PM Summary Result History 3 0 25 20 1 8 1 0 0 5 15 Aug 30 Aug 14 Sep 29 Sep 14 Okt 29 Okt 13 Nov 28 Nov Passed Failures Errors Result History Percentage 100 75 50 25 TTT nnn me EN U Gg 15 Aug 30 Aug 14 Sep 29 5ep 14 Okt 29 Okt 13 Nov 28 Nov Passed Failures Errors Test Run Details D anana a i e S se a aa 3 gt MM aen a 8 ra AA Ee MM M5 ie 3 ERC Oi sf EN HS sener bet sein 1 of eo 1 semen 1 of og 1 aus EL 1 af ef 11 ses 1 af ar 1 ro seas 1 ef af 1 ami sesam sf of 1 Lan naa 1 of of 1 R e 1 sf ol 1 Owens peas 3 1 1 ET h ah ah ke h skbl h ah ak h Fage 1 of 1 Figure 9 14 The Test Run History Report Layout 9 4 Test Runs The Test Runs screen allows the user to generate reports for executed test runs Figure 9 15 144 Evaluate Plan e Execute El Evaluate y Configure S Webapp 2 amp D Dashboard Report Templates Test Runs 3 ID Start Test Case Suite Test Environment System under Test Results v IN x Action Test Run History TRU0000044 6 16 14 11 32 29 AM TC00001 Test 0 1 1 a E Q C TRU0000043 6 16 14 11 30 55 AM TC00003 Test 0 1 1 nadas Ed N O TRU0000042 11 21 13 1 16 09 PM TC00003 tomcat ad hoc 0 1 1 EN aaa ELE EER C TRUO0000041 11 21 13
30. Requirements 0 TestEnvir ENV00003 Windows XP SP1 ENV00004 Windows XP Test Cases Test Suites 70 v 1500001 1 0 HO 2 Selected 3 test environments 1 SL Test Cases ID Revision Mame Traceability Execution Steps TC00002 1 0 Automated 0 Created by Felix Mustermann on 7 23 14 1 TC00001 1 0 Install XyPlanner Manual 5 Last changed by Felix Mustermann on 7 23 14 10 17 AM Test Suites Back COI Nae Test Cases TS00001 1 0 2 Do you want to copy these objects to this project Keep test case states e g DrafVApproved Yes No Figure 6 4 Copying Objects from another Project Checking the Keep test case states checkbox keeps the state of all test cases while copying Unchecking this checkbox sets all test case states to Droft Note When copying a test suite all test cases that are part of this test suite are also being copied 71 Define 6 1 6 4 Securing access to the Project A project can be secured by checking the Disable anonymous project access flag If this flag is checked a user must be logged into Klaros Testmanagement to view bookmarked pages More information about bookmarking is available at Section 9 8 Bookmarking Results 6 1 6 4 1 Assigning Project specific Roles eden Feature only available in Klaros Testmanagement Enterprise Edition edition _d EZ Define Plan Execute pi Evaluate X Configure WebApp 2 L P00012 WebApp a lterations
31. Result A v Failure Start 11 19 13 3 13 54 PM Executor John Doe Execution time 00 01 28 Second s Test Run TRU0000009 11 19 13 3 13 54 PM TestCase TC00001 Testing the file upload of the ticket system Test Environment ENV00002 OpenBSD 5 3 System under Test SUT00001 Ticket System v1 56 Steps Number Action Result Summary Description Action 1 Log into the ticket system O 2 2 Press the button Create new Ticket O EA 3 Press the button Attach file to ticket A The window doesn t open The window to put in the issue data does not open 2 4 Select the file testzip for uploading and press OK O a 5 Press the button Save Ticket Fi Upload Attachment Back Figure 9 36 The Test Case Results Screen Section 6 1 6 1 Editing the Issue Management Systems in a Project explains the configu ration of controlling access to bookmarked pages in the related project 159 Chapter 10 Configure The Configure section provides administrative functions like managing custom reports cre ating and editing user accounts changing application settings configuring remote system parameters and backing up and restoring projects 10 1 Overview The main page of the Configure section is the Overview page This page contains information about the operating system Java runtime environment memory usage and some additional information about the system as shown in Figure 10 1 E Define e Plan TF Execute pm Evalua
32. The import interface consists of a simple REST interface which can be accessed by command line tools as well as custom applications This is further detailed in Section 12 1 3 Execu tion 12 1 1 Import Format The Excel sheet used to import test cases has to follow this strict format 1 Each test case is located on a separate sheet 2 Each sheet is divided into three sections general properties test case steps and custom properties A B c D E F 1 ID TCODOS1 Cycle Major Regression Name Test Login an Tests Revision 1 0 lt General Properties wate gory 3 4 5 Description Check the basic login functionality 6 Precondition Server installed 7 8 a Postcondition User is logged in Expected Result 10 Note Do not skip this 11 Area REGRESSION 12 Design Method BLACK BOX 13 Variety NEGATIVE 14 Execution MANUAL 15 Priority MEDIUM 17 Team QA Test Steps 18 Level COMPONENT 19 Document Base Requirements Document 1 5 12 7 2011 20 Dependency 21 Evaluation MANUAL 22 Traceability UC 112 23 24 25 Step Action Precondition Postcondition Expected Result 26 1 Open login page Login page displayed 27 2 Enter username 28 3 Enter password Password should not be visible 29 4 Press ok User is lagged in Figure 12 1 Test Case Excel Sheet Sample 196 Import Export 12 1 1 1 General Properties The table below lists the cell coordin
33. a user account The Manager Tester and Guest roles can also be assigned to users on a per project basis providing a project based security scheme Detailed information about the role permissions can be found in Appendix A 2 10 Overview of Artifacts System under Test m me sd a a ad a Figure 2 6 Artifacts Overview 2 11 Issue Management Systems Klaros Testmanagement can be integrated with issue tracking systems like Aflassian Jira Bugzilla and many more see Section 12 5 If an error of the system under test is detected in one of the test case steps the user can easily create an entry in the issue tracking system from within Klaros Testmanagement which is automatically linked and tracked inside both systems Chapter 3 Installation Klaros Testmanagement is equipped with an installer for Microsoft Windows and Lin ux based operating systems Excluding a Java Runtime Environment which is needed for the application and the installer itself it will install all of the applications necessary to run Klaros Testmanagement including a file based database Apache Derby and an Apache Tomcat application server ES Warning The installer configures Klaros Testmanagement to use the Apache Derby data base for persistence which is not intended for production use For produc tion systems it is strongly recommended to use a database like MySQL Post greSQL SQL Server or Oracle Database which will provide significantly be
34. criteria Systems under Test may be viewed on a printer friendly page as described in Section 5 2 6 Print Pages as well as categorized as described in Section 5 2 7 Categorization 6 5 1 Creating a System under Test New systems under test may be created by clicking on the New button Figure 6 18 The system under test ID is automatically assigned by Klaros Testmanagement and the ver sion can be specified by the user The system under test is created in the currently selected project Clicking on the delete icon removes the system under test 00000000 gt Why isthe Delete button disabled Systems under test which are already referenced by test runs cannot be deleted so their delete icon is disabled Clicking on the edit icon displays the details page of the system under test 6 5 2 Bulk Actions Ka enterprise Feature only available in Klaros Testmanagement Enterprise Edition 7 edition Some bulk actions are available on the Systems under Test page Bulk actions are described in Section 5 2 10 Bulk Actions The bulk actions available on this page are Edit Print Delete and Assign to category The bulk action buttons can be found above the table on the left 6 5 3 System under Test Details This section allows in depth editing of an individual system under test including user de fined properties The executed test results and change history for the system under test are also visible in
35. e g the execution of tests which can be assigned to individual users and tracked accord ingly This section is only available in Klaros Testmanage ment Enterprise Edition and Klaros Testmanagement Mo bile Edition Execute The Execute section of Klaros Testmanagement allows ex ecution of jobs manual test cases and manual test suites Before a test is executed the tester must select a com bination of system under test and test environment for which he executes the test He is then guided step by step through the manual test Comments can be added at each step Functional Overview If the tester is interrupted during the execution of a long test suite he can stop execution at any time and continue the test suite execution later Evaluate The Evaluate section provides all functionality for analyz ing the project It provides coarse overview reports in the dashboard as well as fine grained information so that each execution of a test can be traced and visualized Configure The Configure section contains access to administrative tasks e g the system settings user management or the import and export of projects The following chapters will describe each category in detail 5 2 Main Functions This section describes the use of some common features of Klaros Testmanagement 5 2 1 The Help Menu System Integration L D Documentation Tutorial Message Boards Fl Contact Support T T 1 I i 44 140143 47 OM
36. header borderWidthBottom 0 1 borderColorBottom black borderWidthTop 0 alignment center gt lt p text value Example report generated date by user name gt lt p header gt lt p footer borderWidthTop 0 1 borderColorTop black borderWidthBottom 0 alignment center gt lt p text value Page gt lt p pageNumber gt lt p footer gt lt p font lt f facet gt Next the front page for the report should be defined to provide a short summary of the report To keep this example short only a fragment is presented For the complete script please see Section E 3 Example report template lt p font style bold size 16 gt lt p paragraph alignment center spacingAfter 5 gt lt p text value user name user email gt lt p paragraph gt lt p font gt The snippet shows how to insert the user s email address which opens the email client when clicked 11 3 3 Creating a Chart To provide a graphical overview it is sometimes necessary to add a chart to the report The required data can be prepared by the Groovy script and stored in the context Then the 192 Custom Reports report template can pass the data to the charting component of SeamPDF This section ex plains how to create a chart as shown in Figure 11 7 A Pie Chart Example Testresults Figure 11 7 A Pie Chart Example 11 3 3 1 Pie Chart Groovy Script As mentioned before the Groovy script is no
37. j KlarosTestEnvironment getTestRuns Set lt KlarosTestRun gt getDescription String getCategories Set lt KlarosTestEnvironmentCategoryNode gt compareTo o KlarosTestEnvironment int equals o Object boolean hashCode int getlterations Set lt Klaroslteration gt getAttachments Set lt KlarosAttachment gt B 1 1 65 KlarosTestEnvironmentCategoryNode A category node for test environments B 1 1 65 1 Synopsis public final class KlarosTestEnvironmentCategoryNode extends KlarosCategoryNode lt KlarosTestEnvironment KlarosTestEnvironmentCategoryTree KlarosTestEnvironmentCategoryNode TestEnvironmentCategoryNode gt Public Constructors public KlarosTestEnvironmentCategoryNode TestEnvironmentCategoryNode wrapped 312 Model API Reference Public Methods public List lt KlarosTestEnvironment gt getReferences Methods inherited from de verit klaros core model KlarosCategoryNode getCatego ryTree getDescription getParent getShortname getSubCategories Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait T I extends KlarosCategoryNode lt l T W P gt de RE Pe VERE dtedoryNod KlarosTestEnvironmentCategoryNode KlarosTestEnvironmentCategoryNode wrapped TestEnvironmentCategoryNode getReferences
38. lt OOOO MO b D nN GGG k O02 00 0 C OOOO O k O OOO GOGO k GO 0000909 oa Figure 9 2 The Test Environment Overview Report Layout e SUT Overview The SUT Overview report shows the test runs that have been executed for a system under test containing the execution date and quantity of success failure and error results An example of the report is shown in Figure 9 3 135 Evaluate Y klaros System Under Test Overview Y klaros Project KLAROS TESTMANAGEMENT POOOO1 Author Felix Mustermann Systems Under Test 5 Date Dec 1 2009 2 32 PM Name SUTO00001 Version KLAROS 1 0 Created by Felix Mustermann Test Runs Execution Date Executed by Passed Failure E TRUO00001 Aug 7 2009 10 43 AM Felix Mustermann 1 0 0 TRU00002 Aug 7 2009 10 43 AM Felix Mustermann 1 0 0 TRU00003 Aug 7 2009 10 44 AM Felix Mustermann 0 0 1 TRUO0004 Aug 7 2009 11 03 AM Felix Mustermann 3 0 1 TRUOODOS Dec 1 2009 1 19 PM Felix Mustermann 1 0 0 TRUOODO6 Dec 1 2009 1 25 PM Felix Mustermann 1 0 0 TRU00007 Dec 1 2009 1 28 PM Felix Mustermann 1 0 0 TRU00008 Dec 1 2009 1 28 PM Felix Mustermann 1 0 0 TRUOODO9 Dec 1 2009 1 31 PM Felix Mustermann 1 0 0 TRUOOD10 Dec 1 2009 1 31 PM Felix Mustermann 1 0 0 TRUOOD11 Dec 1 2009 1 41 PM Felix Mustermann 1 0 0 TRUO0012 Dec 1 2009 1 41 PM Felix Mustermann 1 0 0 TRUOOD13 Dec 1 2009 1 45 PM Felix Mustermann 1 0 0 TRUOOD14 Dec 1 2009 2 17 PM Felix Mustermann 1 0 0 TRUOOD15 Dec 1 2009 2 23 PM Felix Mustermann 3 1 1 Name SUT0
39. lt e worksheet name user name value testCases var testCase gt lt e worksheet gt lt e workbook gt Note the usage of the de veritklaros core model KlarosUser and the de verit klaros core model KlarosTestCase parameter from the context user name and testCases A worksheet uses a list of objects to generate the rows and columns of the excel sheet This list must be passed to the value attribute of the worksheet tag In the var attribute the name of the current object can be defined For example To use the test case name of the current object inside the worksheet block the statement testCase name must be used It is also possible to use multiple worksheet tags in one template In this example we have only one worksheet with the user name as worksheet name 195 Chapter 12 Import Export Klaros Testmanagement provides several interfaces to import data from other tools and export its data into several formats 12 1 Importing Test Cases from Excel Klaros Testmanagement allows importing of test cases from Excel sheets structured in 2 predefined format which will be further detailed in Section 12 1 1 Import Format In addition to the standard fields provided for test cases users of the Klaros Testmanage ment Enterprise Edition are also able to import data for user defined fields For this it is nec essary to prepare the project according to what is listed in Section 12 1 2 Prerequisites
40. public abstract String getDescription The description of this test case Parameters return The description B 1 1 21 9 getDesignTechnique public abstract TestDesignTechnique getDesignTechnique The design technique of this test case Parameters return The type B 1 1 21 10 getDetectedIssues public abstract List lt KlarosIssue gt getDetectedIssues Get detected issues Parameters return List of issues which have been detected by this test case revision B 1 1 21 11 getDocbase public abstract String getDocbase The docbase of this test case Parameters return The docbase B 1 1 21 12 getEvaluation public abstract String getEvaluation The evaluation of this test case Parameters return The evaluation B 1 1 21 13 getExecution public abstract TestExecutionMethod getExecution The execution method of this test case Parameters return The execution method 254 Model API Reference B 1 1 21 14 getExpectedResult public abstract String getExpectedResult The expected result of this test case Parameters return The expected result B 1 1 21 15 getExternalNames public abstract Set lt String gt getExternalNames Gets the external test case names this test case is associated with External test case names are used to match imported test case result to existing test cases Parameters return the external names B 1 1 21 16 getImplementation public a
41. public int hashCodeO public Boolean isSecured Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait wee ee ee ee eee EE TT S S extends LabeledObject KlarosLabeledObject lt KlarosConfiguration Configuration gt KlarosConfiguration getDescription String getTestCases Set lt KlarosTestCase gt getRequirements Set lt KlarosRequirement gt getTestRuns Set lt KlarosTest Run gt getSuts Set lt KlarosSUTImplementation gt getEnvs Set lt KlarosTestEnvironment gt getTestSuites Set lt KlarosTestSuite gt getJobs Set lt Klarosbb gt getlterations Set lt Klaroslteration isSecured Boolean compareTo o KlarosConfiguration int equals o Object boolean hashCode int getlterationCategoryTrees Set lt KlaroslterationCategoryTree gt getRequirementCategoryTrees Set lt KlarosRequirementCategoryTree gt getTestCaseCategoryTrees Set lt KlarosTest CaseCategoryTree gt getTestSuiteCategoryTrees Set lt KlarosTestSuiteCategoryTree gt getTestEnvironmentCategoryTrees Set lt KlarosTestEnvironmentCategoryTree gt getSystemUnderTes
42. public void addResult String verdict KlarosTestCaseResult testResult Map lt String List lt KlarosTestCaseResult gt gt resultMap public void execute KlarosContext context public String getColordint index public List lt gt getConverter Set lt gt testrun public String getDate Date d public String getTestCase KlarosTestRun testrun Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait lterationsReport ex ecute context KlarosContext void addResult verdict String testResult KlarosTestCaseResult resultMap Maps String List lt KlarosTestCaseResult gt gt void getColor index int String getConverter testrun Set lt gt List lt gt getDate d Date String getTestCase testrun KlarosTestRun String B 2 3 1 2 addResult String KlarosTestCaseResult Map lt String List lt KlarosTestCaseResult gt gt public void addResult String verdict KlarosTestCaseResult testResult Map lt String List lt KlarosTestCaseResult gt gt resultMap Adds the result to the results map Parameters verdict the verdict of the result testResult the test result resultMap the result map B 2 3 1 3 getColor int public String getColordint index 331 Model API Reference Gets the color Parameters index the index return the color B 2 3 1 4 getConverter Set lt gt public List lt gt getConverter Set lt gt testrun Gets the conve
43. 1 Editing the Issue Management Sys tems in a Project contains instructions on how to add an issue management system to a project By default the system uses the credentials entered at the login screen to authenticate the user against the issue management system In a Bugzilla issue management system the email password combination of the user is tried as well as this is the common case for a login name here If the credentials entered at login do not work and the issue management system has not yet been used during the session Klaros Testmanagement will request new authentication information in a dialog window Pressing the s icon opens up the external issue management system in a new tab After the desired issue management system has been selected a list of issue fields is shown The exact number and naming of those fields varies depending on the type and configura tion of the issue management system Mandatory fields are shaded in a different color to emphasize their importance I Note gt All mandatory fields need to be filled otherwise the issue cannot be saved Issue Fields for every Issue Management System Test Case The test case with which the issue should be linked e System under Test The system under test with which the issue should be linked Update Test Case State Selecting this checkbox opens up a new dropdown list in which the new state of the linked test case can be selected 9 7 2 1
44. 12 5 2 1 Jenkins Hudson Plugin for Klaros Testmanagement This plugin integrates a continuous integration server with Klaros Testmanagement by pub lishing the test results of a Jenkins Hudson build to the Klaros Testmanagement application The test results will be stored in the Klaros Testmanagement database for further evalua tion and reporting purposes You can find the installation and configuration guide for the plugin in the Jenkins Wiki or Hudson Wiki 207 Import Export 12 6 Exporting Table Content to Excel enterprise T j edition Feature only available in Klaros Testmanagement Enterprise Edition With Klaros Testmanagement it is possible to export the content of all tables to an Excel file The current filter and sort settings will be considered Plan Execute Fi Evaluate Configure Issue Management System Inte A Projects Iterations Requirements Description Test Cases Test Suites Test Runs Created Action Test Environments gt P00005 Test GPS Tracking 3 0 3 1118135 24PM 28 Systems under Test gt P00004 Bestellprozess 2 1 0 11 18 13 5 24PM 2 B Test Cases s P00003 Issue Management System Integration 1 0 0 11 18 13 5 24PM e 2 a Test Suites gt P00002 Testing the email client 1 0 0 11 18 13 5 24PM O 2 E gt P00001 Einrichten des neuen Rechenzentrums 2 1 0 11 18 13 5 24PM 2 Description TestCases Test Suites TestRuns Created Action Figure 12 3 Export Table Co
45. 13 isPassed public abstract boolean isPassed Check if this is a result of a passed test case It is assumed that passed results have a prop erty testCasePassed with value true Parameters return true if this results represents an error 260 Model API Reference B 1 1 22 14 isPending public abstract boolean isPending Checks if the test case result is pending This means that it has not yet been completely executed Parameters return true if the test case result is pending B 1 1 22 15 isSkipped public abstract boolean isSkippedO Check if this is a skipped result It is assumed that skipped results have a property type with the value S or skipped Parameters return true if this results represents a skipped result B 1 1 23 IKlarosTestCaseState This interface provides access to data of a test case state B 1 1 23 1 Synopsis public interface IKlarosTestCaseState Public Methods public abstract String getStateDescription public abstract String getStateNameO public abstract KlarosSUTImplementation get Sut 1 public abstract KlarosTestCase getTestCase B 1 1 23 2 getStateDescription public abstract String getStateDescription Get description of state Parameters return The description of this state 261 Model API Reference B 1 1 23 3 getStateName public abstract String getStateNameO Get name of state Parameters return The nam
46. 17 Redmine Authentication Section 43 Installation Settings General Display Authentication Projects Issue tracking Email notifications Authentication required Autologin disabled Self registration manual account activation Allow users to delete their own account Minimum password length 4 Lost password Allow OpenID login and registration F Enable REST web service Enable JSONP support F Session expiration Session maximum lifetime disabled Session inactivity timeout disabled Warning changing these settings may expire the current sessions including yours Save Figure 3 17 Redmine Authentication Section The following combinations have been successfully tested Redmine 1 0 4 Redmine Redmine Mylyn Connector WS API Plugin 2 7 Redmine 1 2 Redmine Redmine Mylyn Connector WS API Plugin 2 7 4 stable Redmine 2 1 Redmine Redmine Mylyn Connector WS API Plugin 2 8 2 stable Redmine 2 3 Redmine Redmine Mylyn Connector WS API Plugin 2 8 2 stable Redmine 2 5 Redmine Redmine Mylyn Connector WS API Plugin 2 8 2 stable Redmine 3 0 Redmine Redmine Mylyn Connector WS API Plugin 2 8 2 master Later versions are expected to work but are currently not tested 3 12 3 Trac Server Configuration The Klaros Testmanagement Trac integration requires the installation of the TracXMLRPC Plugin The download archives and installation notes are available at http trac hacks org wiki Xm
47. 4 Report Details Further information about creating user defined reports is available in Section 11 1 Create A New Report Template 10 3 Users The Users section is used to create and edit Klaros Testmanagement user accounts The Maintain Users page gives the user an overview of the user accounts in Klaros Testman agement The accounts can be created enabled disabled and edited here Figure 10 5 Only users with an Administrator role can edit all accounts others are only able to edit their own account settings User accounts can be viewed on a printer friendly page as described in Section 5 2 6 Print Pages Changing User Roles Users can not change their own System Account flag or Role 162 Overview Report Templates Mobile Devices System Integration Backup admin devManager manager peter susan system tester tester2 tester3 User Name Configure Full Name A John Doe Devon Manager N Max Mustermann Peter Dev Susan Dev System Account Erika Mustermann PP Lisa Ricardi Harald Martens E Mail doe company com max mustermann company com erika mustermann company com ricardi mustermann com martens mustermann com Fiter Sort El 10 v Administrator 2 E Test Manager w 2 3 Test Manager v TZ E Tester v FE Tester vl FE Tester v FE Tester vi 2 E Tester v ZA Tester v FE zee ca 12 Eleme
48. Back Report Templates ers Properties Project Roles Results Connection Log Changes 10 Mobile Devices Fiter Sort El 1D Description v System Role P00005 Test GPS Tracking Tester v ra Integration Test Manager v P00011 P2 Backup C P00012 WebApp Tester v ID Description Created by John Doe on 11 19 13 10 31 AM Last changed by John Doe on 11 19 13 10 31 AM Back Figure 10 8 The Project Roles Tab Pressing the Assign button opens up a popup window with a list of all projects with project specific roles that the user isn t assigned to yet Pressingthe Ok button assigns the user to the selected projects 165 Configure AE e Plan TF Execute BA evaluate Sprint 1 Test GPS Trackng A L amp Max Mustermann a Overview Back Report Templates users Properties Project Roles Results Connection Log Changes Mobile Devices a Filter Sort El 10 v System E ID Description Role Integration J P00011 P2 Test Manager v ID Description Created by John Doe on 11 19 13 10 31 AM A Assign the role selected below to the following items Backup Last changed by John Doe on 11 19 13 10 31 AM Add Back 10 v i espa C P00012 WebApp P00005 Test GPS Tracking Add users as Tester v OK Cancel Figure 10 9 The Project Roles Tab 10 3 3 3 Connection Log Only available in Klaros Testmanagement Mobile Edition The Connection Log tab displays the conne
49. By Changed Action Test Run Overview Report 1 0 Lists the Test Runs in a project grouped by selectable parameters admin 11 12 13 5 12 PM 2 em Iteration PDF Overview Report 1 0 Lists a defined Iteration in a Project admin 1112135 12PM 8 2 TEN Job Excel Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12PM E 2 System Job PDF Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12PM B 2 IIEEE 829 Testrun Deviation Report Template v1 10 IIEEE 829 Testrun Deviation Report Template v1 admin 11 12 13 5 12PM 8 2 gasar IEEE 829 Test Plan Template v1 1 0 IEEE 829 Test Plan Template v1 admin 11 12 13 5 12PM 8 2 Pos IEEE 829 Test Case Specification Template v1 1 0 IEEE 829 Test Case Specification Template v1 admin 11 12 13 5 12 PM 2 0 Elements found Page 1 of 1 1 10 w New Figure 10 2 User Defined Report Template Page 160 Configure If the user defined report is parameterized all needed parameters must be entered in order to generate the report E Define Plan X Execute L Evaluate E Test GPS Tracking L Report Templates T Name Revision Description Changed By Changed Action Report Templates Test Run Overview Report 1 0 Lists the Test Runs in a project grouped by selectable parameters admin 11 12 13 5 12PM B EZ Users Iteration PDF Overview Report 1 0 Lists a defined Iteration in a Project admi
50. Execution Steps Action Figure 5 14 The Categorization Tree View This view shows an overview of the category structure The available categories are repre sented as a collapsible tree with the name of each category is shown along with the num 58 Functional Overview ber of objects it contains The description of each category is shown as a tooltip when its name is hovered over with the mouse pointer 5 2 7 3 The Menu View Plan po Execute pil Evaluate y Configure WebApp 2 L Test Cases Projects N Iterations ee Categorization Requirements Accepted w sum All 0 3 Development 3 3 Test Environments p EEUNA G E El Systems under Test Close 2 pr 6 Categories Fiter Sort II 10 v Test Suites Revision Traceability Priority State Execution Steps Action O Tco0003 a 1 0 Continuous Integration check Medium Approved w Manual 2 Mal Tcooo002 a 1 0 Project setup check High Locked w Manual 1 2 BB O Tco0001 8 1 0 IDE check Low y_ Draft vw Manual v 2 al Revision Traceability Execution Steps Action Figure 5 15 The Categorization Menu View This view allows more compact use of the category panel It contains a drop down menu which enables the user to choose any of the available categories through a submenu sys tem 5 2 8 Conflict Handling Klaros Testmanagement allows for conflict resolution in a multi user environment When saving an object Klaros
51. Figure 3 12 Incompatible Installation detected When uninstalling Klaros Testmanagement the Force the deletion of Klaros Testmanagement installation path checkbox needs to be set F IzPack Uninstaller m Figure 3 13 The Uninstaller 3 6 2 Manual Changes Some settings may need manual adjustments when updating Klaros Testmanagement from major revision 3 to 4 e g from 3 8 4 to 4 0 0 3 6 2 1 Derby Dialect If your installation of Klaros Testmanagement uses the embedded Derby database you should change the value of hibernate dialect in lt userhome gt klaros hibernate properties to org hibernate dialect DerbyTenSevenDialect for improved database handling 34 Installation 3 6 2 2 Custom Reports If you created custom reports available with Klaros Testmanagement Enterprise Edition the pdf and excel namespace declaration in the XML root element needs to be adapted for each of them Just replace the old URL http jboss com products seam pdf given in an xmins attribute by http jboss org schema seam pdf and http jboss com products seam excel given in an xmins attribute by http jboss org schema seam excel and press Save For new reports the updated URL is already preset so no further action is required If you miss to change the namespace your document will not be rendered and you will receive the following error message Unexpected runtime exception The rendered document has not been found in the
52. Gets the date Parameters d the d return the date B 2 3 3 6 getDateOnly long public final String getDateOnlydlong d Gets the date only Parameters d the d return the date only B 2 3 3 7 getSortTestRuns List lt gt KlarosContext public final List lt gt getSortTestRuns List lt gt testRuns KlarosContext context 335 Model API Reference Gets the sort test runs Parameters testRuns the test runs context the context return the sort test runs B 2 3 3 8 getTestCaseError KlarosTestCaseResult public final int getTestCaseError KlarosTestCaseResult result Gets the error Parameters result the result return the error B 2 3 3 9 getTestCaseResult KlarosTestCaseResult public final String getTestCaseResult KlarosTestCaseResult result Gets the result Parameters result the result return the result B 2 3 3 10 getTestCaseStepError KlarosTestCaseStepResult public final int getTestCaseStepError KlarosTestCaseStepResult result Gets the error Parameters result the result return the error B 2 3 3 11 getTestCaseStepResult KlarosTestCaseStepResult public final String getTestCaseStepResult KlarosTestCaseStepResult result Gets the result Parameters result the result return the result B 2 4 de verit klaros scripting model B 2 4 1 Parameter 336 Model API Reference The Parameter class encapsulates a report guery parameter B 2 4 1 1 Synopsis public class Para
53. ID Start Test Case Test Run Test Environment System under Test Executor Time Result Details TCR0000016 11 9 13 8 03 30 PM TC00003 TRU0000010 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 A Qa Report Templates Test Run History ELE TCR0000015 11 8 13 8 03 30 PM TC00002 TRU0000010 tomcat ad hoc 0 2 SNAPSHOT JohnDoe 000001 A BQ ESTOS TCR0000014 11 8 13 8 03 30 PM TC00001 TRU0000010 tomcat ad hoc 0 2 SNAPSHOT JohnDoe 000001 Q Test Suite Results Back Issues Figure 9 29 The Test Suite Results Screen Test Results y enterprise 7 edition da Feature only available in Klaros Testmanagement Enterprise Edition This screen can also be viewed as a printer friendly page Figure 9 30 153 Evaluate 7 Test Suite Result TS00005 LadyPurse RC1 for documentation purposes Summary Description Result eror Passed 1 Failure 1 Error 1 Test Case Results ID tcrooooos2 OG Error Timestamp Apr 29 2011 1 27 PM Test Case TCODOD4 Create a subfolder without having a root folder Test Run TRUDODOOS3 Test Environment ENVOOOO2 Windows 7 System Under Test SUTOODOS LadyPurse RC3 Executor Felix Mustermann ID terooooost ZN Failure Timestamp Apr 29 2011 1 27 PM Test Case TC00002 Restore non existing repository Test Run TRUDOODOS3 Test Environment ENVOOOO2 Windows 7 System Under Test SUTOODOS LadyPurse RCS Executor Felix Mustermann ID TCRooooosa passed Timestamp Apr 29 2011 1 2
54. IKlarosProperty Public Methods public abstract String getNameO public abstract String getValueO 238 Model API Reference B 1 1 15 2 getName public abstract String getNameO Gets the property name Parameters return the property name B 1 1 15 3 getValue public abstract String getValueO Gets the property value Parameters return the property value B 1 1 16 IKlarosRequirement This interface provides access to data of a requirement B 1 1 16 1 Synopsis public interface IKlarosRequirement lt T S extends Revision gt extends IKlarosRevision lt T S gt Public Methods public abstract Set lt KlarosAttachment gt getAttachments public abstract Set lt KlarosRequirementCategoryNode gt getCategories public abstract KlarosConfiguration getConfiguration public abstract Set lt KlarosTestCase gt getCoveringTestCases public abstract String getDescription public abstract Set lt String gt getExternalNames public abstract Set lt KlarosIteration gt getIterations public abstract RequirementPriority getPriority public abstract KlarosRequirementGroup getRequirementGroup public abstract String getShortnameO public abstract String getState public abstract String getSummary 239 Model API Reference B 1 1 16 2 getAttachments public abstract Set lt KlarosAttachment gt getAttachmentsO Gets the attachments associated with this requirement Parameters
55. Issue Details Editing an Existing Issue Editing an issue is done inthe same page as creating as Section 9 7 2 Issue Details Creating a new Issue The only difference is that a button New is placed on the lower left section of the page This button serves as a convinience method when creating multiple issues in a row Pressing this button opens up a new Issue Details page in which another issue can be configured 156 Evaluate Q After creating and saving a new issue the New button also appears so that an other issue can be created right away 9 7 2 2 Issues by Test Case Details E Define e Plan ZL Execute pmi Evaluate X Configure Ewa 2 2 J Issues by Test Case TC00017 aa Dashboard Report Templates ID System System under Test Summary Created Created By Assigned To Priority State Action Test Run Histo PLAYGROUND 20859 E im00001 Test 5 26 2015 admin hudson Blocker Open QE Test Runs PLAYGROUND 18870 E imo0001 0 1 SNAPSHOT Importante 12 2 2014 admin hudson Blocker Open 2 Q E Test Case Results PLAYGROUND 4173 EI IM00001 0 2 de 8 23 2010 admin admin Blocker Open ZOE Test Suite Results Figure 9 33 The Issues by Test Case Details Screen The Issues by Test Case Details page shows all issues which are linked to the selected test case Pressing the icon opens up the Section 9 7 2 1 Issue Details Editing an Existing Issue page where the individual fields of the issue can
56. KlarosSUTImplementation sut Get name of the state related to given SUT Parameters sut The related SUT implementation return The name of the state 256 Model API Reference B 1 1 21 26 getStates public abstract Map lt KlarosSUTImplementation KlarosTestCaseState gt getStates Get test case states Parameters return Collection of the states of this test case revision in relation to the different SUT versions B 1 1 21 27 getTeam public abstract String getTeam The team responsible for this test case Parameters return The team B 1 1 21 28 getTestCaseSteps public abstract List lt KlarosTestCaseStep gt getlestCaseStepsO Get test case steps Parameters return list of steps of this test case revision B 1 1 21 29 getTraceability public abstract String getTraceabilityQ The traceability of this test case Parameters return The traceability B 1 1 21 30 getVariety public abstract TestVariety getVarietyQ The variety of this test case Parameters return The variety B 1 1 22 IKlarosTestCaseResult This interface provides access to data of a test case result B 1 1 22 1 Synopsis public interface IKlarosTestCaseResult extends IKlarosNamedEntity Public Methods public abstract Set lt KlarosAttachment gt getAttachments 257 Model API Reference public abstract String getDescription public abstract long getExecutionTimeO public abstract List lt KlarosTestCase
57. Mobile Edition can also be used without an active network connection Tests can be syn chronized with the test management server at a later date Key Features More information can be found in the documentation of the Klaros Testmanagement Mobile Edition Android Client Chapter 2 Introduction 2 1 What is Klaros Testmanagement Klaros Testmanagement is a modern web application which helps you to organize and man age your test process It documents all test relevant data by storing it in a database and gives an overview about the test progress of a project or piece of software at any time A single item of test relevant data will be called Artifact throughout this document The main artifact is called Project It contains all the other artifacts that are needed to define execute and evaluate tests For more details on defining projects see Section 6 1 2 2 Test Cases The Basis of Testing Figure 2 1 Test Case Structure The central artifact of a test project is the Test Case which represents a single test A test case can be executed in an automated or manual fashion An automated test case refers to a piece of software code that gets executed and in return delivers a test result usually in form of a test result file A manual test case contains beside other entries one or more Test Case Steps which hold detailed written instructions and test conditions for the testers executing the test case Precondition Fi
58. Name Description Default Events Projects Action Integration x NS00001 Default Default Authentication Scheme El 0 0 2GB k Backup Name Description Default Events Projects Action Figure 10 16 The Notification Schemes Tab Clicking the New button creates a notification scheme The Name and Description fields can be set here directly If the Default check box is activated this notification scheme will be the default notification scheme which is per default applied to every project By pressingthe Icon the notification edit tab is shown where the notifications and project assignments can be defined Clicking the icon causes the notification scheme to be sced uled for deletion When the Save button is clicked the notification scheme will be saved The Cancel discards the changes made 10 5 2 1 Notification Scheme Settings Figure 10 17 shows the edit options for a notification scheme The list shows the notifications already defined for the notification scheme currently edited For creating a notification the user may individually assign events from a predefined set of available notification events to one or more notification targets user accounts The available notification events are s Job Assigned This event is triggered once a Job is saved with a new assignee Account Created This event is triggered once a user account has been created Account Password Changed This event is triggered once an account password has been ch
59. Parameters return The number of covered test requirements B 1 1 17 9 getNumberReduirements public abstract int getNumberRequirements Get number of test requirements including all descendants test requirements Parameters return The number of overall test requirements B 1 1 17 10 getParent public abstract KlarosRequirementGroup getParent Get the parent of this reduirement group Parameters return The parent reduirement group or null B 1 1 17 11 getRequirements public abstract Set lt KlarosRequirement gt getRequirements Get the related requirements of this requirement group Parameters return Set containing the requirements which belong to this re quirement group B 1 1 18 IKlarosRevision This interface provides access to a revisionable Klaros object B 1 1 18 1 Synopsis public interface IKlarosRevision lt T S extends Revision gt extends IKlarosNamedEntity Public Methods public abstract KlarosRevision lt T S gt getBranchRoot public abstract Set lt KlarosRevision lt T S gt gt getBranches public abstract KlarosRevision lt T S gt getPredecessor public abstract String getRevisionComment public abstract String getRevisionId public abstract KlarosRevision lt T S gt getRoot public abstract KlarosRevision lt T S gt getSuccessor public abstract KlarosRevision lt T S gt getTrunkRoot 245 Model API Reference B 1 1 18 2 getBranches
60. Port 25 Your local port settings may vary from the given defaults Send Test Mail This link sends a test email to verify that your mail server settings are valid Therefore it is required that your user account contains a valid email address Plan e Execute qa Evaluate E Configure Issue Management System Integration 2 Integration Issue Management E Mail Network LDAP Report Templates SMTP Server localhost SMTP Server Port 25 Users Monia Das User Name systemAccount System Password eeeeeee Integration Sender Address system developmen Authentication SMTP v Backup Security 8 None Y SSL TSL gt Send Test Mail Save Discard Figure 10 26 The E Mail Tab Click the Send Test Email link to test if the fields are filled in properly 179 10 6 3 Network Configure Klaros Testmanagement supports the use of HTTP and SOCKS proxies for network connec tions Proxy settings are configured in the Network section of the configure menu The net work page is shown in Figure 10 27 The Network Tab Integration Report Templates Proxy Host Users s Port Mobile Devices No Proxy For System Type of Proxy Requires Authentication Integration Backup Username Password Plan TF Execute qa Evaluate E Configure Issue Management E Mail Issue Management System Integration Network LDAP http 124 1 3 156 proxy 8013 HTTP O socks v
61. Pty Ltd Other names may be trademarks of their respective owners Third party software and licenses This product contains software covered by the following licenses OTN License Agreement OTN This application contains the Oracle JDBC Driver Please read http www oracle com technology index html for more details on JDBC Driver License agreement JDBC Driver and all associated intellectual property rights are retained by Oracle Corporation and or its licensors To use JDBC Driver included this application you need to agree with Oracle Technology Network Development and Distribution License Terms If you don t you can t use this application REDISTRIBUTION LICENSE FOR MICROSOFT JDBC DRIVER 4 0 FOR SQL SERVER OTN This application contains the Microsoft SQLServer JDBC Driver 4 0 Please read http download microsoft com download 0 2 A 02AAE597 3865 456C AE7F 613F99F850A8 license txt for more details on the Microsoft SQLServer JDBC Driver License agreement Microsoft SQLServer JDBC Driver and all associated intellectual property rights are retained by Microsoft and or its licensors To use the Microsoft SQLServer JDBC Driver included this application you need to agree with MICROSOFT JDBC DRIVER 4 0 FOR SQL SERVER MICROSOFT SOFTWARE LICENSE TERMS If you don t you can t use this application Lesser GNU Public License LGPL 2 1 JasperReports This product uses software available under the Apache Software License ASL 2 0 T
62. SE L tester2 Full Name Leon Miller ee Testor Ga tester3 New Password termann com Tester 2 8 Retype new Password E Mail Role Action System Account O O found Page 1 of 2 1 2 gt rr 10 ly Save Cancel P New i Save Discard Figure 10 6 The Save New User Dialog 163 Configure 10 3 2 Deleting a User Clicking the jj icon on the Maintain User Page Figure 10 5 causes the user account to be disabled Only users of role Administrator can see and restore disabled users 10 3 3 User Details This page Figure 10 7 allows the user to edit the following attributes of a user account Full Name The full name of the user User Name The login name of the user E Mail Address The e mail address of the user is used for notification emails If email notifications are U configured see Section 10 3 1 Creating a User and an email address is provided while creating a new user see Section 10 5 2 Notification Settings this user will receive a registration email This email contains the new user s username and password System Account If this flag is set the user is not able to login at the login page and interactively control the application System accounts should be used for automated tasks like importing data Password The password to log in to Klaros Testmanagement Retype Password Confirmation of the password User Role The role of the user which can be Administrator Manager Tester or Gu
63. SNAPSHOT Made with IzPack http izpack org Figure 3 1 Welcome Screen The installation may be aborted by clicking the Quit button Clicking Next proceeds with the installation 3 3 2 Step 2 Information The second step shows information about the product and the revision history listing the fixed issues and the newly added features Figure 3 2 20 Installation Information Step 2 of 10 Please read the following information Release Notes for Klaros Testmanagement version 4 3 2 SNAPSHOT Klaros Testmanagement is an AJAX based web application for the clear and concise management of the quality assurance process in software development projects Klaros Testmanagement supports the collection of test data and the creation and assignment of test plans as well as interfacing with issue management systems and extensive reporting capabilities Open interfaces allow the import of existing data from outside sources such as spreadsheets or other applications An accompanying web client application allows the automated logging and result acquisition of manually executed test cases The comprehensive and up to date database allows the precise deduction of facts about the current status of the software quality at any time Made with IzPack http izpack org Figure 3 2 Information Screen The installation may be aborted by clicking the back to the Welcome step and clicking Next 3 3 3 St
64. SP3 Passed 4 Failure 2 E Error 2 Figure 9 6 The Latest Success Rate Report 9 1 2 3 The Test Activity Report The Test Activity Report shows the count and the results of the test runs for a selected combi nation of system under test and test environment in a selected period of time as a histogram The configurable properties of the report are The name of the report A boolean value indicating that this report always uses the active project Klaros Testman agement Enterprise Edition only Alternatively the fixed project that this report will display A boolean value indicating that this report always uses the active iteration if available Alternatively the fixed iteration that this report will display if available The system under test to display 139 Evaluate The test environment to display The time period in days Latest Test Activity Test Activity Last 200 days for SUT 0 2 SNAPSHOT 6 and Test Environment Solaris 11 2011 11 Results Date Figure 9 7 The Test Activity Report 9 1 2 4 The Project Health Matrix Report EN enterprise edition d Feature only available in Klaros Testmanagement Enterprise Edition The Project Health Matrix Report shows the project health as weather icons for each defined test environment and system under test in a matrix The icons are calculated from the exe cution and success rate in each category which is shown in detail in a
65. Set lt KlarosSUTImplementation gt getSutsO public abstract Set lt KlarosTestRun gt getTestRuns B 1 1 9 2 getAttachments public abstract Set lt KlarosAttachment gt getAttachments Gets the attachments associated with this iteration Parameters return the attachments B 1 1 9 3 getCategories public abstract Set lt KlarosIterationCategoryNode gt getCategories Gets the categories this object belongs to Each category node will belong to a different category tree 229 Model API Reference Parameters return the category nodes B 1 1 9 4 getCurrentState public abstract StateDef getCurrentStateQ Gets the current state Parameters return the current state B 1 1 9 5 getDescription public abstract String getDescription Gets the description Parameters return the description B 1 1 9 6 getDueDate public abstract Date getDueDate Gets the due date Parameters return the due date B 1 1 9 7 getEnvs public abstract Set lt KlarosTestEnvironment gt getEnvs Gets the test environments associated with this iteration Parameters return the test environments B 1 1 9 8 getjobs public abstract Set lt KlarosJob gt getJobs Gets the jobs associated with this iteration Parameters return the jobs B 1 1 9 9 getShortname public abstract String getShortname Gets the short name Parameters return the short name 230 Model API Reference B 1 1 9 10 g
66. String getDependency String getEvaluation String get Traceability String getExpectedResult String getCategories Set lt KlarosTestCaseCategoryNode gt getExternalNames Set lt String gt getAttachments Set lt KlarosAttachment gt 252 Model API Reference B 1 1 21 2 getArea public abstract TestAreatopic getArea The area of this test case Parameters return The area B 1 1 21 3 getAttachments public abstract Set lt KlarosAttachment gt getAttachments Gets the attachments associated with this test case Parameters return the attachments B 1 1 21 4 getCategories public abstract Set lt KlarosTestCaseCategoryNode gt getCategories Gets the categories this object belongs to Each category node will belong to a different category tree Parameters return the category nodes B 1 1 21 5 getConfiguration public abstract KlarosConfiguration getConfiguration Get the project configuration this test case revision belongs to Parameters return The related configuration B 1 1 21 6 getCovers public abstract Set lt KlarosRequirement gt getCovers Get covered requirements Parameters return Set of requirements which are covered by this test case re vision B 1 1 21 7 getDependency public abstract String getDependency The dependency of this test case Parameters return The dependency 253 Model API Reference B 1 1 21 8 getDescription
67. String getNoteO String getPostconditionQ String getPrecondition TestPriority getPriorityO Set lt KlarosTestCaseResult gt getResultsO String getShortnameQ String getState String getStateName KlarosSUTImplementation sut Map lt KlarosSUTImplementation KlarosTestCaseState gt getStates String getleamO List lt KlarosTestCaseStep gt getTestCaseSteps String getTraceabilityQ TestVariety getVariety 251 E E ie N E Model API Reference Interface IKlarosLabeledObject interface IKlarosNamedEntity interface IKlarosRevision lt T S gt interface IKlarosTestCase getConfiguration KlarosConfiguration getimplementation KlarosExternallmplementation getDetectedIssues Lists Klaroslssue gt getCovers Set lt KlarosRequirement gt getResults Set lt KlarosTestCaseResult gt getTestCaseSteps Lists KlarosTestCaseStep gt getStates Maps KlarosSUTImplementation KlarosTestCaseState gt get StateName sut KlarosSUT Implementation String getShortname String getDescription String getPrecondition String getPostcondition String getNote String getArea TestAreatopic getDesignTechnique TestDesignTechnique getExecution TestExecutionMethod get Variety Test Variety getPriority TestPriority getState String getTeam String getLevel TestLevel getDocbase
68. Test Environments Systems under Test Test Cases and Test Suites may be created and edited There is a menu entry on the left hand side for each of these artifact types 6 1 Projects The Projects section allows managing projects in Klaros Testmanagement Projects are col lections of all test artifacts for a given product and the related results and jobs Test artifacts are objects like test cases and test suites When accessing Klaros Testmanagement for the first time it is necessary to create a project to work with To create a new project select the menu entry Projects Figure 6 1 and follow Section 6 1 1 Creating a Project After at least one project has been created users may select one from the table After a successful login the Projects screen is shown It gives the user an overview of the projects stored in the Klaros Testmanagement database Projects may be created removed and updated on this page Figure 6 1 The displayed projects may be filtered and sorted as described in Section 5 2 5 Filtering and Sorting EZ Define Me EG FI Evaluate Configure webapp 7 a Projects Iterations Filter Sot El 5 z Requirements e Description Iterations Requirements TestCases Test Suites Test Runs Created Action Test Environments P00015 1 0 0 0 0 3 months ago ZA Systems under Test P00012 WebApp 5 11 5 3 67 2 years ago D EA a Test Cases P00011 A P2 0 0 2 1 3 2 years ago ab Test Suites P00010
69. Testmanagement attempts to automatically resolve any pos sible conflicts with concurrent changes made by other users Non conflicting changes i e any changes made by other users which do not affect fields which the current user has changed will be merged with no additional user input If there are any conflicting changes i e changes to fields which were also changed in the mean time by another user the Conflict Resolution Dialog will be displayed to allow the user to choose how the conflicts should be resolved Figure 5 16 shows the Conflict Resolution Dialog for a conflicting test case change Plan dj Execute Pl Evaluate Configure mRooooe PO0032 L K Concurrent modification conflict E Y gt Projects G A Your changes are conflicting with concurrent modifications done by other users Please select the data that should finally be stored Discard Back Iterations Properti Description Test that the firmware reset function works User Test Environments Ne Make sure firmware resetis possible Database 2 View Mode Page Size 10 Is Systems under Test EN lt a gt be amp Merge x E E Des Database Test Suites Requirements Test Case Step Action Open Menu Precondition Postcondition Expected Result Test Case Step Action Navigate to Firmware Options Precondition Postcondition Expected Result Test Case Step Action Choose the Reset option Precondition Postcondition
70. active after entering all required parame ters 9 3 Test Run History Report On the test run history screen a report for the test runs using the selected system under test can be generated The report contains a summary with two result history graphics per centage and total number and the details of each test run Figure 9 13 E Define Plan Dl Execute ig Evaluate X Configure issue Management System Integration Aa Test Run History Dashboard Start Date End Date Nov wl 2013 v Nov v 2013 ly Report Templates Test Run History Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa 4 2 Test Runs z 2 3 4 5 6 7 8 9 3 4 5 6 7 8 9 Test Case Results 10 11 12 13 14 15 16 10 11 12 13 14 15 16 Test Suite Results 17 18 el Me 4 2 23 17 18 19 20 21 2 23 Issues 24 25 26 27 28 29 30 24 25 26 27 28 29 3 Time 17 24 Time 15 34 Hour Hour Minute Minute Now Now Choose System under Test Ticket System v1 55 v2 beta v Format ppr lHTML Sl Gav Generate Figure 9 13 The Test Run History Report Klaros Testmanagement can export these test run report in three different file formats 143 Evaluate PDF HTML CSV After selecting the Start Date End Date and System under Test the Generate can be clicked enabling the user to choose their preferred file format in which to download the report see Figure 9 13 The layout of the report is shown in Figure 9 14 j P Y klaros Test Result History Y klaros
71. and the number of completed jobs are displayed at the top of this page A table displays the details of each individual job The action column contains a button which allows the user to execute the Job This process is described in Section 7 1 4 Executing a lob 8 2 Run Test Case Executing a test case consists of running a test on a specific version of the system under test in a selected test environment The Run a Single Test Case page shows all test cases in a list To get a better overview of the available test cases the sorting and filtering functionality of the Filter Sort panel can be used as described in Section 5 2 5 Filtering and Sorting 8 2 1 Executing a Single Test Case Clicking on the action icon of a test case executes that Test Case Figure 8 2 114 Execute 0 Execute pa Evaluate y Configure webapp 2 p Run Test Case My Jobs Run Test Case Fiter Sot 10 f ID 2 Revision Name Traceability Steps Action SUBES STER TC00003 1 0 Continuous Integration check 2 F RTI THE TC00002 10 Project setup check 1 F Import Test Results TC00001 A 1 0 IDE check 2 583 Figure 8 2 The Run Test Case Screen Warning Only test cases with the states Draft Approved and Skip can be executed A dialog showing information about the test case will be displayed Figure 8 3 Clicking the view icon on the right side of the dialog displays more detailed information about t
72. be changed to the tabular step instructions view by mark ing the tabular view checkbox The test suite results screen allows the user to write a description and summary for the test suite run as well as for each individual test case and test step in the test run Figure 8 11 122 Execute Tabular View 1500001 Sprint Null Test Case MN ora Test Suite Execution Overview Test Suite Result T3R0000003 Test Run TRUD000010 Execution time 0 Second s Test Case Results E Test Case Result T1C00001 TCRO000014 Test Case TC00001 IDE check summary Description Steps Step 1 Start IDE Summary Description Save Changes Link Issue Create Issue Finish Figure 8 11 The Test Suite Results Screen 00000000 Note Ea If there are any issue management systems configured for this project the Create Issue button will be enabled For instructions on creating an issue with Klaros Testmanagement see Section 8 6 Creating Issues 8 4 Continue Test Run Sometimes a test run has to be suspended due to working hours or external conditions which prevent further test case executions A tester may stop executing a test run at any time without losing any previously entered test data A test run which is interrupted in its execution can be continued later The execution resumes with the first test case step with no result The Continue Test Run page lists all test runs in the selected project which have not
73. been finished To get a better overview of the available interrupted test runs the sorting and filtering functionality of the Filter Sort panel can be used as described in Section 5 2 5 i Filtering and Sorting 123 Execute F gt Note The Miscellaneous settings page contains a setting which prevents users with the role Tester from seeing interrupted test runs of jobs from other users Sec tion 10 5 1 Miscellaneous Settings 8 4 1 Continuing a Suspended Test Run To continue the execution of a stopped suspended test run click on the icon of the test run Figure 8 12 To delete a suspended test run click on the icon in the action column MN Sop Execute SCE SET WebApp A Continue Test Run Filter Sort Ey 10 Run Test Case ID e Revision Description Executor Test Environment System under Test Progress TS00001 1 0 Sprint Null 11 20 13 7 45 11 PM John Doe tomcat ad hoc 0 2 SNAPSHOT 0 3 Fre a Run Test Suite Continue Test Run Import Test Results TC00003 1 0 Continuous Integration check 11 20 13 7 44 57 PM John Doe tomcat ad hoc 0 2 SNAPSHOT 0 1 Pg a Figure 8 12 The Continue Test Run Screen Section 8 2 Run Test Case describes the process of executing a test suite The new test results are merged automatically with the suspended test suite run results 8 5 Import Test Results Klaros Testmanagement allows users to import test results fr
74. can be enabled at once Enabled languages are added to the language selection panel at the top of the screen in Klaros To enable a language click the icon in the Available Languages table and to disable a language click the icon in the Enabled Languages table AN Caution Please refer to Section 4 1 Languages for detailed information on the file for mat 10 6 Integration This page contains the settings for integration of Klaros Testmanagement with external tools and infrastructure It contains four tabs E Mail Issue Management Network and LDAP Clicking the Save button persists the changes to the Klaros Testmanagement proper ties file and clicking Cancel discards all changes 10 6 1 Issue Management An Issue Management System aka Issue Tracker Bug Tracker is a software package that manages and maintains issues occuring during the testing process Issues may contain re ports about defects in a software system or other observed information Klaros Testmanagement is capable of creating and retrieving entries in remote issue man agement systems and assigning them to failed test results It is possible to configure and simultaneously use multiple issue management systems Currently Klaros Testmanagement supports the following issue management systems 174 Configure e Bugzilla a free open source issue management system see http www bugzilla org s JIRA a commercial issue management system produced by
75. case that may be useful for users to know Dependency The dependencies of the test case it may depend on another test case Evaluation 95 Define The mode of test result evaluation Manual or Automated e Execution The mode of test case execution Manual or Automated Traceability A reference to the corresponding requirement use case or work package e State The test case state determines whether it is editable executable or visible in result listings Only test cases with the state Draft are editable A test case with the state Locked is not executable and a test case with the state Skip is not shown in any reports Projects Iterations Requirements Test Environments Systems under Test Test Suites Plan po Execute pi Evaluate y Configure Issue Management System Integration L p 1 0 TC00001 Testing the file upload of the ticket system E Back Properties User Defined Steps Attachments Revisions Results Changes ID TC00001 Name Testing the file upload of the ticket system Description The ticket system supports attaching files to tickets in the most recent Version In this test case it should be tested to what extend the file upload works A new ticket should be created and a file should be attached to this ticket Precondition The tester is logged in at one of the terminals Postcondition Expected Result The ticket has been successfully created Note
76. clickthe Assign button to open a dialog which allows you to select artifacts to assign to this iteration Artifacts may be removed by selecting them and clicking the icon above the table The Test Environments tab shows the test environments which have been added to this iter ation The Systems under Test tab shows the systems under test which have been added to this iter ation as well as their Compliance Coverage Success and Progress metrics These are metrics relating to the amount of test cases executed and the latest results of these executions Progress and Success show these metrics for all test cases in the project while Coverage and Compliance show them for test cases which cover requirements in this iteration Progress The percentage of the test cases in the project which have been executed in this iteration Success For the test cases executed in the Progress metric the per centage which were last executed with the result Passed 78 Define Coverage The percentage of the test cases which cover requirements which are included in this iteration which have been exe cuted in this iteration Compliance For the test cases executed in the Coverage metric the per centage which were last executed with the result Passed The Requirements tab shows the requirements which have been added to this iteration as well as their Compliance and Coverage metrics These are metrics relating to the amount of test cases executed agains
77. com Administrator 2 E System C devManager Devon Manager Test Manager v 2 I E Integration Y manager A Max Mustermann max mustermann company com TestManager y Z SA Backup C peter Peter Dev Tester v ZE Y susan Susan Dev Tester v 258 VW tester Email mann company com Tester v 2 E tester2 A Rote cae gt termann com Tester v FE tester3 ae pe ustermann com Tester v FE testers 3 users will be edited Esad 228 Next Cancel found Page 1 of 2 1 2 gt 10 Iy Figure 5 19 Bulk Editing Objects 5 2 11 User Defined Properties da Feature only available in Klaros Testmanagement Enterprise Edition 7 edition gt In Klaros Testmanagement Iterations Requirements Test Environments Systems under Test Test Cases Test Suites and Test Runs can all be extended by extra fields using user defined properties These are defined on a per project basis in the User Defined tab of the Project Details page This tab is shown in Figure 5 20 Functional Overview Plan po Execute pi Evaluate y Configure Issue Management System Inte E e A fr P00003 Issue Management System Integration a A KE ER Iterations Properties User Defined Copy Test Cases Access Results Changes Reguirements Test Environments 10 vw Systems under Test Object Type Name Default Action TostCas0s Requirement Text requirement number 0 S Test Suites Test Case Boolean regression test O SH Iteration Text
78. document store 3 6 3 Database Migration After updating Klaros Testmanagement to a newer version it is possible that a database migration will be necessary If so Klaros Testmanagement will show the following screen on startup To startthe migration an administrator account is needed Before the migration process starts the appropriate authentication domain should be selected LDAP or KLAROS Figure 3 14 To use the new version the database has to be User Name updated You need an administrator access to Klaros to do this Please create a backup ofthe database first 9 For this please refer to the manual of your database application Password Active Database Revision 4 6 Current Database Revision 49 Authentication Domain KLAROS y testmanagement Figure 3 14 Database Migration 3 6 3 1 Migration of installations prior version 3 0 In order to update Klaros Testmanagement installations prior version 3 0 to version 3 0 0 or above it is mandatory to upgrade the installation to Klaros Testmanagement 2 6 2 before attempting any further upgrade 35 Installation 3 7 Important File Locations There are two important locations in a Klaros Testmanagement installation One of these is the installation folder where application server and the klaros web application will be installed in The other is the home folder containing runtime data like configuration files search indices and attachments Per default is th
79. ears Server Address localhost User Context DN ou Person dc acme dc com Server Port 389 User Object Classes person uidObject Mobile Devices s 2 Bind DN cn Manager dc acme dc com Enable naive DN Matching Mode System Bind Credentials eeeeee User DN Prefix uid Integration Follow Referrals User DN Suffix ou Person dc acme dc com Backup User Search Attribute uid Full Name Attribute cn User Name Attribute uid Email Attribute mail User Password Attribute userPassword Enabled Attribute Set as default Disable Password Synchronization Test LDAP access Figure 10 28 The LDAP Tab Parameters needed to contact the LDAP server Server Address The URI under which the LDAP server resides e g ldap acme com s Server Port The port on which the LDAP server is listening typically 389 Bind DN The distinguished name used for binding to this LDAP server s Bind Credentials The credentials password required to be able to bind to this LDAP server s Follow Referrals If this option is enabled searching a directory automatically follows any referrals the serv er might return When disabled referrals will be ignored and other servers will not be con tacted during the search Parameters needed to locate user accounts e User Context DN The distinguished name under which user accounts will be searched e g ou Users dc verit dc de User Object Classes 181 Configu
80. element may occur inside the following elements lt testcase gt Table C 5 lt attributes gt elements 345 Test Case Import File Specification C 5 lt container gt The container element for test cases This is the root element of this schema Table C 6 lt container gt elements C 6 lt testcases gt The list of custom attributes This element may occur inside the following elements lt container gt Table C 7 lt testcases gt elements C 7 lt testcase gt A test case definition This element may occur inside the following elements lt testcases gt me Maties penaas ooo mes i EN EN EO WEE ET i S EN EEN EE sede CSI EN ET CI NN fee rte Ot me R meaa R asn R foie R 346 Test Case Import File Specification name manas besete oser Oe EN IE ET Ot ESTOS e mm em ON ee CMS anger R ETT CCAA Table C 8 lt testcase gt elements C 8 lt triggers gt The list of triggers for this object This element may occur inside the following elements lt testcase gt maa R Table C 9 lt triggers gt elements C 9 lt testsuite gt If this element is present a test suite with the name given here will be generated upon import This test suite will contain all the test cases that are part of this import container This element may occur inside the following elements lt con
81. getTestRuns Returns the project test runs Parameters return Set containing the test run objects of the project B 1 1 4 15 getTestSuiteCategoryTrees public abstract Set lt KlarosTestSuiteCategoryTree gt getTestSuiteCategoryTrees Returns the project test suite category trees Parameters return Set containing the test suite category trees of the project B 1 1 4 16 getTestSuites public abstract Set lt KlarosTestSuite gt getTestSuites Returns the project test suites Parameters return Set containing the test suite objects of the project 223 Model API Reference B 1 1 4 17 isSecured public abstract Boolean isSecured Returns whether this project is secured or not Parameters return true if this project is secured false if not B 1 1 5 IKlarosEnumValue A Custom property enumeration value B 1 1 5 1 Synopsis public interface IKlarosEnumValue Public Methods public abstract String getValueO T B 1 1 5 2 getValue public abstract String getValueO Gets the enumeration value Parameters return the value B 1 1 6 IKlarosExternalImplementation This interface provides access to the information about the implementation of a test case B 1 1 6 1 Synopsis public interface IKlarosExternalImplementation extends IKlarosExternalLink Public Methods public abstract KlarosTestCase getImplementation0f O 224 Model API Reference B 1 1 6 2 getImplementationO
82. getTrunkRootO Get the root of a trunk Parameters return the revision which is the first revision of the branch to which this revision belongs B 1 1 19 IKlarosSUTImplementation 247 Model API Reference This interface provides access to data of a system under test version B 1 1 19 1 Synopsis public interface IKlarosSUTImplementation extends IKlarosNamedEntity Public Methods public abstract Set lt KlarosAttachment gt getAttachments public abstract Set lt KlarosSUTImplementationCategoryNode gt getCategories public abstract KlarosConfiguration getConfiguration public abstract Set lt KlarosIssue gt getIssues public abstract Set lt KlarosIteration gt getIterations public abstract String getProductversion public abstract Set lt KlarosTestRun gt getTestRuns B 1 1 19 2 getAttachments public abstract Set lt KlarosAttachment gt getAttachments Gets the attachments associated with this system under test Parameters return the attachments 248 Model API Reference B 1 1 19 3 getCategories public abstract Set lt KlarosSUTImplementationCategoryNode gt getCategories Gets the categories this system under test belongs to Each category node will belong to a different category tree Parameters return the category nodes B 1 1 19 4 getConfiguration public abstract KlarosConfiguration getConfigurationO Get configuration Parameters return The related configurati
83. gt getCategories KlarosConfiguration getConfiguration Set lt KlarosTestCase gt getCoveringTestCases String getDescription Set lt String gt getExternalNamesO Set lt KlarosIteration gt getIterations KlarosRequirement getPredecessor RequirementPriority getPriority KlarosRequirementGroup getRequirementGroup KlarosRequirement getRoot String getShortnameO String getState KlarosRequirement getSuccessor String getSummary KlarosRequirement getTrunkRootO Methods inherited from de verit klaros core model KlarosRevision getRevisionComment getRevisionld Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty 294 Model API Reference Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait ER IE Se i S Sextends Revision KlarosRevision lt KlarosRequirement Requirement gt j KlarosRequirement getConfiguration KlarosConfiguration getCovering TestCases Set lt KlarosTestCase gt getRequirementGroup KlarosRequirement Group getCategories Set lt KlarosRequirementCategoryNode gt getTrunkRoot KlarosRequir
84. havior of the web application is unpredictable when it is used 5 1 Login Figure 5 1 shows the login screen of Klaros Testmanagement To login just enter the user name in the User name field and the associated password into the Password field My defect was a showstopper on build UserName 645 Quote ofthe day Password Authentication Domain KLAROS y Klaros om x testmanagement Figure 5 1 Login Screen The Klaros Testmanagement database predefines three default users accounts with follow ing roles e Administrator Username admin Password admin s Manager Username manager Password manager e Tester Username tester Password tester For a description of the users roles and the permissions associated with each role see Ap pendix A Role Permission Overview Confirm the login to Klaros Testmanagement by clicking the Login button 49 Functional Overview Klaros Testmanagement is multilingual By default Klaros Testmanagement chooses the language that is determined by the locale settings of the server Klaros Testmanagement is installed on If you want to choose a different language you may select the corresponding flag at the bottom right corner of the login screen The language of the user interface changes immediately and the choice will be stored automatically After a successful login the Maintain Project page is shown Figure 5 2 Plan Execute Fi Evaluate X Configure W
85. icon opens the test case details page where more properties of the test case can be set Section 6 6 3 Test Case Details Clicking the duplicate icon allows the user to create a copy of the test case 6 6 3 Test Case Details 6 6 3 1 Test Case Overview Plan Execute pl Evaluate X Configure webapp L TC00001 IDE check EN KYU Projects Back Iterations EE Overview Properties User Defined Steps 2 Attachments Revisions Issues Jobs 2 Results 31 Changes Requirements Test Environments pp Execution Manual Systems under Test Priority Low Latest Executor John Doe Test Suites Execution Times of this Test Case Most unsuccessful Test Case Steps 12 10 Ez 8 gt E S Maximum a 6 L A Failure E edge B Error amp Minimum YE Ed 2 x LL 0 Step pou Ere oe EE Ee EE Ee Passed 02 SNAPSHOTS 0 3 SNAPSHOT Latest Results ID 3 Name Start Executor Test Run Test Environment System under Test Duration Result Action TC00001 IDE check 11 20 13 8 24 06 PM John Doe TRU0000015 tomcat ad hoc 0 2 SNAPSHOT 6 1ms Q TC00001 IDE check 11 20 13 8 24 14PM John Doe TRU0000016 tomcat ad hoc 0 2 SNAPSHOT 6 1ms Q TC00001 IDE check 11 20 13 8 29 39 PM John Doe TRUO0000027 tomcat ad hoc 0 2 SNAPSHOT 6 ims A TC00001 IDE check 11 20 13 8 03 30 PM John Doe TRUO0000010 tomcat ad hoc 0 2 SNAPSHOT 6 1ms Q TC00001 IDE check 11 20 13 8 24 21 PM John Doe TRU0000017 tomcat ad hoc 0
86. importer password since plugin ver The password for the import If Klaros Testmanagement sion 1 1 is configured to use authentication for the import a valid password must be passed to the importer A complete example for a QF Test import URL would look like this http localhost 18080 klaros web seam resource rest importer conf ig P00001 amp env ENV00001 amp sut SUT00001 amp type qftest amp time 01 03 2011_12 amp username me amp password secret Example 12 11 QF Test import URL sample e The lt klaros app ur1 gt Term The http localhost 18080 klaros web URL shown above is the default klaros application url when accessing Klaros Testmanagement from the host it is in stalled on and may vary with your setup Throughout this this chapter the term lt klaros app url gt will be used instead to reflect this The result file is contained in the HTTP request body The curl command line tool can be used on Linux or Windows Cygwin to trigger an import in a single command line curl v H Content Type text xml T lt test result file gt lt klaros app url gt seam resource rest importer config P00001 amp env ENV00001 amp sut SUT00001 amp type junit amp time 23 05 2011 14 55 Example 12 12 curl command line example I Note All artifacts which are referenced during import like projects or test cases con tain five digits in their ID For example P00001 is a valid project ID while POT and POO1 are not
87. installation Use the following sample script and adapt installpath and the userInputs The installation may issue some warnings of the form AutomationHelper class not found for panel which can be safely ignored lt xml version 1 0 encoding UTF 8 standalone no gt lt AutomatedInstallation langpack eng gt lt com izforge izpack panels htmlhello HTMLHelloPanel id hello gt lt com izforge izpack panels htmlinfo HTMLInfoPanel id info gt lt com izforge izpack panels licence LicencePanel id license gt lt com izforge izpack panels target TargetPanel id target gt lt installpath gt opt Klaros Testmanagement lt installpath gt lt com izforge izpack panels target TargetPanel gt lt com izforge izpack panels packs PacksPanel id packs gt lt pack index 0 name Tomcat 8 Application Server selected true gt q n lt pack index name Klaros Testmanagement selected true gt lt pack index 2 name PDF Documentation selected false gt lt com izforge izpack panels packs PacksPanel gt lt com izforge izpack panels userinput UserInputPanel id portselection gt lt userInput gt lt entry key tomcat_server_port value 18005 gt lt entry key tomcat_http_port value 18080 gt lt entry key tomcat_https_port value 18443 gt lt entry key tomcat_ajp_port value 18009 gt lt entry key tomcat_session_timeout value 60 gt lt entry key tomcat_memor
88. instance of the xUnit architecture for unit testing frame works MbUnit is an extensible unit testing framework for the NET Framework that takes in and goes beyond xUnit pattern testing MbUnit is part of the Gallio bundle MSTest is he command line command that is used to run tests This command has several options you can use to customize your test run NUnit is a unit testing framework for all Net languages It is written entirely in C and has been completely redesigned to take advantage of many NET language features for ex ample custom attributes and other reflection related capa bilities PHPUnit is a member of the xUnit family of testing frame works and provides both a framework that makes the writ ing of tests easy as well as the functionality to easily run the tests and analyse their results QF Test is a professional tool for automated testing of Java and Web applications with a graphical user interface The QTestLib framework is a tool for unit testing Qt based applications and libraries Ranorex is a GUI test automation framework for testing of desktop web based and mobile applications Selenium is a web browser automation tool primarily used for automated testing of web apps Selenium is able to pro duce Unit compatible test results which can be imported into Klaros Testmanagement TestComplete is a cross platform automated GUI testing tool from SmartBear Software TestNG is a testing framework inspir
89. last login are displayed Clicking the x icon closes the log panel It can be opened again at any time by clicking on the log panel icon in the navigation bar Figure 5 10 The Log Panel Icon 5 2 5 Filtering and Sorting It is possible to filter and sort the displayed objects on most pages in Klaros Testmanage ment The Filter Sort link above the table opens the panel which contains two tables The left hand table contains the active filters and the right hand table contains the active sort orders Plan Execute Pl evaluate X Configure Swe p 7 Test Cases Projects Iterations aa A GE E B Categories Filter 1 Sort 0 Ej 10 v Requirements Filter 1 Sort 0 Test Environments R E s Type Value Action Order by Type Action Systems under Test ID v Like v 00003 No entries available c A Test Suites Apply Reset Close Revision Traceability Priority State Execution Steps Action OJ Tco0003 a 1 0 Continuous Integration check Medium Approved Manual 2 2 ER T Tcooo002 a 10 Project setup check High Locked Manual 1 2 ER OJ TC00001 a 10 IDE check Low Draft Manual 2 2 BB Revision Traceability State Execution Steps Action Figure 5 11 The Filter and Sort Panel Below the two tables are two buttons Apply The Apply button applies the filter and sorting criteria specified in the two tables and presents the filtered and sorted results Reset The Reset button clears the filter and sort
90. lt W P gt implements IKlarosCategoryNode lt I T W P gt Public Constructors public KlarosCategoryNode P wrapped Public Methods public T getCategoryTree public String getDescription public W extends KlarosCategoryNode lt I T W P gt getParentO public String getShortname public List lt W gt getSubCategories Direct known subclasses de verit klaros core model KlarosIterationCategoryNode de verit klaros core model KlarosRequirementCategoryNode de verit klaros core model KlarosSUTImplementationCategoryNode de verit klaros core model KlarosTestCaseCate goryNode de verit klaros core model KlarosTestEnvironmentCategoryNode de verit klaros core model KlarosTestSuiteCategoryNode Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 278 Model API Reference xtends KlarosCategoryNode lt l T W P gt e xtends CategoryNode KlarosCategoryNode KlarosCategoryNode wrapped P extends CategoryNode getShortname String getDescription String getCategoryTree T getParent W extends KlarosCategoryNode lt l T W P gt getSubCategories List lt W gt B 1 1 33 2 KlarosCategoryNode P public KlarosCategoryNode P wrapped Instantiates a new klaros category node Parameters wrapped the wrapped class B 1 1 34 KlarosCatego
91. nthal Pfalz A ae G l Pfilzenvald i iN o i a Pkilzerwale i f i gt L KO A x N Schriesheim C Pfalzerwaid Bad pne SN o BA L TTT Kaisi r lautern RE ALL ayr N A Standstuh Leaflet Map data Data imagery and map information provided by MapQuest OpenStreetMap and contributors ODbL Back Figure 9 26 The Location Tab The map has several interactive elements on it The map can be moved in any direction by pressing the left mouse button holding the mouse button and then moving the mouse Initially the map is centered to the marker of the first test case step result The map is also scaleable The scaling can be triggered by scrolling the mouse wheel up Scale up or down scale down Alternatively the toolbar in the upper left of the map can be used to scale the map 9 6 Test Suite Results The test suite result screen shows results for individual test suites The total number of re sults for each test suite is shown Figure 9 27 To get a better overview of the test suites the sorting and filtering functionality of the Filter Sort panel can be used as described in Section 5 2 5 Filtering and Sorting E Define Plan LS Execute m Evaluate N Configure Test Suite Results Dashboard Fiter Sort El 10 Report Templates ID Revision Description TestCases Results Action Test Run History TS00001 1 0 Sprint Null 3 1 amp Q Test Runs Test Case Results
92. overview of all mobile devices with the Klaros Testmanagement Mobile Edition Android Client installed that have tried to synchronize with the Klaros Testmanagement server at least once 166 Configure Plan TF Execute Ln Evaluate E Configure Test GPS Tracking ma A Mobile Devices Licensed Mobile Devices 1000 Report Templates Activated Mobile Devices 41 Fiter Sort El 15 v Users MD00045 amp Nexus S 2 tester 10 23 2013 2 E SEAN 11D00044 amp GT N8010 tester 10 23 2013 GE Mere MDOOO43 amp Nexus S 1 torsten 10222013 2 B A D00042 GT 19100 torsten 10222013 2 B MD00041 GT N7000 tester 10 21 2013 2 B MD00040 amp Nexus7 Tablet tester 10 23 2013 2 E MD00039 amp GT N8010 tester 10 21 2013 2 E MD00038 Nexus S admin 10 21 2013 2 E MD00037 GT N8010 tester 10 21 2013 2 MD00036 amp HTC Desire S tester 10 30 2013 GE MD00035 amp GT 19100 tester 10 21 2013 GE MD00034 Nexus S tester 10 18 2013 2 MD00033 amp Android SDK built for x86 tester 10 18 2013 ra MD00032 Nexus 5 This device is deactivated tester 10 18 2013 2 E ID Device Name Comment Last User LastAccess Action 44 Elements found Page 3 of 3 14 lt a 1 2 3 15 v Figure 10 11 The Mobile Devices Page The first column of the table shows the automatically generated number that each mobile device is assigned The second info column indicated by the light bulb shows the status of the mobile device which can be either activate
93. public public public public public public public abstract abstract abstract abstract abstract abstract abstract abstract abstract Model API Reference List lt KlarosJob gt getSubJobsO Integer getSuccessRate String getSummaryQ KlarosSUTImplementation getSutO KlarosTestCase getTestCase Set lt KlarosTestRun gt getTestRuns KlarosTestSuite getTestSuite List lt KlarosJobUpdateAction gt getUpdateAction List lt KlarosJobTimeBlock gt getWork 232 Model API Reference B 1 1 10 2 getAttachments public abstract Set lt KlarosAttachment gt getAttachments Gets the attachments associated with this job Parameters return the attachments B 1 1 10 3 getTestRuns public abstract Set lt KlarosTestRun gt getTestRuns Gets the test runs executed with this job Parameters return the test runs B 1 1 10 4 getUpdateAction public abstract List lt KlarosJobUpdateAction gt getUpdateAction Gets the update action list Parameters return the update action B 1 1 10 5 getWork public abstract List lt KlarosJobTimeBlock gt getWorkO Gets the list of work items done on this job Parameters return the work items B 1 1 11 IKlarosjobTimeBlock The job time block defines a certain amount of time the job has been worked on B 1 1 11 1 Synopsis public interface IKlarosJobTimeBlock Public Methods public abstract String getDescription public abstract Date getDoneAt
94. public abstract Set lt KlarosRevision lt T S gt gt getBranches Get branches of this revision Parameters return Set containing all revision objects which have been creat ed as first revision of a branch trunk root and habe been Created using this revision B 1 1 18 3 getBranchRoot public abstract KlarosRevision lt T S gt getBranchRoot Get the original revision of a trunk root revision object Parameters return The revision object that has been used to create a new branch B 1 1 18 4 getPredecessor public abstract KlarosRevision lt T S gt getPredecessorO 246 Model API Reference Get the predecessor of the revision Parameters return The revision object that is the predecessor of this revision B 1 1 18 5 getRevisionComment public abstract String getRevisionCommentO Get comment Parameters return The comment of the revision B 1 1 18 6 getRevisionId public abstract String getRevisionldO Get the revision id Parameters return The revision id B 1 1 18 7 getRoot public abstract KlarosRevision lt T S gt getRoot Get the root of the revision hierarchy Parameters return The root revision object B 1 1 18 8 getSuccessor public abstract KlarosRevision lt T S gt getSuccessorO Get the successor of the revision Parameters return The revision object that is the successor of this revision B 1 1 18 9 getTrunkRoot public abstract KlarosRevision lt T S gt
95. public abstract UUID getKey Get the internal key of the object This key is globally unique Parameters return The internal key B 1 1 13 4 getName public abstract String getName Get the name of the object This matches the id field visible in the UI Parameters return The name of the object B 1 1 13 5 isEnabled public abstract boolean isEnabledO Returns the value of the enabled flag of this object Parameters return true if the entity is enabled else false B 1 1 14 IKlarosNamedEntity This interface provides access to data of a properties owner B 1 1 14 1 Synopsis public interface IKlarosNamedEntity extends IKlarosLabeledObject Public Methods public abstract KlarosUser getAssignee public abstract List lt IKlarosProperty gt getPropertiesO public abstract boolean isDefinedProperty String propertyName 237 Model API Reference B 1 1 14 2 getProperties public abstract List lt IKlarosProperty gt getProperties Gets the list of properties Parameters return the properties B 1 1 14 3 isDefinedProperty String public abstract boolean isDefinedProperty String propertyName Check if a property identified by given name is a defined property Parameters propertyName The name of the property to check return true if the identified property is a defined property false else B 1 1 15 IKlarosProperty A user defined property B 1 1 15 1 Synopsis public interface
96. required execute more queries to retrieve the data or process the already retrieved data and store the processed data in the context with a different name 191 Custom Reports Note El It is possible to store more than one object in the context Just use a different name for each object 11 3 2 Creating a SeamPDF Report Template The code snippets presented in this section show how to build a report template for Klaros Testmanagement For detailed information please refer to SeamPDF man ual More information on the Klaros Testmanagement object model can be found in de verit klaros core model The following snippet shows how to build the frame for the report template Inside this frame all other Report details can be described and grouped in chapters and sections lt p document xmlns ui http java sun com jsf facelets xmlns f http java sun com jsf core xmlns p http jboss org schema seam pdf title Klaros Testmanagement Test Suite Report marginMirroring true author user name creator user name pageSize A4 gt lt p document gt Note the usage of the de verit klaros core model KlarosUser parameter from the context user name L The next code snippet shows how to define headers and footers for all pages in the report This snippet makes use of the date and the de verit klaros core model KlarosUser object in the context lt f facet name header gt lt p font size 8 gt lt p
97. results A job may be repeated and executed multiple times so one job can refer to more than one test run Introduction Test Manager Results Figure 2 5 Jobs In addition to test execution other job types exists allowing to schedule reviews of test cases or reduirements and specify arbitrary tasks in a textual form Jobs can be nested and individually assigned to users Therefore it is possible to track progress of larger distributed test activities 2 9 User Roles Every User has his Rights Klaros Testmanagement defines four roles available to users Administrator Manager Tester and Guest Only a user with the Administrator role is able to create and assign other users Guests are only able to view artifacts and reports they are not able to change anything in the system Testers have more permissions than those in the role of guest They are not only able to view artifacts but in addition they are allowed to execute jobs test cases and test suites and edit test results Managers inherit all rights of a tester and also possess additional rights to create and update artifacts like test cases requirements and more Introduction Administrators have all available rights in the system In addition to the rights a manager has they are able to create and delete projects and users as well as configuring system wide parameters Each users has a defined default role which is assigned by an administrator when creating
98. return the attachments B 1 1 16 3 getCategories public abstract Set lt KlarosRequirementCategoryNode gt getCategories 240 Model API Reference Gets the categories this object belongs to Each category node will belong to a different Category tree Parameters return the category nodes B 1 1 16 4 getConfiguration public abstract KlarosConfiguration getConfiguration Get configuration Parameters return The related configuration B 1 1 16 5 getCoveringTestCases public abstract Set lt KlarosTestCase gt getCoveringTestCases Get test cases covering the requirement Parameters return Set of test cases which cover this test requirement B 1 1 16 6 getDescription public abstract String getDescription Get the description Parameters return the string B 1 1 16 7 getExternalNames public abstract Set lt String gt getExternalNames Gets the external requirement names this requirement is associated with External require ment names are used to match imported requirements to existing requirements Parameters return the external names B 1 1 16 8 getIterations public abstract Set lt KlarosIteration gt getIterations Get the iterations this requirement is assigned to Parameters return Set of iterations this requirement is assigned to 241 Model API Reference B 1 1 16 9 getPriority public abstract RequirementPriority getPriority Gets the priority Param
99. see Section 8 6 Creating Issues 8 3 Run Test Suite Executing a Test suite consists of running a defined set of test cases on a specific version of the system under test in a selected test environment The Run Test Suite page shows all test suites of a project in a list To get a better overview of the available test suites the sorting and filtering functionality of the Fi ter Sort panel can be used as described in Section 5 2 5 Filtering and Sorting 8 3 1 Executing a Test Suite Clicking on the action icon of a test suite executes that test suite Figure 8 8 dO 30 Execute 9 BSC SET Swersp O Run Test Suite My Jobs Fiter Sort 10 e Run Test Case Run Test Suite Continue Test Run ID Revision Description TestCases Action Tso0003 A 1 0 Sprint 01 0 iS Ts00002 1 0 Sprint 02 0 b Import Test Results TS00001 10 Sprint Null 3 Figure 8 8 The Run Test Suite Screen 120 Execute Warning Test cases with the state Locked or without any steps will be skipped when exe cuting the test suite A dialog showing information about the test suite will be displayed Figure 8 9 Clicking the icon on the right side of the dialog displays more detailed information about the test suite Execute Test Suite TS00001 Sprint Null O Test Suite Details ID T500001 Revision 1 0 Description Sprint Mull s 7 PA O D TC00001 amp 1 0 IDE check Manual L
100. side of the screen A Define Plan po Execute qa Evaluate E Configure Issue Management System Integration S amp Report Templates gas Name Revision Description Changed By Changed Action Test Run Overview Report 1 0 Lists the Test Runs in a project grouped by selectable parameters admin 11 12 13 5 12 PM 2 a WET Iteration PDF Overview Report 10 Lists a defined Iteration in a Project admin 11 12 13 5 12 PM 2 MT Job Excel Overview Report 10 Lists the defined Jobs in a project grouped by selectable parameters admin 11 121135 12PM E 2 a System Job PDF Overview Report 1 0 Lists the defined Jobs in project grouped by selectable parameters admin 11 12 13 5 12 PM 2 a IEEE 829 Testrun Deviation Report Template v1 1 0 NEEE 829 Testrun Deviation Report Template v1 admin 11 12 13 5 12 PM B a a E IEEE 829 Test Plan Template v1 1 0 IEEE 829 Test Plan Template v1 admin 11 12 13 5 12 PM 2 E Pe IEEE 829 Test Case Specification Template v1 1 0 IEEE 829 Test Case Specification Template v1 admin 11 12 13 5 12 PM 2 E 0 Elements found Page 1 of 1 1 10 w Figure 11 2 The Report Templates Page To create a new report click on the New button on the Report Templates page Then provide the basic data for the report by entering a name in the Name field and a short description in the Description field 187 Custom Reports E Define 9 Plan TF Execute qa Evaluate E Configure Test GPS Tracking Report Template Details AN Revis
101. sisie ss eee 9 210 ve JANIS ES e ee niu 10 214 TSSUC Management SYSTEMS see ee 10 3 s 11 IL BERNS MON PP 11 ST 1 License Model USER saa 11 3 1 2 License Model Mobile Devices ses ee ee ee ee ee ee ee ee ee ee ee ee Re Ge ee 11 82 EM JE O T 12 52 1 CENT Prere quistes saa 12 3 2 2 SERVER Prerecduisites 4 12 3 3 Installatio n PROCESS ia Gee Ee ee De Se 19 SL SET Welcome EE ee EE nes eran arte A EE 19 5 32 T R 2 OA TN See 20 55 53 5100 I LICENSING AGreeGIMents PP 21 3 3 4 SEN TAJ PEN re 22 3 3 5 Step 5 Select Installation Packages esse ecce eee eee 23 550 SEN O VE DIN 24 3 3 7 SENT SANN AAPP E EG 24 3 3 8 Step 8 Perform External Processes issie ese de de de ee ke 26 5 30 50609 setup SOE sje 26 3 3 10 Step 10 Installation Finished iese se eee eee eee ee Ge ee 27 3 4 Console based sl re 28 TSN We Welcome iS EE EE oe DE ee Ee 28 342 Step 2 Moralen sb Ee EER GE EE ee De N EE ee Ee 29 34 5 Step 3 LICENSING Agreement ansiosa 29 3 4 4 Step 4 Target Patli NE 30 3 4 5 Step 5 Select Installation Packages sesse ss se sk eee 30 SAO Stepo JE Data aa AET H De GE Eg 30 547 A N DE EE N De EG ER Ee De 31 3 4 8 Step 8 Perform External Processes sese eee eee 31 2 4 9 SENT SUP SONE T 31 3 4 10 Step 10 Installation Finished sss sees ecce ecce eee eee ee Re ee 31 35 Automated Installatiom SU ae 32 3 6 Update PORS SN 33 Klaros Testmanagement User Manual 3 6 1 Incompatible Installatio
102. systems to the project they must first be created by an administrator Y Click here to create an Issue Management System Created by John Doe on 11 18 13 5 24 PM Last changed by John Doe on 11 18 13 5 24 PM Save Discard Back Figure 6 2 The Project Properties Page On this page it is also possible to edit the Description of the project 6 1 6 2 User Defined Properties y j OS Feature only available in Klaros Testmanagement Enterprise Edition ition User defined properties can be used to customize objects within Klaros Testmanagement by adding custom fields This process is described in Section 5 2 11 User Defined Properties 6 1 6 3 Copying Objects from another Project to the current Project enterprise Feature only available in Klaros Testmanagement Enterprise Edition edition JE It is possible to copy objects from another project to the current one This function can be accessed via the Copy Objects tab on the project details page see Figure 6 2 The Project Properties Page To copy objects a project has to be selected from the Source Project drop down box first This opens up several tabs with requirements test environments systems under test test cases and test suites from the source project 70 Define Plan po Execute pi Evaluate y Configure mRo0o002 Traffic controler system S L 2 P00010 a pack Iterations Properties User Defined Copy Objects Access Results C
103. table above tables with bulk options and as a large icon at the top right of Details pages The print page displays all of the fields of the object on a single page The print pages for objects which contain other objects e g test suites contain test cases also contain print options at the top These allow the user to limit the information which is printed e g the Details option on the test suite print page limits the displayed test case information to the ID and Name of the test cases contained in the test suite By selecting the Suppress empty fields checkbox all fields which do not contain contents are suppressed from the print view Figure 5 12 shows the print page for a test suite 00000000 Note PP The selected print options will preserved during a user session 56 Functional Overview Print Options Suppress empty fields Details Brief vi 7 Test Suite T500001 Sprint Null Properties Name sprint Null System under Test SUTO00006 0 2 SNAPSHOT Revision 1 0 Created Erstellt Test Cases ID TC00001 Name IDE check ID TC00002 Name Project setup check ID TC00003 Name Continuous Integration check Figure 5 12 The Test Suite Print Page 5 2 7 Categorization Ka aditien E Feature only available in Klaros Testmanagement Enterprise Edition edition ES In order to manage a large numer of artifacts it is possible to catigorize them using arbi trary cretiria This feature can be used with
104. tables and displays all objects 5 2 5 1 Specifying Filtering Criteria Each line in the filter table represents a criterion which restricts the result set 54 Functional Overview Clicking the icon adds a new empty row for a filter criterion to the table The filtering criteria table has four columns The Field column denotes the field in the table that the criterion filters for The fields which can be filtered in the Filter Sort panel vary from page to page but generally include the main attributes of the objects which are displayed including user defined properties if available The Type column denotes the operator that is used for the criterion The following opera tors are available in Klaros Testmanagement Equals Only the items that exactly match the value of the criterion are shown Not equals The items that do not equal the value of the criterion are shown in the result table Greater than or equals Items that are greater than or equal the value of the crite rion are shown Less than or equals Items that are less than or equal the value of the criterion are shown Greater than Items that are greater than the value of the criterion are shown Less than Items that are less than the value of the criterion are shown Like Items that have a part that matches value of the criterion are shown The Value column defines the value for the filtering criterion The Action column contains a button for d
105. terms of this license agreement Made with IzPack http izpack org Figure 3 3 Licensing Agreement Screen The installation may be aborted by clicking the Quit button Clicking Previous goes back to the Information step and clicking Next proceeds with the installation 3 3 4 Step 4 Target Path The fourth step requests the target path where Klaros Testmanagement will be installed The user can usethe Browse button to search for the specific path in the local file system Figure 3 4 Important It is not recommended to install Klaros Testmanagement in the Programs fold er on systems running Microsoft Windows Vista or later By default Klaros Test management will not be able to start if installed here as tomcat requires write access to the install folder in order to deploy the web application This is blocked by Microsoft Windows User Account Control UAC If you wish to install Klaros Testmanagement in this location UAC must be dis abled 22 Installation Target Path Step 4 of 10 Select the installation path C Users gidley Klaros Testmanagement Figure 3 4 Target Path Screen The installation may be aborted by clickingthe Quit button Clicking Previous goes back to the Licensing Agreement dialog and clicking Next proceeds with the installation 3 3 5 Step 5 Select Installation Packages The fifth step allows to select the packages that are installed with Klaros Tes
106. test environment e Progress The progress rate shows how many test cases have been executed at least once in this test environment Note In contrast to the success rate the coverage rate considers only if a test case has been executed at least once in this test environment regardless of the result passed failed error Define Compliance The compliance rate shows how many test cases which are part of this iterations require ments have been successfully executed in this test environment Coverage The coverage rate shows how many test cases which are part of arequirement have been executed at least once in this test environment Note I In contrast to the compliance rate the coverage rate considers only if a test case has been executed at least once in the iteration regardless of the result passed failed error e Success History This graph shows changes in the compliance coverage progress and success rates of this test environment over time The timeline is automatically adjusted depending on the given timeframe s Most unstable Systems under Test This table displays the systems under test which have the lowest success and progress rates in conjunction with this test environment 00000000 Note DP This table is limited to five entries The other system under tests can be viewed by pressing the Show All button s Latest failing Test Cases This table lists the test cases which recent
107. test re sults related to this test suite as described in Section 5 2 14 Related Test Runs and Results 6 7 3 2 6 Bookmarking Test Suites Ke edition Feature only available in Klaros Testmanagement Enterprise Edition Test suites may be linked to from outside of Klaros Testmanagement using the link on the bookmark icon Right click the icon and choose Copy Link Location Firefox Chrome or the equivalent option 103 Chapter 7 Plan This section describes the plan section of Klaros Testmanagement The plan section is used to define and maintain jobs generate jobs from test cases and test suites and to track the workload and progress of users in the selected project Ka edition Feature only available in Klaros Testmanagement Enterprise Edition ition 7 1 Maintain Jobs This section is used to define and maintain jobs Jobs may consist of the execution of test cases or test suites or any other possible task Jobs can be nested and assigned to individual users The executions and results of jobs are automatically tracked by Klaros Testmanage ment Jobs can be created removed updated and nested on this page Figure 7 1 The displayed Jobs may be filtered and sorted as described in Section 5 2 5 Filtering and Sorting E Define amp Pan ES Execute qa Evaluate X Configure WebApp L Maintain Jobs Jobs from Test Cases Jobs from Test Suites Zee Bp Filter Sort amp 15
108. test suites 111 Plan A Define Pian ES Execute qa Evaluate y Configure WebApp Aa Jobs from Test Suites Maintain Jobs Fiter Sont 5 15 Jobs from Test Cases Jobs from Test Suites ID Revision Description Test Cases IT T500003 1 0 Sprint 03 0 EO S Ts00002 1 0 Sprint 02 0 Y T500001 1 0 Sprint 01 3 Schedule Execution Schedule Review Figure 7 8 The Jobs from Test Suites Screen When the Generate button is clicked Klaros Testmanagement generates a job for every selected test suite using the specified Assignee System under Test and Test Environment Each generated job is created with the corresponding test suite set in its Test Suite field 7 1 8 Jobs by User This section is used to track the workload and progress of individual users in the selected project On the Jobs by User page the workload work duration and progress of every user for the current active project is shown Clicking the Gi icon displays the details page Figure 7 10 for the selected user E Define amp ren L Execute qa Evaluate X Configure Jobs by User Maintain Jobs Fiter Sot 10 Jobs Estimated Time h Busy from Busy to Progress Action 0 0 00 Q 0 0 11 7 13 7 25 AM Q 0 0 10 31 13 10 00 PM Q 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Jobs from Test Cases Jobs from Test Suites Torsten Divers Ted Steve Manager Susan Dev Peter Dev Max Mustermann Lisa Ricardi John Doe Har
109. this section 88 Define 6 5 3 1 System under Test Overview E Plan po Execute pl Evaluate X Configure Sl SUT00020 0 2 Projects iterations Overview Properties User Defined Attachments Issues 1 Results 1 Changes Requirements Success History Test Environments Systems under Test Test Cases Success Progress MEN Test Suites Results Compliance Coverage Show all Created 2 months ago by John Doe Figure 6 19 The System under Test Overview Tab e Success The success rate shows how many test cases have been successfully executed in this sys tem under test e Progress M Success E Progress E Compliance E Coverage Mar 26 AprO1 Test Run Most unstable Test Environments ID System under Test TestRuns Success Progress Compliance Coverage Action ENVO0011 Solaris 11 2011 11 3 HIM HEM HEM Show all Latest failing Test Cases ID Name Start Executor Test Run Test Environment Duration Result Action TC00004 Kopie von IDE check 4 2 15 5 55 11PM John Doe TRUO0000064 Solaris 11 2011 11 00 00 09 A Q Show all Latest Issues ID System Summary Created Created By Assigned To Priority State Action PLAYGROUND 4173 E imo0001 de 8 23 2010 admin Blocker Open D Last changed 3 hours ago by John Doe Back The progress rate shows how many test cases have been executed at least once in this system under test Note In contrast to the success rate the coverage rate c
110. toString wait KlarosTestCaseState getTestCase KlarosTestCase getSut KlarosSUTImplementation getStateName String getStateDescription String B 1 1 62 KlarosTestCaseStep This class provides access to the information stored for test case steps B 1 1 62 1 Synopsis public final class KlarosTestCaseStep extends KlarosWrapper lt KlarosTestCaseStep TestCaseStep gt implements IKlarosTestCaseStep Public Methods public String getAction public String getExpectedResultO public String getPostcondition public String getPrecondition Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 309 Model API Reference KlarosTestCaseStep getAction String getExpectedResult String getPostcondition String getPrecondition String B 1 1 63 KlarosTestCaseStepResult This class provides access to the information stored for test case step results B 1 1 63 1 Synopsis public final class KlarosTestCaseStepResult extends KlarosNamedEntity lt KlarosTestCaseStepResult TestCaseStepResult gt implements IKlarosTestCaseStepResult Comparable lt KlarosTestCaseStepResult gt Public Methods public int compareTo KlarosTestCaseStepResult o public boolean equals Object o public String getActionO public String getDescription publi
111. tool tip of each icon The configurable properties of the report are The name of the report A boolean value indicating that this report always uses the active project A boolean value indicating that this report always uses the active iteration if available Alternatively the fixed iteration that this report will display if available Alternatively the fixed project that this report will display The execution rates assigned to the different health categories The success rates assigned to the different health categories Health Report 1 6 0 13 Tomcat 6 0 12 1 5 0 15 JBoss 5 1 0 GA Sun Microsystems Inc Sun Microsystems Inc Windows XP SP3 Ubuntu 9 04 a React05 WebLogic Linux IE Firefox 2 0 4 0 Oracle JRockit Open office 3 0 KLAROS 1 0 KLAROS 1 1 KLAROS 1 2 KLAROS 1 3 KLAROS 2 0 Figure 9 8 The Project Health Matrix Report 140 Evaluate 9 1 2 5 The Test Progress Report enterprise 7 edition i Feature only available in Klaros Testmanagement Enterprise Edition The Test Progress Report shows the rate of executed vs defined tests of a project for a given test environment and a system under test The configurable properties of the report are The name of the report A boolean value indicating that this report always uses the active project e Alternatively the fixed project that this report will display A boolean value indicating that this repor
112. used Figure 9 22 E Define Plan kS Execute Tg Evaluate X Configure WebApp sa L Test Case Results TC00003 Continuous Integration check Dashboard Test Case Details Fiter Sort El 10 Report Templates Test Run History ID Start Test Run Test Environment System under Test Executor Time Result Action METER TCR0000046 11 20 13 8 31 36 PM TRU0000040 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 Y 8 Q TCR0000045 11 18 13 8 31 27 PM TRU0000039 tomcat ad hoc 0 2 SNAPSHOT JohnDoe 00 00 01 x amp Q TEE TCR0000044 11 20 13 8 31 16 PM TRU0000038 tomcat ad hoc 0 2 SNAPSHOT JohnDoe 000001 HA EE TCR0000043 11 20 13 8 31 08 PM TRU0000037 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 Q TCR0000042 11 20 13 8 30 59 PM TRU0000036 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 Y a TCR0000041 11 20 13 8 30 52 PM TRU0000035 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 gt Q TCR0000040 11 20 13 8 30 44 PM TRU0000034 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 x L Q TCR0000031 11 14 13 8 25 38 PM TRU0000025 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 x amp TCR0000030 11 13 13 8 25 30 PM TRU0000024 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 x TCR0000029 11 12 13 8 25 21 PM TRU0000023 tomcat ad hoc 0 2 SNAPSHOT John Doe 00 00 01 Y Q 14 Elements found Page 1 of 2 12 o 10 x Back Figure 9 22 The Single Test Case Results Screen The test case details panel in the page shows all details of
113. 00001 tomcat ad hoc John Doe 1ms Q Q 34 Elements found Page 1 of 4 1 2 3 4 10 ly Created by Devon Manager on 10 30 13 2 26 PM Last changed by Devon Manager on 10 30 13 2 27 PM Back Figure 5 25 The Results Tab In both of these tabs the names of artifacts are links to the Details Pages of the artifacts The amp icon displays the Details Page of the corresponding test run or test result In the Test Runs tab Figure 5 25 reports may also be generated as described in Section 9 4 Test Runs 5 2 15 Change History y enterprise 7 edition i Feature only available in Klaros Testmanagement Enterprise Edition The Details section of each editable object in Klaros Testmanagement contains a Changes tab This shows the change history for the object Figure 5 26 shows the Changes tab for a test case 65 EI kS Execute pi Evaluate KN Configure Projects Iterations Requirements Test Environments Edited by John Doe on 1 8 14 11 07 44 AM Systems under Test Field Description Test Suites Precondition Edited by John Doe on 1 8 14 11 07 02 AM Field Description Edited by John Doe on 1 8 14 11 06 17 AM Field Name Edited by John Doe on 1 8 14 11 00 36 AM Field Name Edited by John Doe on 1 8 14 11 00 24 AM Field Name Edited by John Doe on 1 8 14 11 00 13 AM Field Steps Edited by John Doe on 1 8 14 10 59 58 AM Field Priority Edited by John Doe on 1 8 14 10 59 54 AM Field Execu
114. 0002 Version KLAROS 1 1 Created by Felix Mustermann Name SUT00003 Version KLAROS 1 2 Created by Felix Mustermann Figure 9 3 The SUT Overview Report Layout s Test Suite Overview The Test Suite Overview report shows the selected test suite containing its test cases de scription how many times it was executed and with what results An example report is shown in Figure 9 4 136 Evaluate EI Y klaros Test Plan Overview Y klaros Project KLAROS TESTMANAGEMENT P00001 Author Felix Mustermann Test Plans 3 Date Dec 1 2009 2 32 PM Name 1500001 Test Cases 5 Test Plan Runs 2 Description Login and Logout with Seam Securtiy Created by Felix Mustermann Test Case Team Created by Priority Shortname Name 1500002 Test Cases 4 Test Plan Runs 1 Description Creating a project environment and sut Created by Felix Mustermann Test Case Team Created by Priority Shortname Name 1500003 Test Cases 4 Test Plan Runs 1 Description Creating a new test case Created by Felix Mustermann Test Case Team Created by Priority Shortname Figure 9 4 The Test Suite Overview Report Layout The reports can be generated in three different file formats PDF e HTML e CSV Clicking on a file type icon generates the report will in the selected format 9 1 2 The Dashboard Reports The dashboard is a container for multiple reports Each report has the same structure It consists of a title bar and an area in which the report is dis
115. 002 Sprint 01 11 11 2013 10 00 fF 25 11 2013 10 00 PH 0 c BGE gt ITR00001 Setup phase 28 10 2013 10 00 a 29 10 2013 10 00 is 3 EE ES ID Name Start Date Due Test Runs Action Figure 6 8 The Iterations Screen The Iterations section shows all of the iterations defined for the current project Clicking on the table fields allows direct editing of the attributes The leftmost column allows iterations to be selected for bulk actions The uppermost check box is a global select button which selects or deselects all elements shown in the table Please note that the displayed elements are subject to the current search and catagorization criteria Iterations may be viewed on a printer friendly page as described in Section 5 2 6 Print Pages as well as categorized as described in Section 5 2 7 Categorization Clicking on the delete icon removes the Iteration 2 Why is the Delete button sometimes disabled Iterations that are referenced by test runs cannot be deleted so their delete icon is disabled Clicking on an edit icon displays the Iteration Details page of the corresponding iteration 6 2 1 Bulk Actions Some bulk actions are available on the Maintain Iterations page Bulk actions are described in Section 5 2 10 Bulk Actions The bulk actions available on this page are Edit Print Delete and Assign to Category The bulk action buttons can be found above the table on the left 6 2 2 Cre
116. 1 13 52 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT 1 KN na C TRU0000040 11 20 13 8 31 36 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT 1 ji SL Q gep C TRUO0000039 11 20 13 8 31 27 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT 1 B eR G TRUO0000038 11 20 13 8 31 16 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT 1 B ea G C TRU0000037 11 20 13 8 31 08 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT 1 E Q C TRU0000036 11 20 13 8 30 59 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT 1 E Q A C TRUO0000035 11 20 13 8 30 52 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT 1 aa 41 Elements found Page 1 of 5 1 2 3 4 5 K K 10 w Figure 9 15 The Test Runs Screen This page lists all test runs that have been executed in the selected project To get a better overview of the test runs the sorting and filtering functionality of the Filter Sort panel can be used as described in Section 5 2 5 Filtering and Sorting Pressing the delete icon removes the test run Note Deleting a test run will delete corresponding test case results and test suite re sults Clicking the icon displays the details of the test run E Deine e Plan Execute gal Evaluate KASET Swe ES Test Run TRU0000010 0 2 SNAP SHOT tomcat ad hoc 11 20 13 8 03 30 PM 2 E Dashboard Fiter Sort El 10 v Report Templates ID e Start Test Case Test Environment System under Test Executor Duration Result Details Test Run History TCR0000015 11 9 13 8 03 30 PM TC00003 tomcat ad hoc 0 2 SNAPSHOT John D
117. 1 15 3 36 PM EA i 3 30 15 10 30 AM HE E z lave S 3 30 15 10 23 AM z m 2 S Maximum F E Failure E Error z Average 3 24 15 11 17 AM EED i E Minimum Skipped 9 3 5 15 2 47 PM I K 0 1 2 3 0 12 Results 0 Developer local Solaris 11 Ubuntu 14 04 1 System under Test Produktion IDE integrated Windows 8 1 Staging 2011 11 tomcat ad hoc TE 0 2 SNAPSHOT 6 Created 2 years ago by Devon Manager Last changed 2 years ago by John Doe Back Figure 6 29 The Test Suite Overview Tab s Latest Test Runs This graph shows the number of passed failed erroneous and skipped test cases for the latest five test runs for this test suite e Execution Times of this Test Suite This graph shows the minimum maximum and average execution times for this test suite 101 Define Q This can be very useful in determining the estimated time needed for future executions of this test suite System under Test Overview This table shows the latest result of this test suite for every system under test and test environment this test suite has been executed in Hovering the mouse cursor over a single result will sho a more detailed overview of the individual test case results of this test suite Pressing the result will open up the appertaining test case result 6 7 3 2 Test Suite Properties 6 7 3 2 1 User Defined Properties edition Feature only available in Klaros Testmanagement Enterprise Edition ition gt User d
118. 10 14 The Mobile Device Connection Log Tab sss esse sese eee eee 169 10 15 the Miscellaneous Settings FAP see ENE EE ae EE ED ee Ge dee 169 10 16 The Notification Schemes Tab ee RE Ge EG Re ee eo ge 171 TOMA The Notiitations TaD sa 172 10 18 Assigning Projects to a Notification Scheme sese eee eee eee ee ee ee ee ee ee 172 10 19 The Interface Settings Va saa 173 10 20 The Languages Hap svare 174 10 21 The Issue Management Taiana 175 10 22 TAS Bug zllla Project ID 176 10 23 Tie R Project Dvs 177 10 24 The Mantis Project ID 177 10 25 The Reaimine Project ID ss SEE ES a E EEE ED ee 178 10 26 H L ET 179 10 2 Me Network Ta Descanse 180 10 28 Te DAPT NN 181 10 29 The LDAP Authentication POPUP EG EO ds 183 10 30 Te B TE 184 1031 The TRpPOr Tab sa 184 11 1 The Report Generation Process so 186 11 2 The Report Templates Page 4 187 11 3 The New Report Templates Page is is Se See Es bene iii nit 188 11 4 0 ea 0 Parameters san ii SE GREG ee er EE Oe RE er ESE Ee 189 1758 AD DIY a Report Ter plate AE 190 VEE PAra ME EI se SE DE ORE EG GE ED Pe RA OG EG EE de 191 TAPE GT lo PN 193 121 Test Case Excel SNE sample ED EE Ne a DE GE ED N 196 12 2 Requirement Excel Sheet Sample esec ecce eee eee Se ee Se ee Ne AG ee Gee Ge ee 200 12 3 Export Table Contentito PE se 208 XIV List of Tables 3 Stipported H ne see 12 3 2 SUPPEN DANSE Jarre 12 3 3 Supported External Issue Management SYSTEMS ese eee eee see eee eee eee eee 42
119. 12 1 General Property COONGINACCS ie is 197 12 2 Test Case Ste pC COON GIN ACES cuen 197 12 3 User Defined Property Coordinates esse sese cesses de ee de de de de ee de 198 12 4 General Property Coordinates sss ss ss ss ss ese ek ee ee Ne ee ee Sk AG ee be Ge 201 12 5 User Defined Property Coordinates esse sese eee eee eee ee de de de de ee AG dk de de 201 A 1 Role Permission Overview Table Klaros Testmanagement Community Edition 214 A 2 Role Permission Overview Table Klaros Testmanagement Enterprise Edition 214 A 3 Role Permission Overview Table Klaros Testmanagement Mobile Edition 214 Bl Tae enel TT 342 Colo BEEN SUIG ai 343 EDENS SS 345 SEE EE ENE ETE 345 GA REIER L ENE ve 345 E salirbutes de Save 345 COs contant ENN HSA 346 Ey WES FAS CS elements KO EO OE RE 346 ES stestcase NNN PN 346 EMNER ENN 347 D PEenen SMN id 351 ERT R RNI IEL lenene 552 KTR SIE elements RR ERE ES GE RE SE Ge Re 352 D conta er elements passe 352 D 3 re quirfements gt elements siria as 352 DOG sredtikemient ENER 352 Dto ers elements ss MEE EE H a 353 El COntext Vara DIE NR 355 XV List of Examples SA sampi UO S NN 32 3 2 Additional entries in mysdl cnf to support UTF 8 character Sets see eee eee eee 59 12 1 Excel Test Case Import via Command Line esse sees ecce eee eee eee 198 12 2 Excel Test Case Import via Command Line with authentication ees sesse ses ee 199 12 3 XML Test Case Import via Command L
120. 169 1051 Miscellaneous SeUINGS sv 169 19052 Noen Sen eiii ios 170 1055 10 ere SENGS Are 172 10 54 ale LTTE 174 VENNE 174 16 6 l 15506 Management as coa 174 EEE aceso 178 VES NNK 180 10 64 EDAP T 180 A SE AA EE NL OE EE RA EE aaa 183 VERD pe 183 OZ ga ole a RER EE RE esos EN 184 IE CUSCO e aia 186 111 Create A New Report Template aars 187 11 1 1 Supported Parameter Types iss ss eee 189 11 1 2 Dealin dit Rarameters TT 189 11 2 Applying a Report Template esec ece eee ce eee eee se eee 190 RE Example REDO EES eas ete N ee een A Gees GE Ge 191 11 3 Creating ME GrOOVY SU RS DE OR EE GE Ee Ee 191 11 3 2 Creating a SeamPDF Report Template ecce ecce eee ee ee de Se ee de 192 MAME A aa a S 192 viii Klaros Testmanagement User Manual Vis NTT ei s Ties IE AE HAR 194 11 3 5 Creating a SeamExcel Report Template eee eee se ee ee ee de 194 12 A DOPE BYTE anda 196 12 1 Importing Test Cases from Excel sss eee eee eee 196 12 Da A E 196 12 12 PrOFeQUISITOS mado Ree 198 12 1 3 PEN Ha 198 122 Importing Test Cases HOM AM E 199 12 2 GE EEE EET EE E RT ERE 199 12 4 2 BEIN FR 199 12 3 Importing Requirements from Excel esse eee ee eee eee eee 200 123 L 1APOFEEOFDA cojos 200 12 3 2 PreiedUulsites ses dia 201 12 35 es aldie ET ER RE 202 12 4 Importing and Synchronizing Requirements from XML eee ee eee eee eee 202 VL Feed 202 e 2 o A 203 AS a TT 203 125 Me KST e Test Results AN 205 125 Peres
121. 2 6 Print Pages as well as categorized as described in Section 5 2 7 Categorization Clicking on the delete icon removes the requirement Why is the Delete button sometimes disabled Requirements that are referenced by test runs cannot be deleted so their delete icon is disabled Clicking on an edit icon displays the Requirement Details page of the corresponding re quirement 6 3 1 Bulk Actions Some bulk actions are available on the Requirements page Bulk actions are described in Section 5 2 10 Bulk Actions The bulk actions available on this page are Edit Print Delete New Revision Duplicate and Assign to category The bulk action buttons can be found above the table on the left 6 3 2 Creating a Requirement Clicking onthe New button creates a new Requirement in the currently selected project Figure 6 13 The Name and Priority fields can then be specified The requirement ID is au tomatically assigned by Klaros Testmanagement 80 Define 6 3 3 Requirement Details 6 3 3 1 Requirement Overview EZ Define Plan 1 Execute L Evaluate y Configure 1 0 R00002 Reject invalid login TR gt MO N ET Back Projects iterations Overview Properties User Defined Attachments Test Cases 7 Revisions Results 3 Changes Test Environments al om Priority High Coverage 85 State Draft stems under Test z Automation Rate TEE Summary Ifthe user puts in an unknown usern
122. 2 SNAPSHOT 6 1ms Q Show all Figure 6 22 The Test Case Overview Tab e Execution Times of this Test Case This graph shows the minimum maximum and average execution times for this test case Tip This can be very useful in determining the estimated time needed for future executions of this test case 93 Define s Most unsuccessful Test Case Steps This graph shows all test case steps of this test case and which steps have been marked as failed or error during a test run Q N This graph can be used Tor determining possible misconfigurations if errors happen more freguently at one specific step for example System under Test Overview This table shows the latest result of this test case for every system under test and test environment this test case has been executed in Pressing the result will open up the appertaining test case result e Latest Results This table shows the latest results for this test case where the latest result is shown on the top 2 Note This table is limited to five entries The other issues can be viewed by pressing the Show All button e Latest Issues This list shows the latest issues which have been created in conjunction with this test case during test execution or linked to this test case after its creation 2 Note gt This table is limited to five entries The other issues can be viewed by pressing the Show All button 6 6 3 2 Test Case Properties This pa
123. 205 12 5 2 EE 205 12 6 Exporting Table Content to Excel ee Ge ee dk ee ee ee 208 12 7 BACKUD RECOV EN 208 GOS SM idol cas 209 A Role Permission OVENEN Jar 214 B Model APR EN BE ve 216 Bl APER NOE 216 B 1 1 de verit klaros core model sissies eee eee 216 B 2 SEriptind APl Relierefite dai 322 B2 1 deveritklaros SErIDUNG pss Ed oe es ee ee 322 B 2 2 de verit klaros scripting context css ecce eee eee AG ee dk 326 B 2 3 de verit klaros scripting CUStOM esec eee eee ee ee eee eee eee 330 B 2 4 de verit klaros scripting model scs 336 B 2 5 Constant field valli s ae 342 C Test Case Import Ele Specification es EG DE AS 343 E de ETE HE OON EE N EN 345 G2 SLBDE EE EET ET Ee Ee Ge 345 ES erdie AE RT EE RA ER EE EE untae 345 A ANNES gt cists DE SS Ee ee 345 Gea EE Ge SE Se NE EE never ee EE OD 346 EO ETT a 346 EEE ER N N 346 CeO TTS Se 347 Ed EE TTT 347 CIO NU TTT 347 CSR SON T 347 GE ig ee L EE EE 347 EI diealOPIE de dee EE E 348 ENN SR TE RE EER EE EE EE ico 348 Klaros Testmanagement User Manual ETE NNN NN 348 EO NE ne 348 ET ee 348 EMO NS 348 AS Y A A 348 20 E tata 348 EL SMED ds 349 22 NENNE 349 G23 eee REE EE EE ERE NE 349 24 Precndnion sae RS 349 EY ELO ENE EE EE EN EE 349 20 POONA Ee 349 ENO E ee ve od 349 GAS State as EV Re EER RE DR be EE Ao RE DE be GE 349 ZF LC MN EO Ee EG eee E 349 BO CACC AD NOY Je 350 GE Is Valle N SE eR Coe PD E Te 350 Coz NAME S A AA 350 ES o o ENE 350
124. 3 12 2 2 Redmine 2 0 and later The Klaros Testmanagement Redmine integration for Redmine 2 0 and later requires the in stallation ofthe Redmine Mylyn Connector 2 8 2 or later Please follow the installation notes which can be found at http danmunn github com redmine_mylyn_connector 3 12 2 3 Redmine 3 0 and later The Klaros Testmanagement Redmine Integration for Redmine 3 0 and later requires the installation of a patched version of Redmine Mylyn Connector 2 8 2 Please follow the instal lation notes which can be found at http danmunn github com redmine mylyn connector but use git github com joaopedrotaveira redmine_mylyn_connector git instead of the documented git github com danmunn redmine_mylyn_connector git command 3 12 2 4 Redmine common configuration Figure 3 16 Redmine Plugin Section shows the Redmine Plugin section after the successful installation of the plugin Search o Jump to a project v P lugi ns Administration d Projects amp Users Plugin must show up like this gt Groups 5 Roles and permissions kel Trackers wr Issue statuses sa Workflow Custom fields Enumerations wg Settings amp LDAP authentication amp Information Figure 3 16 Redmine Plugin Section 2 Note In order to use Klaros Testmanagement Redmine integration the Authentication Required and the Enable REST Web Service checkbox in the Authentication section of the Redmine settings must be checked Figure 3
125. 3 5 12 PM a a 0 Elements found Page 1 of 1 1 10 w Figure 9 11 User Defined Reports Screens 142 Evaluate If the user defined report is parameterized all required parameters must be entered to start the generation of the report _ a y A neira 4 GN ALE Plan 1 Execute pa Evaluate E Configure Sprin L E 7 Report Templates Le Hame Revision Description Changed By Changed Action Test Run Overview Report 1 0 Lists the Test Runs in a project grouped by selectable parameters admin 11 12 13 5 12 PM B EA WEEN Iteration PDF Overview Report 1 0 Lists a defined Iteration in a Project admin 11 12 13 5 12PM 8 2 TEN Job Excel Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM a te Job PDF Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM B EA a IIEEE 829 Testrun Deviation Report Template v1 1 0 IIEEE 829 Testrun Deviation Report Template v1 admin 11 12 13 5 12PM 8 2 AE ccc 820 Test Plan Template v1 1 0 IEEE 829 Test Plan Template v1 admin 11 12 13 5 12PM B 2 A EEE 829 Test Case Specification Template v1 1 0 IEEE 829 Test Case Specification Template v1 admin 11 12 13 5 12PM E 2 7 Elements found Page 1 of 1 4 1 10 vi New Please enter all needed parameters Iteration ID ITR00001 Generate Cancel Figure 9 12 Generate a parameterized Report Note The Generate button becomes
126. 5 Apply a Report Template Clicking on the or icon of a report template causes a PDF or Excel report to be rendered If the Groovy script was defined with parameters a pop up window will prompt the user to enter the defined parameters before the Report is generated 190 Custom Reports MEE O ND 7 Configure Sprint 1 2 Test GPS Tracking Report Templates Overview Kes E s Name Revision Description Changed By Changed Action Report Templates Test Run Overview Report 1 0 Lists the Test Runs in a project grouped by selectable parameters admin 11 12 13 5 12 PM 2 VEGER iteration PDF Overview Report 1 0 Lists a defined Iteration in a Project admin 11 12 13 5 12PM 8 2 B Mobile Devices Job Excel Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12PM BI 2 a System Job PDF Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM B 2 a IIEEE 829 Testrun Deviation Report Template v1 1 0 IIEEE 829 Testrun Deviation Report Template v1 admin 11 12 13 5 12 PM B 2 Integration IEEE 829 Test Plan Template vi 1 0 IEEE 829 Test Plan Template vi admin 11 12 13 5 12 PM B iaaa IEEE 829 Test Case Specification Template v1 1 0 IEEE 829 Test Case Specification Template v1 admin 11 12 135 12PM 2 7 Elements found Page 1 of 1 1 10 w New Please enter all needed parameters Iteration ID ITR00001 Generate Cancel Figure 11 6 Ent
127. 6 PM Test Case TCO0001 Log into system Test Run TRUOOOOOSS Test Environment ENVOOOO2 Windows 7 System Under Test SUTOODOS LadyPurse RC3 Executor Felix Mustermann Figure 9 30 The Test Suite Results Screen Print Test Results The results of the test suites are shown using the following icons s Ey The test finished successfully i A failure of the system under test has been detected An error occured during the test execution The test result could not be determined Clicking the icon starts a retest of the test suite 9 7 Issues With Klaros Testmanagement it is possible to link issues from external issue management systems like JIRA or Bugzilla with test cases In addition to this issues can be created from within Klaros Testmanagement and even during test execution 154 Evaluate 9 7 1 Issues by Test Case E Deine n Plan Execute pal Evaluate HALLO webapp E A Issues by Test Case Dashboard Filter Sort El 70 v Report Templates R ID Name Traceability Issues Action Test Run History TC00017 10 2 Q METER TC00004 1 1 IDE check 0 Q ESTARAS TC00004 1 0 IDE check 0 Q Test Suite Results TC00003 1 1 Continuous Integration check 0 Q Issues TC00003 1 0 Continuous Integration check 0 Q TC00002 1 0 Project setup check 0 Q TC00001 1 0 IDE check 0 Q ID Revision Name Traceability Issues Action 7 Elements found Page 1 of 1 1 70 Y Figure 9 31 The Issues by Test Case Screen This page
128. 69 Define gt Creating issue management systems Before issue management systems are available for assignment they must be created by an administrator For instructions on the creation of issue management systems see Sec tion 10 6 1 Issue Management The project properties page in the project details section Figure 6 2 The Project Properties Page shows two tables The upper table contains the issue management systems that are already in use in the project the lower table shows all issue management systems that are configured in Klaros Testmanagement and not in use by the project Pressing the add icon adds the corresponding issue management system to the project The issue manage ment system is removed from the lower table and added to the upper table Plan Execute Fi Evaluate X Configure Testing the emai client 2 P00002 Testing the email client a EE som K omr Iterations Properties User Defined Copy Objects Access Results Changes Requirements Test Environments Description Testing the email client Systems under Test z 3 Q Assigned Issue Management Systems Test Cases Assigned Issue Management Systems Available Management Systems le Test Suites Bugzilla Server Bugzilla JIRA Server Jira lssue Management System Integration e Trac Server Trac 34 Mantis Server Mantis fy Redmine Server Redmine GPS Testing O To assign issue management
129. 71 6 5 The Project Access AD E E 72 Gb Te PORS PO DUD TT 73 6 7 The Iteration and Project Selection Toolbar iese eee ee de ee 73 6 6 He R eT ee creed didas 74 69 The tera ion Verden Ta sitial la 75 6 OeTHedteratiom SUCCESS RATE a DS ES AAA 75 6 11 The Iteration Health Matrix sesse sesse sesse se se se se de se ee Se ee Ge ee ee Ge ee ee ee ee ee ee Ge ee ee 76 6 12 The Iteration Details Screen ad i n 78 613 The Requirements STEN ve 80 6 14 The Requirement Overview Tab rrrnnnnernnnnnnvnnrrnnnnnennnrnnnnuvnnnrnnennnnnnnnnennernnnnnnnnnsneee 81 6 15 The Requirement Details Screen issie eee ecce eee 83 6 16 The Test Environments Screen arrrnnnnrnrnnrnennnnennnnennnnennnnenennnnennnnennnnenennenennanennaneneene 84 6 17 The Test Environment Overview Tab rarnrnnnnannnnennnnannnnnnnnnnnennnnennnnennnnennnnenennenennener 85 6 18 The Systems under Test Screen sees eee eee eee eee 87 6 19 The System under Test Overview Tab sese eee ecce eee eee Ge AG ee be ee 89 6 20 TRE Test Case Issues STEM ve 91 621 TETEN Cases SEN aS 92 6 22 The Test Case Overview TID saa NSK 93 6 23 The Edit Test CASES STEM SS A A a Sa 96 624 The Edit Test steps STEN He 97 625 The Test Case Issues STENA 98 6 26 The Test Case JONS SEN Je 98 Sel METTES SEN 99 6 28 The Test Suite Details Screen rrannnnrnnnnrnnnnrnnnnnnennnnennnnennnnenennnnennnnennnnenennenennnnennene 101 6 20 Tn6 Test Suite OVERVIEW TED ua 101 6 50 Te TESE
130. AVA HOME nor the JRE HOME environment variable is defined Windows users will find an option to set this in their computer control panel The instructions to reach this vary with different versions of windows an example is shown below Linux users should set these variables in their startup scripts If you have installed a Java SDK you would set the JAVA HOME variable If your system only contains a Java Runtime JRE please use JRE HOME accordingly 3 2 2 2 Setting the JAVA HOME JRE HOME environment variable under Win dows s Go to Control Panel Find System Adjust your computer s settings D kh Fonts Intel PROSet Wireless Tools E Lenovo s Power Controls EL Network and Sharing aN Center R Performance Information and Tools id Programs and Features LI RemoteApp and Desktop A Connections a Windows CardSpace Windows Update it 7 Sa Installation Ed K Control Panel All Control Panel Items Getting Started Internet Options Location and Other Sensors Notification Area Icons Personalization QuickTime 32 bit Sound Taskbar and Start Menu Windows Defender Then go to Advanced system settings 14 ad Hc Jay NY LA Ph TT Re Installation ay d Control Panel All Control Panel tems System Control Panel Home ss View basic information about your compute Device Manager Windows edition dy Remote sett
131. Atlassian Pty Ltd see http www atlassian com e Mantis a free open source issue management system see http www mantisbt org e Redmine a free open source issue management system see http www redmine org e Trac a free open source issue management system see http trac edgewall org A Remote System Configuration may be Required Please refer to Section 3 12 Configuring External Issue Management Systems for detailed information on prerequisites for the different issue management systems Some systems need to be configured before they can be connected to These issue management systems are configured in the Issue Management section in the Configure menu The page is shown in Figure 10 21 The Issue Management Tab REN Overview Report Templates Users Mobile Devices Plan e Execute pi Evaluate E Configure Issue Management System Integration 2 Integration Issue Management E Mail Network LDAP 10 vw System Project Description Default Action IM00002 System Integration IM00003 IM00005 Backup IM00001 IM00004 amp Bugzilla v Bugzilla Server http devverit de bugzilla4 D a DI Trac v Trac Server http infosys verit de playground L a W Mantis v Mantis Server http infosys mantis D a Jira v Issue Management System Integration JIRA Server http infosys verit de jira D a fy Redmine v GPS Testing Redmine Server h
132. Backup To move data between different database installations or to selectively import data Klaros Testmanagement provides the functionality to import and export database content via XML files Only Administrators and Managers are able to import or export projects 10 7 1 Export Here it is possible to export selected project data The user can select one or more projects or click at the Select all option to select all the projects that are available Figure 10 30 183 Configure A Define Plan po Execute fm Evaluate E Configure issue Management System Integration Backup Overview Export Import Report Templates Users Fiter Sort al 10 v Mobile Devices ID Description Test Cases Test Runs Y P00005 Test GPS Tracking 3 3 System v P00004 Bestellprozess 2 0 Integration C P00003 Issue Management System Integration 1 0 P00001 Einrichten des neuen Rechenzentrums 2 0 ID Description Test Cases Test Runs Export Discard Figure 10 30 The Export Tab Clicking the Export button exports the selected projects to an XML formatted output file and clicking the Cancel button discards the selection Note Exported backup files carry a version number identifying the version of the data base that was exported Backup files may only be imported when the database version of the Klaros installation matches the version of the backup file 10 7 2 Import Here it is possible to import t
133. CategoryNode gt L I Methods inherited from de verit klaros core model KlarosCategoryTree getDescrip tion getRootNode getShortname Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 1 I TT S Sextends NamedEntity KlarosNamedEntity lt W P y a OE EE EK EIE EES E E er ay Ra E ESS Kal E Ha T SSS MOS SEES RES eee CST 1 W W extends KlarosCategoryTree lt l W P X Y gt I P Pextends CategoryTree X X extends KlarosCategoryNode lt I W X Y gt Y Y extends CategoryNode L KlarosCategoryTree lt KlarosSUTImplementation KlarosSUTImplementationCategoryTree SUTCategoryTree KlarosSUTImplementationCategoryNode SUTCateg ZN KlarosSUTImplementationCategoryTree B 1 1 56 KlarosTag This class encapsulates the tag information of a taggable klaros object B 1 1 56 1 Synopsis public final class KlarosTag extends KlarosWrapper lt KlarosTag Tag implements IKlarosTag Public Methods public Set lt KlarosRevision lt gt gt getRevisions public String getTagIdO pu
134. CategoryNode gt getExternalNames Set lt String gt getAttachments Set lt KlarosAttachment gt B 1 1 58 KlarosTestCaseCategoryNode A category node for test cases B 1 1 58 1 Synopsis public final class KlarosTestCaseCategoryNode extends KlarosCategoryNode lt KlarosTestCase KlarosTestCaseCategoryTree KlarosTestCaseCategoryNode TestCaseCategoryNode gt L Public Constructors public KlarosTestCaseCategoryNode TestCaseCategoryNode wrapped Public Methods 305 Model API Reference public List lt KlarosTestCase gt getReferences Methods inherited from de verit klaros core model KlarosCategoryNode getCatego ryTree getDescription getParent getShortname getSubCategories Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait AAA A i T T 1 W Wextends KlarosCategoryNode lt l T W P gt 1 P Pextends CategoryNode L KlarosCategoryNode lt KlarosTestCase KlarosTestCaseCategoryTree KlarosTestCaseCategoryNode TestCaseCategoryNode gt A KlarosTestCaseCategoryNode KlarosTestCaseCategoryNode wrapped TestCaseCategoryNode getReferences List lt KlarosTestCase gt B 1 1 58 2 KlarosTestCaseCategoryNode TestCaseCategoryNode public Klaros
135. Chapter 11 Custom Reports The following chapter covers user defined reports See Section 9 1 1 The Overview Reports on how to generate the pre configured overview reports that are included in Klaros Test management Community Edition saan Feature only available in Klaros Testmanagement Enterprise Edition With Klaros Testmanagement Enterprise Edition it is possible to define custom reports Though Klaros Testmanagement already provides several reports it might be helpful to de sign new reports that suite your and your customer s needs Figure 11 1 The Report Gen eration Process gives an overview of the report generation process As the report definition process is based on a Groovy or Java script and SeamPDF or SeamExcel basic knowledge in Groovy or Java programming and XML Conventions are helpful for a report designer Report Designer Query Script 7 3 Report Template lt gt Y Klaros Report Parameter User Figure 11 1 The Report Generation Process The reporting process involves two roles the Report Designer and the Report User While the report designer provides the structure of the report and prepares the report layout the report user applies the reports to the data collected in Klaros Testmanagement The report 186 Custom Reports designer has to provide a script and a template to build a report The guery script prepares the data and is implemented in Groovy or Java wh
136. Components A short summary of the issue The type of the issue e g a bug or an improvement The priority of the issue The components of the system that are affected multiple selections are allowed here Affected Versions The version of the system in which the issue appeared multiple se lections are allowed here Fixed Versions The version of the system in which the issue has been fixed Multiple selections are allowed here Due Date Description Test Environment Issue Management System Summary Issue Type Priority Components Affected Versions Fixed Versions Due Description Environment Mandatory fields must be filled Update Test Case State State Figure 8 15 Jira Issue Page The date when the issue should be fixed A longer description of the issue A description of the test environment in which the issue occurred IM00001 JIRA Server e E Bug Blocker Left Component Right component 20 a 1 0 20 a 10 20 11 2013 20 07 http Mlocalhost8080 klaros r web browse jsp type testCaseResult amp ENVO0005 tomcat ad hoc Save Back The following fields are available for the Trac issue management system The type of the issue e g a defect or enhancement Summary A short summary of the issue Issue Type Importance The priority of the issue 128 Components Version Milestone Description Keywords Execute The component of the s
137. D Requirement Import File Specification see ee eee eee eee ee ee eee eee 351 AAN CS si EE NE A GE 352 D 2 arnes S A 352 DE EA do ge N EE RE RE EE N EE oan 352 DAs SFEQUIFGIMOCN US Jar 352 D 5 TEOUE LT 352 DO SUMO GON RE EE di dci a 353 PAS o A AE ee OR RE DRS SE 353 DE R l len ER EES a EE EO N EG Eie 353 DERN 353 DIO ESPN aa 354 DAN EE EEE EE EE 354 EI TEU PS 354 DIS SONNE SS 354 D 14 SUNN ae 354 DAS names pvr 354 DAS Valle LS 354 E REDONUNG RESOURCES serca ridad 355 El COMLEXE Varlables EER SR SE N Ee ER Ee Ee OE SEE DE Ge eb ES 355 E 2 Klarosseript Interlaer se EN EG Ge ie Ee N ee ER Gie 355 ES Example report template SR EE EO RE EE i 355 ME 359 List of Figures 2 Nes CCAS E SINNES 5 22 NESE GaSe SN e EE OE RE TRE 5 ATEN 6 24 TESORUN wit Test RES UGS see 7 DES OES EE ER REE RE NN EEE ERE EEE REAR 9 26 Aas NENNE 10 IS STN 20 3 2 MOEN STEENS 21 5 5 LICENSING Agreement STEEN svarer 22 BAe TAP SEN ee 23 3 5 Select Installation Packages Screen esec ecce eee eee eee 23 CAR SE E aA 24 S J Installation in Progress SEE Aa 25 SSS BON BANEN SNE 25 3 9 Perform External Processes Screen ese eee eee eee 26 10 Se NOTE STEN se tt N Ee ee n We ie GR 27 311 INStallation Fini hed Screen Ree 28 3 12 Incompatible Installation detected issie ss ee AE Ee ee Ge ee Ak ee Ak 34 SP ie ie SEM SE oo EE EO OR HE NO NEE AT EG 34 3 14 Database M NS 35 3 15 Additional Tomcat memory settings sissies sesse se Ne ee Se ee S
138. D or for a fully featured full text search in the current selected project These are described in the following sections is John Doe Administrator veril informationssysteme Figure 5 6 The Search Field 5 2 3 1 Full Text Search Ca edition y Feature only available in Klaros Testmanagement Enterprise Edition The Search field allows the user to search for object ids or words or phrases contained in fields of objects This search function uses Apache Lucene which provides a powerful syn tax for searching individual fields or with wildcards This syntax is described on the Apache Lucene website 52 Functional Overview 7 Define amp ran ES Execute q Evaluate y Configure Iterations Requirements Test Environments Systems under Test Test Cases Test Suites Search Results Job 2 System under Test 3 Test Case 1 User 1 1 JOB00001 Test the file upload of the ticket system FreeBSD Issue Management System Inte L A Summary Test the file upload of the ticket System FreeBSD 2 JOB00002 Test the file upload of the ticket system OpenBSD Summary Test the file upload of the ticket System OpenBSD Figure 5 7 The Search Results Page Figure 5 7 shows the Search Results page This page displays each object containing the search term and highlights the occurrences Figure 5 8 shows the message which appears in the log panel upon completion of a search Q The search fini
139. Define Z Plan X Execute q EEC 7 Configure Issue Management System Integration SA amp 2 EJ xT 1032 SE Overview Report Templates x Properties Results Connection Log Changes sers Mobile Devices Test Case Results Test Suite Results Test Runs System 3 Fiter Sort El 10 v ee ID e Start Test Run Test Case Test Environment System under Test Executor Duration Result Action Backup TCR0000013 6 16 14 11 05 43 AM TRU0000012 TC00001 FreeBSD 9 2 Ticket System v1 55 Erika Mustermann 00 00 05 TCR0000012 6 16 14 11 05 43 AM TRU0000012 TC00001 FreeBSD 9 2 Ticket System v1 55 Erika Mustermann 00 00 08 TCR0000011 6 16 14 11 04 09 AM TRU0000011 TC00001 FreeBSD 9 2 Ticket System v1 55 Erika Mustermann 00 00 06 TCR0000002 6 16 14 10 58 24 AM TRU0000001 TC00001 Windows 8 1 CANON Pixma MG5150 Erika Mustermann 00 00 05 TCR0000001 6 16 14 10 58 24 AM TRU0000001 TC00002 Windows 8 1 CANON Pixma MG5150 Erika Mustermann 00 00 06 OG Q Created by Erika Mustermann on 6 16 14 10 58 AM Last changed by Erika Mustermann on 6 16 14 11 05 AM Back Figure 10 13 The Mobile Device Results Tab The Connection Log tab displays the connection log for the mobile device It shows the time and user name used for each synchronization of this device with Klaros Testmanagement Clicking the user name opens up the user details page for this user 168 Report Templates g Nexus Properties Results Connection Log Changes Configure User
140. Gets the category tree Parameters return the category tree B 1 1 2 3 getDescription public abstract String getDescriptionO Gets the description Parameters return the description B 1 1 2 4 getParent public abstract W getParent Gets the parent category node Parameters return the parent B 1 1 2 5 getReferences public abstract List lt I gt getReferences Gets the references of this category Parameters return the references B 1 1 2 6 getShortname public abstract String getShortname 218 Model API Reference Gets the shortname Parameters return the shortname B 1 1 2 7 getSubCategories public abstract List lt W gt getSubCategories Gets the sub categories Parameters return the sub categories B 1 1 3 IKlarosCategoryTree A generic category tree B 1 1 3 1 Synopsis public interface IKlarosCategoryTree lt I W extends KlarosCategoryTree lt I W P X Y gt P extends CategoryTree X extends KlarosCategoryNode lt I W X Y gt Y extends CategoryNode gt extends IKlarosNamedEntity Public Methods public abstract String getDescriptionO public abstract KlarosCategoryNode lt I W X Y gt getRootNode public abstract String getShortname 219 Model API Reference B 1 1 3 2 getDescription public abstract String getDescription Gets the description Parameters return the description B 1 1 3 3 getRootNode public abstract KlarosC
141. Help Playground Project 3 Overview Activity Roadmap Issues Mew issue Gantt Calendar News Documents Settings Information Modules Members Versions Issue categories Wiki Repository Forums Name Playground Project 3 30 characters Maximum lil Description g y UNS C alles EIE pe os BM Playground Project Identifier playground3 Homepage Public Figure 10 25 The Redmine Project ID 10 6 1 1 Adding a new Issue Management System To add a new issue management system click the New button An empty row will be added to the list of issue management systems Clicking the Save button submits the changes while clicking the Cancel button dis cards them 10 6 1 2 Editing an existing Issue Management System The configuration of an issue management system can be changed by editing the fields in the table Clicking the Save button submits the changes while clicking the Cancel button dis cards them 10 6 1 3 Deleting an Issue Management System If the issue management system is not used in any project it can be deleted by clicking the delete button of the entry in the table for configuration of the issue management systems 10 6 2 E Mail In the E Mail tab it is possible to change the e mail server settings of the application The E Mail server settings are required for sending notification emails configured in Section 10 5 2 i Notification Settings The attributes which can be ed
142. IRpcPlugin After successful installation of the plugin it has to be activated using the Trac web administration interface Figure 3 18 Trac Plugin Section shows the Trac Plugin section after the successful installation of the plugin 44 Installation Search logged in as admin Logout Preferences Help Guide About Trac RPC API Administration Manage Plugins Install Plugin RET Trac 0 12 File General i ER Basic Settings NN NNN No file selected set Upload a plugin packaged as Permissions Jploac ug ckaged as Plugins gt TracAccountManager 0 3dev r9591 Python egg Ise ent plugin for Trac Ticket System Install Components Milestones Priorities Resolutions Severities Ticket Types Versions gt TracXMLRPC 1 1 0 r9171 TracHTTPAuth 1 1 intManag plugin to provide HTTP auth tication T Trac itself Version Control Repositories Plugin must show up like this ij trac Figure 3 18 Trac Plugin Section To make the plugin accessible authenticated users must be able to access the XML_RPC plugin as shown below veril _Search informationssysteme logged in as admin Logout Preferences Help Guide About Trac RPC API ikt Timeline Roadmap Browse Source View Tickets New Ticket Admin Administration Manage Permissions Grant Permission General Subject Action Subject Basic Settings admin 7 TRAC_ADMIN Logging Action BROWSER VIEW Permissions anonymous F BRO
143. Iterations Requirements Systems under Test Test Environments Test Cases and Test Suites The categorization panel is opend by clicking the Categories link above the table in question In the categorization panel users may create Category Groups and Categories Objects may be assigned to one category in each group There is no limit on the amount of categories or category groups which can be created In order to apply categorization the Categories panel must be open The Categories panel contains 3 different views the Edit view the Tree view and the Menu view If no categories have been defined only the edit view can be used Each view allows selection of the active category group through the use of a dropdown menu or selection of the blank category group to disable categorization 57 Functional Overview 5 2 7 1 The Edit View EZ Define E Plan Ti Execute pm Evaluate y Configure Test Cases Projects Iterations A SP Accepted v TOE Test Environments Name Accepted Requirements Systems under Test AGP Z28 A der 28 Management Test Suites dr d ZB Department ASP ZA Development E Revision Traceability OJ Tco0003 a 1 0 Continuous Integration check Medium Approved Manual 2 2 EE O 71000002 a 1 0 Project setup check High Locked Manual 1 2 EE O Tco0001 a 10 IDE check Low Draft Manual 2 au Revision Traceability Priority Execution Steps Action Figure 5 13 The Categorizati
144. Klaros Testmanagement User Manual Version 4 3 11 Publication date December 16 2015 veril informationssysteme Copyright 2009 2015 verit Informationssysteme GmbH Klaros Testmanagement User Manual by Selcuk Akgunlu Caroline Albuquerque Sabrina Gidley Fabian Klaffke Claudia K nnecke Klaus Mandola Patrick Reilly Tobias Schmitt Torsten Stolpmann and Heiner Westphal Version 4 3 11 Publication date December 16 2015 Copyright O 2009 2015 verit Informationssysteme GmbH Abstract This document serves as the reference documentation for the Klaros Testmanagement applica tion It gives a detailed description of the user interface and the provided functionality Legal Notice Copyright 2009 2015 verit Informationssysteme GmbH Europaallee 10 67657 Kaiserslautern Germany All rights reserved This product or document is protected by copyright and distributed under licenses restricting its use copying distribution and decompilation No part of this product or documentation may be reproduced in any form by any means without prior written authorization of verit Informationssysteme GmbH and its licensors if any Trademarks ZA Oracle Java and Solaris are trademarks of Oracle and or their affiliates Microsoft Excel SQLServer and Windows are either registered trademarks or trademarks of Mi crosoft Corporation in the United States and or other countries JIRA is a registered trademark of Atlassian
145. KlarosIssue extends KlarosWrapper lt KlarosIssue Issue gt implements IKlarosIssue Public Methods public KlarosSUTImplementation getAcceptediInO public Date getCreationDate public String getDescription public String getExternalld public Date getLastSynched public String getOwnerO public String getPriorityO public String getReporterO public String getResolution public String getState public String getSubjectO public Set lt KlarosTestCase gt getTestCases Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 283 Model API Reference getExternalld String get TestCases Set lt KlarosTestCase gt getAcceptedlni KlarosSUTImplementation getDescription String getCreationDate Date getPriority String getResolution String getState String getLastSynched Date getOwner String getReporter String getSubject String B 1 1 39 KlarosIteration An iteration in a project B 1 1 39 1 Synopsis public final class KlarosIteration extends KlarosNamedEntity lt KlarosIteration Iteration gt implements IKlarosIteration Comparable lt KlarosIteration gt Public Methods public int compareTo KlarosIteration o public boolean equals Object o public Set lt KlarosAttachment gt getAttachmentsO
146. Name Users Mobile Devices Ls 11 6 13 9 51 46 AM tester System 11 6 13 9 51 07 AM tester Integration 11 6 13 9 50 49 AM tester2 Backup 11 6 13 9 22 53 AM tester 11 6 13 9 22 50 AM tester Created by Erika Mustermann on 11 6 13 9 22 AM Figure 10 14 The Mobile Device Connection Log Tab 10 5 System Test GPS Tracking Ta L ek Back Status Ok Device deactivated Authentication failed Ok Ok Last changed by Erika Mustermann on 11 6 13 9 51 AM Back This page contains the settings for the appearance and behavior of Klaros Testmanage ment It contains four tabs Miscellaneous Notifications Interface and Languages Clicking the Save ties file and clicking Cancel 10 5 1 Miscellaneous Settings E Define Plan X Execute qa Evaluate E Configure System Overview BAAN Miscellaneous Interface Languages Report Templates Application URL Users Y Check Application URL Mobile Devices integration Maximum Upload File Size Byte 9223372036854775807 Backup Use the default container session timeout Y Session Timeout Minutes 30 Authentication required for import O Create test suite results when importing test case results Only administrators may create users O Testers may only execute tests via a related job O Testers may only resume jobs assigned to them O Figure 10 15 The Miscellaneous Settings Tab Ho button persists the changes to the Klaros Testmana
147. O public abstract String getDuration public abstract Long getDurationInMilliseconds public abstract String getEstimatedTimeLeft public abstract Long getEstimatedTimeLeftInMilliseconds public abstract KlarosJob getJob public abstract KlarosTestRun getTestRun 233 Model API Reference B 1 1 11 2 getDescription public abstract String getDescription Gets the work description Parameters return the work description B 1 1 11 3 getDoneAt public abstract Date getDoneAt Gets the date this work was done at Parameters return the start date B 1 1 11 4 getDuration public abstract String getDuration Gets the work duration as a String Parameters return the duration B 1 1 11 5 getDurationInMilliseconds public abstract Long getDurationInMilliseconds Gets the work duration in milliseconds Parameters return the work duration in hours B 1 1 11 6 getEstimatedTimeLeft public abstract String getEstimatedTimeLeft 234 Model API Reference Gets the estimated time left for this job as a String Parameters return the estimated time left B 1 1 11 7 getEstimatedTimeLeftInMilliseconds public abstract Long getEstimatedTimeLeftInMilliseconds Gets the estimated time left for this job in milliseconds Parameters return the estimated time left in hours B 1 1 11 8 getJob public abstract KlarosJob getJob Gets the job this job time block belongs to Parame
148. OO 4 2 Page 1 7 Z Figure 9 18 The Single Test Run Report 146 Evaluate Mavigate to project et page Click He selection bution an the e of fe table for Sre project Havigate to the executs best case selection pags Fassa Mo button The execute button does not appear beside the fest case Click tht assets lsdisror button BE necessary to complete the fest cape aklooed Figure 9 19 The Single Test Run Report continued 9 5 Test Case Results The Test Case Result screen shows results for individual test cases The total number of passed failed error and skipped results for each test case is shown Figure 9 20 To get a better overview of the test cases the sorting and filtering functionality of the Filter Sort panel can be used as described in Section 5 2 5 Filtering and Sorting This screen displays an overview of the test cases for the project To narrow the search the filtering and sorting functionality of the page can be used The latest result of a test case is displayed in the column E Deine e Pian ZL Execute EI Evaluate y Configure WebAps F L Test Case Results Dashboard Fiter Sort El 70 vw Report Templates Revision Traceability i KELLER DO TC00001 10 IDE check 25 am amp Q EGTER 0 TC00003 Y 10 Continuous Integration check 20 EN EN C ea Test Case Results TC00002 1 0 Project setup check 5 Test Suite Results Issues Figure 9 20 The Test Ca
149. Open EA D PLAYGROUND 5369 IM00001 0 2 This is a test issue 11 27 2010 hudson hudson Blocker Open Fi D 278 P IM00003 0 4 Cannot open the main page of the web application 11 26 2009 admin admin blocker new Fi D New Link Refresh Created 2 years ago by Ted Steve Manager Last changed 5 days ago by John Doe Back Figure 6 25 The Test Case Issues Screen This tab lists all issues that have been linked to this test case Pressing the New button opens the Issue Details page Section 9 7 2 Issue Details Creating a new Issue where new issues can be created and linked to this test case By pressing the Link button it is possible to link existing issues to this test case Section 9 7 3 Link Issues 6 6 3 8 Jobs Plan 1 Execute L Evaluate X Configure WebApp L A 5 Tc00002 Project setup check a E Projects Back Ite rations Overview Properties User Defined Steps 1 Attachments Revisions Issues Jobs 2 Results Changes Requirements Test Environments Filter Sort amp 70 v Systems under Test ID Summary Priority Status Progress Success Due Assignee Action JOB00010 w Minor New 0 25 11 2013 00 00 ff John Doe v Za Test Suites 40800003 A Major Resolved BE 06 11 2013 18 00 Susan Dev v Zo Created 2 years ago by Ted Steve Manager Last changed 2 months ago by John Doe Back Figure 6 26 The Test Case Jobs Screen This tab lists all jobs in which this testcase is included These jobs can be directly executed fr
150. Requirement gt getReduirementsO Returns the project requirements Parameters return Set containing the requirement objects of the project B 1 1 4 9 getSuts public abstract Set lt KlarosSUTImplementation gt getSutsO Returns the project SUTs systems under test Parameters return KlarosSet containing the SUT objects of the project B 1 1 4 10 getSystemUnderTestCategoryTrees public abstract Set lt KlarosSUTImplementationCategoryTree gt getSystemUnderTestCategoryTrees Returns the project system under test category trees Parameters return Set containing the system under test category trees of the project 222 Model API Reference B 1 1 4 11 getTestCaseCategoryTrees public abstract Set lt KlarosTestCaseCategoryTree gt getTestCaseCategoryTrees Returns the project test case category trees Parameters return Set containing the test case category trees of the project B 1 1 4 12 getTestCases public abstract Set lt KlarosTestCase gt getTestCases Returns the project test cases Parameters return Set containing the test case objects of the project B 1 1 4 13 getTestEnvironmentCategoryTrees public abstract Set lt KlarosTestEnvironmentCategoryTree gt getTestEnvironmentCategoryTrees Returns the project test environment category trees Parameters return Set containing the test environment category trees of the project B 1 1 4 14 getTestRuns public abstract Set lt KlarosTestRun gt
151. S New Created 1 year ago by John Doe Last changed 1 year ago by John Doe Back Figure 5 22 The Test Suite User Defined Tab The values of user defined properties for test runs are set in the execute dialog as shown in Figure 8 3 5 2 12 Attachments Attachments may be uploaded and linked to certain objects within Klaros Testmanagement This can be done within the Attachments tab on the relevant details page or during execution of a test case Clicking the Upload Attachment button opens the upload attachment dialog Clicking the Browse button opens the Open File dialog which allows the user to select a file to upload Clicking the Upload button uploads the selected file to Klaros Testmanagement 63 Functional Overview 2 Plan dj Execute pi Evaluate X Configure Issue Management System Inte A p 1 0 TC00001 Testing the file upload of the ticket system E ed Projects Iterations l Properties User Defined Steps Attachments Revisions Results Changes Requirements Name Size File Type Version Created By Action testxml bd 14 16KB text plain charset ISO 8859 1 1 0 John Doe 2 a Test Environments Systems under Test eee Test Suites Created by John Doe on 10 29 13 10 35 AM Last changed by John Doe on 11 19 13 4 50 PM Back Figure 5 23 The Assign Attachments Screen After the attachment is saved it is possible to download the file by clicking on the icon Clicking on the 4 icon cause
152. SUE ODS STEEN 102 LA Hie Maintain Jobs STEEN sele GN 104 EZ Te ob Overview Tab jer ii didas 106 PN NN NN 108 LANE OD Details STN EDE E A DE ie ke 109 7 5 The Add a Comment DialOG sisie a GE EG GE ee GE de GE Es Ge 110 7 6 The bod NRK DAN is EI De nares 111 7 1 The ODS Tom Test Cases STEEN Lasse 111 2 8 The Jobs trom Test Suites Screen se ese A dica 112 TO TRE JOOS by User STEN HR 112 210 Th Jobs BY User STEEN JE 113 8 The MOS SEN RPR 114 8 2 Tlie RUM TEST CASE SEN sr S 115 8 3 The Single Test Case Execution Dialog issie sesse ke Ee ee Sk ee Ge AG ee eg 115 8 4 The Step by step Instructions VIEW issie sesse se ee eee Ee Ek AG ee Ne ee Ge AG ee 116 xii Klaros Testmanagement User Manual 8 5 he Tapular Step Instructions STEEN ER EE EE N RE Ge Ee Oe ED 117 8 6 The Error or Failure Detected Dialog esse sese 119 8 7 The Test Case Results STEEN 4 120 8 8 The Run Test Suite Screen eee eee eee eee 120 8 9 The Detailed Information about the Test Suite Screen sese eee eee eee de ee de 121 8 0 Tie Overvlew STE vare 122 S A The Test Suite Results an Ve 123 8 12 The Continue Test RUN STEEN ss EE RS Ee AE ED ge EE N EE GO be 124 S 18 MPO Results PIE NNN 126 8 14 The Import Test Results Page orrrnnnnernnnrnnennrrnnrnnvnnnrnnnnennnnrnnennnnnnnnnennennnnnnnnneeneee 127 ASA Ie PS 128 15 TESE Pad RR 129 8 17 Reamine Issue Padel 130 818 BUG 15546 PaE 4 131 1 Mantis ISSUC PIGE PP 132 8 20 Creating a Rev
153. StepResult gt getStepResultsO public abstract String getSummary public abstract KlarosTestCase getTestCase public abstract KlarosTestRun getTestRun public abstract Integer getTestSuitePosition public abstract KlarosTestSuiteResult getTestSuiteResult public abstract boolean isErrorO public abstract boolean isFailureO public abstract boolean isPassed public abstract boolean isPending public abstract boolean isSkippedO B 1 1 22 2 getAttachments public abstract Set lt KlarosAttachment gt getAttachments 258 Model API Reference Gets the attachments associated with this test case result Parameters return the attachments B 1 1 22 3 getDescription public abstract String getDescription Get the test result description This is usually set for failed error status results Parameters return The test result description B 1 1 22 4 getExecutionTime public abstract long getExecutionTimeO Get the test execution time in ms Parameters return The test execution time B 1 1 22 5 getStepResults public abstract List lt KlarosTestCaseStepResult gt getStepResultsO Get the associated step results Parameters return List of test case step results B 1 1 22 6 getSummary public abstract String getSummary Get the test result summary This is usually set for failed error status results Parameters return The test result summary B 1 1 22 7 getTestCase public abst
154. String getRole public String getUsername public int hashCode public String toStringO Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 321 Model API Reference getEmail String getUsername String getRole String compareTo o KlarosUser int equals o Object boolean hashCode int toString String B 2 Scripting API Reference B 2 1 de verit klaros scripting B 2 1 1 KlarosContext Context to provide all methods to the user to add own objects to the event context B 2 1 1 1 Synopsis public class KlarosContext implements IKlarosContext Public Constructors public KlarosContext Context context UUID activeProjectId UUID activelterationld KlarosQueryFactory factory ParameterContext parameters public KlarosContext Context context UUID activeProjectld UUID activelterationld KlarosQueryFactory factory ParameterContext parameters Locale locale Public Methods public void add String name Object value public List lt gt executeParameterizedQuery String query public List lt gt executeQuery String query public KlarosIteration getActivelt
155. Test The system under test for which this job should be executed Test Environment The test environment in which the job should be executed E Detine amp Pian ES Execute q Evaluate y Configure Testing the E Mail client FE amp Q The Job JOB00001 has been successfully saved x Maintain Jobs ma JOB00001 Test the file size limitation when attaching large files to emails 62828 A Jobs from Test Cases Back Jobs from Test Suites Jobs by User Overview Properties User Defined Attachments Results Comments Work Log Changes ID JOB00001 Type Test Execution x Execution Manual Summary Test the file size limitation when attaching large files to emails Description There is a configurable file size limit when attaching files to emails When uploading a file whose size exceeds this limit a warning message should be displayed to the user and the operation should be cancelled Priority a Major Status New lt Estimated Time 00 30 00 Progress 0 Start Date 24 05 2015 00 00 7 Due 29 11 2015 12 00 FA Assignee Erika Mustermann Test Case TCO0001 Test the file size limitation when attaching large E B ES files to emails pen System under Test email client Test Environment Ubuntu 13 04 Created 2 years ado by John Doe Last changed moments ago by John Doe Back Figure 7 4 The Job Details Screen 109 Plan It is possible to assign a test case or test suite to a job but only if the job does no
156. TestCaseCategoryNode TestCaseCategoryNode wrapped Instantiates a new klaros test case category node Parameters wrapped the wrapped class B 1 1 59 KlarosTestCaseCategoryTree A category node for test cases B 1 1 59 1 Synopsis public final class KlarosTestCaseCategoryTree extends KlarosCategoryTree lt KlarosTestCase KlarosTestCaseCategoryTree TestCaseCategoryTree KlarosTestCaseCategoryNode TestCaseCategoryNode gt Methods inherited from de verit klaros core model KlarosCategoryTree getDescrip tion getRootNode getShortname Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty 306 Model API Reference Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait I TT 8 Sextends NamedEntity KlarosNamedEntity lt W P gt A SE EE DEER EIN OER EE N i EI I W W extends KlarosCategoryTree lt l W P X Y gt I P P extends CategoryTree y X X extends KlarosCategoryNode lt l W X Y gt 1 Y Y extends CategoryNode L P KlarosCategoryTree lt KlarosTestCase KlarosTestCaseCategoryTree TestCaseCategoryTree KlarosTestCaseCategoryNode TestCa
157. TestRuns Set lt KlarosTestRun gt getCategories Set lt KlaroslterationCategoryNode getAttachments Set lt KlarosAttachment gt compareTo o Klaroslteration int equals o Object boolean hashCode int B 1 1 40 KlarosIterationCategoryNode An category node for iteration implementations 285 Model API Reference B 1 1 40 1 Synopsis public final class KlarosIterationCategoryNode extends KlarosCategoryNode lt KlarosIteration KlarosIterationCategoryTree KlarosIterationCategoryNode IterationCategoryNode gt Public Constructors public KlarosIterationCategoryNode IterationCategoryNode wrapped Public Methods public List lt KlarosIteration gt getReferences Methods inherited from de verit klaros core model KlarosCategoryNode getCatego ryTree getDescription getParent getShortname getSubCategories Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait PT SS SO TT W W extends KlarosCategoryNode lt l T W P gt I P Pextends CategoryNode y L KlarosCategoryNode lt Klaroslteration KlaroslterationCategoryTree KlaroslterationCategoryNode IterationCategoryNode gt A KlaroslterationCategoryNode KlaroslterationCategoryNode wrapped IterationCategoryNode getReferences List lt Klaroslteration gt B 1 1 40 2 KlarosIte
158. Time ms gt P Note Make sure to escape characters like amp lt or gt when using them in XML attributes in the report template 11 2 Applying a Report Template To apply a report to your test data click on the Evaluate icon and select Report Templates from the menu on the left side A list of available report templates will be provided for se lection Plan Execute Pl Evaluate E Configure Issue Management System Integration 75 A Report Templates Revision Description Changed By Changed Report Templates Test Run Overview Report 1 0 Lists the Test Runs in a project grouped by selectable parameters admin 41 12 13 5 12 PM 78 Users Iteration PDF Overview Report 1 0 Lists a defined Iteration in a Project admin 11 12 13 5 12 PM EA a Mobile Devices Job Excel Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM El EA a System Job PDF Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM 2 a IIEEE 829 Testrun Deviation Report Template v1 1 0 IIEEE 829 Testrun Deviation Report Template v1 admin 11 12 13 5 12 PM 2 a Integration IEEE 829 Test Plan Template vi 1 0 IEEE 829 Test Plan Template vi admin 11 12 13 5 12 PM a a Ee IEEE 829 Test Case Specification Template v1 1 0 IEEE 829 Test Case Specification Template v1 admin 11 12 13 5 12 PM 2 a 0 Elements found Page 1 of 1 1 10 w Figure 11
159. TimeBlock JobTimeBlock gt implements IKlarosJobTimeBlock Comparable lt KlarosJobTimeBlock gt Public Methods public int compareTo KlarosJobTimeBlock o public boolean equals Object o 289 Model API Reference public String getDescription public Date getDoneAt public String getDurationO public Long getDurationInMilliseconds public String getEstimatedTimeLeftO public Long getEstimatedTimeLeftInMilliseconds public KlarosJob getJobq public KlarosTestRun getTestRun public int hashCode Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait I I KlarosJobTimeBlock getDescription String getDoneAt Date compareTo o KlarosbbTimeBlock int equals o Object boolean hashCode int getDurationInMilliseconds Long getEstimatedTimeLeftInMilliseconds Long getDuration String getEstimatedTimeLeft String getbb Klarosbb getTestRun KlarosTestRun B 1 1 44 KlarosjobUpdateAction The model of a job comment B 1 1 44 1 Synopsis public final class KlarosJobUpdateAction extends KlarosWrapper lt KlarosJobUpdateAction JobUpdateAction gt implements IKlarosJobUpdateAction Comparable lt KlarosJobUpdateAction gt Public Methods public int compareTo KlarosJobUpdateAction o public boolean equals Object o
160. Tracking Restricted Notification Issue Management System Integration Target Action Integration Job Assigned jnee di Testing the E Mail client Backup Account Created oP Account Password Chang db le Created 2 minutes ago by Johr Last changed moments ago by John Doe e Assign Projects p Save Discard gt Assign Cancel Figure 10 18 Assigning Projects to a Notification Scheme 10 5 3 Interface Settings This tab contains settings which govern the behavior of the user interface in Klaros Test management 172 Configure E Define Z Plan oe Execute pa Evaluate E Configure System Overview Miscellaneous Notifications Interface Languages Report Templates Test Runner starts in tabular view E Users Show test case information during test execution system Test step editing starts in the tabbed view mode F Integration Rows per table page 15 Backup Quote of the day Use random quote of the day quotes tt Upload Quotes Figure 10 19 The Interface Settings Tab The following settings can be controlled here Test Runner starts in tabular view If true the testrunner will per default show the tabluar view Show test case information during test execution If true the test case detail information panel is always expanded per default when launch ing or executing tests Test step editing starts in the tabbed view mode If true the default view in the Steps tab in the Test Case Detail
161. WSER VIEW F CHANGESET VIEW Plugins FILE VIEW FP LOG VIEW Grant permission for an action to a M MILESTONE VIEW REPORT SQL VIEW subject which can be either a user or Ticket System 7 REPORT VIEW P ROADMAP VIEW ks Components SEARCH VIEW F TICKET VIEW Milestones FT TIMELINE VIEW M WIKL VIEW Add Priorities s Resolutions authenticated TICKET CREATE TICKET MODIFY sg F WIKI CREATE CF WIKI MODIFY c l f Severities Add Subject to Group 7 ML RPC Ticket Types kant Versions tester M authenticated oe Version Control westphal Pf TRAC ADMIN Group Repositories Add a user or group to an existing Remove selected items permission group Note that Subject or Group names can t be all upper cas permission names D as that is reserved for Add Make sure that the XML RPC rights are given to authenticated users at tra N POWERED Figure 3 19 Trac Permissions Section The following combinations have been successfully tested e Trac 0 12 TracXMLRPC 1 1 0 Later versions are expected to work but currently not tested 45 Installation 3 13 SSL Support Note on self signed certificates If you are accessing HTTPS servers with self signed certifi cates you will need to import those certificates into your Java trusted keystore One instruc tion on how to achieve this can be found at http stackoverflow com questions 2893819 telling java to accept self signed ssl certificate 3 14 Uninstall To u
162. able on the Maintain Jobs page Bulk actions are described in Section 5 2 10 Bulk Actions 104 Plan The bulk actions available on this page are Edit Delete Duplicate Assign to Parent and if viewing sub jobs Move to new Position and Move up one Level The bulk action buttons can be found above the table on the left 7 1 2 Creating Jobs Clicking the New button creates a new job in the selected project Figure 7 1 The job ID is automatically assigned by Klaros Testmanagement The Summary Priority Due Date and Assignee fields can be specified here The new job must be persisted by clicking the Save button 7 1 3 Arranging Jobs Jobs can be arranged using the arrow icons in the Arrange column The icon opens a dialog which allows the user to move the job to a new position and the lt j and icons change the job hierarchy Using the lt j icon will put the job in the same hierarchy level as its parent job Using the opens a dialog which allows the user to choose a new parent job from the job s siblings Parent Jobs have specific features A parent job can not be assigned to any test case or test suite A parent job can also contain multiple parents with subordinated jobs If the arrow key on a parent is gray this means there is no other job parent available To subordinate a job create a job of type Task that does not have a test case or test suite Then select a job that should be subordinated by clicking t
163. ailed results have a property type with the value F Parameters return The number of failed test cases B 1 1 28 8 getNumberPassed public abstract int getNumberPassed 270 Model API Reference Get number of passed test cases of this test run It is assumed that passed results have a property testCasePassed with value true Parameters return The number of passed test cases B 1 1 28 9 getNumberSkipped public abstract int getNumberSkipped Get number of skipped test cases of this test run It is assumed that failed results have a property type with the value S Parameters return The number of skipped test cases B 1 1 28 10 getRelatedSummary public abstract String getRelatedSummaryO Gets the summary of the job test suite or test case related to this test run Parameters return the related summary B 1 1 28 11 getResults public abstract Set lt KlarosTestCaseResult gt getResultsO Get results Parameters return Set of results of test case executions B 1 1 28 12 getRunId public abstract String getRunIdO Get id of test run Parameters return The id of the test run B 1 1 28 13 getSut public abstract KlarosSUTImplementation getSut Get the tested system version Parameters return The SUT version which has been tested 271 Model API Reference B 1 1 28 14 getTestSuite public abstract KlarosTestSuite getTestSuite Get the test suite executed with t
164. ald Martens Erika Mustermann e eoele ol N N NI Oo Devon Manager 10 Elements found Page 1 of 1 Jobs without Assignee Fiter Sot 5 10 f Summary Priority Status Progress Success Due 408009044 Ausf hrung TC00003 Continuous Integration check w Minor Resolved JQ800010 Ausf hrung TC00002 Projekt setup check w Minor Resolved JOB00009 Ausf hrung TC00001 IDE check w Minor Resolved 30809003 Execution TS00001 Sprint Null A Major Resolved Figure 7 9 The Jobs by User Screen 7 1 8 1 Jobs by User Details This page displays the workload work duration and progress for a user in the currently selected project The user s jobs are shown in a table and a Gannt chart aids visualization of the user s workload Clicking the edit icon of a job opens the job details page for that job Further information can be found in Section 7 1 5 Job Details 112 Plan Define gt Execute Evaluate AL Configure de eN Jobs by User Peter Dev Maintain Jobs Name Peter Dev Width 800px Jobs from Test Cases Jobs 2 Label 25 Is Reopened Estimated Time h 0 0 l Jobs from Test Suites Busy from Start B to 10 31 13 10 00 PM End Resolved ollel aze l l Closed Progress Rejected In Progress User Occupation Peter Dev Time 1 Nov 3 Nov 5 Nov 7 Nov 9 Nov 11 Nov 13 Nov 15 Nov 17 Nov 19 Nov 21 Nov N JOBO0007 Projekt aufsetzen Fite
165. alue F or failure Parameters return true if this results represents a failure B 1 1 25 14 isPassed public abstract boolean isPassed Check if this is a result of a passed test case It is assumed that passed results have a prop erty testCasePassed with value true Parameters return true if this results represents an error 266 Model API Reference B 1 1 25 15 isSkipped public abstract boolean isSkippedO Check if this is a skipped result It is assumed that skipped results have a property type with the value S or skipped Parameters return true if this results represents a skipped result B 1 1 26 IKlarosTestEnvironment This interface provides access to data of a test environment B 1 1 26 1 Synopsis public interface IKlarosTestEnvironment extends IKlarosNamedEntity Public Methods public abstract Set lt KlarosAttachment gt getAttachments public abstract Set lt KlarosTestEnvironmentCategoryNode gt getCategories public abstract String getDescriptionO public abstract Set lt KlarosIteration gt getIterations public abstract Set lt KlarosTestRun gt getTestRuns B 1 1 26 2 getAttachments public abstract Set lt KlarosAttachment gt getAttachments 267 Model API Reference Gets the attachments associated with this test environment Parameters return the attachments B 1 1 26 3 getCategories public abstract Set lt KlarosTestEnvironmentCa
166. ame password combination on the login page an error message should be shown Test Cases Test Suites Compliance History Show all Created 2 years ago by Ted Steve Manager Figure 6 14 The Requirement Overview Tab s Priority 60 a so 8 40 30 E 20 de de 10 0 2013 2014 2015 Test Run Latest failing Test Cases ID 2 Name Start Executor Test Run Test Environment TC00004 Kopie von IDE check 4 2115 5 55 11 PM John Doe TRU0000064 Solaris 11 2011 11 0 2 TC00003 Continuous Integration check 11 20 13 8 25 30 PM John Doe TRU0000024 tomcat ad hoc 0 2 SNAPSHOT 6 TC00002 Project setup check 11 20 13 8 03 30 PM John Doe TRUO0000010 tomcat ad hoc 0 2 SNAPSHOT 6 E Compliance E Coverage System under Test Duration Result Action 00 00 09 Q ims ims Q Last changed 4 days ago by John Doe Back The priority of the requirement This signifies how crutial the compliance of this require ment is Compliance The compliance rate shows how many test cases which are part of this requirement have been successfully executed Coverage The compliance rate shows how many test cases which are part of this requirement have been executed at least once Note Note In contrast to the success rate the coverage rate considers only if a test case has been executed at least once in the iteration regardless of the result passed failed error e Automation Rate This bar shows h
167. anagement Enterprise Edition edition 4 If a tester notices a flaw in a test case or test suite description at any point during test exe cution he or she can schedule a review job by pressing the building site helmet icon 4 This opens a dialog window in which the details of the review job can be entered 132 Execute Tabular View Y TC00003 Continuous Integration check Step EETA Action Change the text on the landing page ofthe web app Expected Result Jenkins builds the project due to the changes and creates a war file which can be run in tomcat under default settings The changes on the landing page are verifyable in the browser Create a test case review request Atthe current state this test case cannot be fully executed since the testers cannot Description access the jenkins build folder z Assignee Lisa Ricardi T Priority Critical T Start Date 23 12 2015 00 00 Due Lock Test Case Generate Cancel A gZ lt 0 d OAO Figure 8 20 Creating a Review Job during Execution 133 Chapter 9 Evaluate This chapter describes how Klaros Testmanagement can be used to gather information about the selected project and evaluate its data 9 1 Dashboard The dashboard shows basic statistics about the active project and provides the links to the overview reports An example of a dashboard is shown in Figure 9 1 E Define MET po Execute pal Evaluate y Configu
168. anged in the local user database The available notification targets are e Assignee The assigned user account for a job assignment or the currently created changed user account e Creator The user responsible for triggering the notification event e g by assigning a job 171 Configure s Current User The user account currently active Specific User A specific user account E Define Plan TF Execute pal Evaluate E Configure B gt amp System Overview mnan Miscellaneous Notifications Interface Languages Report Templates VERE 2 Scheme Default system Default Authentication Scheme Event Target Action Integration Job Assigned ra Backup Account Created Assignee di Account Password Changed di Created 5 minutes ago by John Doe Last changed 4 minutes ago by John Doe Add notification Assign Projects Event Target Save Discard Job Assigned lt 9 Assignee Account Created Account Password Changed ELE 2 Current User Specific User Devon Manager Add Cancel Figure 10 17 The Notifications Tab Usingthe Assign Projects button the user may assign a notification scheme to a limited set of projects thus overriding the default notification scheme Figure 10 18 shows the dialog for project assignement Agee Plan HF Execute pil Evaluate Se Gn Assign Projects to Notification Scheme System Miscellaneous Notific Order Management WebApp a Scheme Restr Data Center Test GPS
169. ar 14 Apr 29 Apr 14 May 29 May 13 Jun 28 Jun 13 Jul Test Cases Test Cases with Result Figure 9 10 The Test Progress History Report 9 2 Report Templates edition y Feature only available in Klaros Testmanagement Enterprise Edition The Report Templates screen allows to generate PDFs of user defined reports The icon starts the generation and if necessary opens a new window to enter the needed parame ters The process of creating user defined reports is explained in Section 10 2 Report Tem plates Report Templates Name Revision Description Changed By Changed Action Report Templates Test Run Overview Report 1 0 Lists the Test Runs in a project grouped by selectable parameters admin 11 12 13 5 12 PM EA a VEGER iteration PDF Overview Report 1 0 Lists a defined Iteration in a Project admin 11 12 13 5 12PM 8 2 E TE Job Excel Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12PM E 2 a G Job PDF Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM EA a y IIEEE 829 Testrun Deviation Report Template v1 1 0 IIEEE 829 Testrun Deviation Report Template v1 admin 11 12 13 5 12 PM EA a Integration IEEE 829 Test Plan Template v1 1 0 IEEE 829 Test Plan Template v1 admin 11 12 13 5 12 PM 2 a A IEEE 829 Test Case Specification Template v1 1 0 IEEE 829 Test Case Specification Template v1 admin 11 12 1
170. arameter String name method The methods will return null if no parameter with the specified name can be found 11 1 1 Supported Parameter Types The following parameter types are supported Report Parameter Types e Text Number Date Boolean Enumeration e Multi enumeration 11 1 2 Dealing with Parameters As mentioned before the passed parameters can be retrieved from the context by the meth ods getParameterValue String name and getParameter String name 189 Custom Reports The following code snippet shows how to access the parameters and how to use them in the Groovy script query append select tcr from KlarosTestCaseResult tcr where tcr executionTime lt long executionTime context getParameterValue executionTime query append executionTime List lt gt tcr context executeQuery query toString This query will retrieve all KlarosTestCaseResult instances that have an execution time small er than the value passed with the parameter executionTime As an alternative the parameters can be directly accessed in the query as shown in the fol lowingcode snippet query append select tcr from KlarosTestCaseResult tcr where tcr executionTime lt executionTime List lt gt tcr context executeParameterizedQuery query toString Parameters can be accessed from the report template in the following way lt p text value Testresults for testruns with execution time amp lt execution
171. are referenced during import like projects or test cases con tain five digits in their id For example P00001 is a valid project ID while P0001 and P000001 are not 12 2 Importing Test Cases from XML Klaros Testmanagement allows importing of test cases from XML Files The import process will always create new instances of the supplied test cases for each invocation The format of the XML file is described in Appendix C Test Case Import File Specification For validation purposes an XML schema is also available from the following URL http www klaros testmanagement com files schema klaros testcases 1 0 xsd 12 2 1 Prerequisites To import XML based test cases the following prerequisites have to be met 1 The file that is going to be imported has to be in xml format 2 The project that should contain the imported test cases has to be already created 3 If the Authentication required for import flag is set see Section 10 5 1 Miscella neous Settings username and password of a system user have to be provided see Sec tion 10 3 3 User Details for more information on system users 4 If custom properties are to be used they have to be defined for the project prior to starting the import process Please note that custom properties are Only available in the Klaros Testmanagement Enterprise Edition 12 2 2 Execution To import XML based test cases a REST interface is available which allows you
172. ategoryNode lt I W X Y gt getRootNodeQ Gets the root category node Parameters return the root B 1 1 3 4 getShortname public abstract String getShortnameO Gets the shortname Parameters return the shortname B 1 1 4 IKlarosConfiguration This interface provides access to data of a test project B 1 1 4 1 Synopsis public interface IKlarosConfiguration extends IKlarosLabeledObject Public Methods public public public public public public public public public public public public public public public public abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract String getDescription Set lt KlarosTestEnvironment gt getEnvs Set lt KlarosIterationCategoryTree gt getIterationCategoryTrees Set lt KlarosIteration gt getIterations Set lt KlarosJob gt getJobs Set lt KlarosRequirementCategoryTree gt getRequirementCategoryTrees Set lt KlarosRequirement gt getRequirements Set lt KlarosSUTImplementation gt getSutsO Set lt KlarosSUTImplementationCategoryTree gt getSystemUnderTestCategoryTrees Set lt KlarosTestCaseCategoryTree gt getTestCaseCategoryTrees Set lt KlarosTestCase gt getTestCases Set lt KlarosTestEnvironmentCategoryTree gt getTestEnvironmentCategoryTrees Set lt KlarosTestRun gt getTestRuns Set lt KlarosTestSuiteCategoryTree gt
173. ates for the general test case properties None of these values are mandatory Some fields can take only predefined values which are listed there Table 12 1 General Property Coordinates 12 1 1 2 Test Case Steps Test cases may contain an variable number of test steps These are listed one per row start ing from cell A26 downwards The import parser will stop reading steps once it encounters an empty step number A27 ff Step Number 52700 GT 027 E27 ff Expected Result Table 12 2 Test Case Step Coordinates 197 Import Export 12 1 1 3 Custom Properties Test cases may contain custom attributes These are listed as name value pairs starting from cell G1 downwards The name in the name column must exactly match the name of general property for a value to be parsed correctly The parsing stops once an empty name cell has been found The value field for enumeration properties must exactly match the name of the enumeration property value definition to be parsed ST m Table 12 3 User Defined Property Coordinates 12 1 2 Prerequisites To import Excel based test cases the following prerequisites have to be met 1 The file that is going to be imported has to be in xIs format 2 The project that should contain the imported test cases has to be already created 3 If the Authentication required for import flag is set see Section 10 5 1 Miscella neous Settings username and password of a system user h
174. ating an Iteration Clicking on the New button creates a new iteration in the currently selected project Figure 6 8 The Name Start Date and Due Date fields can then be specified The iteration ID is automatically assigned by Klaros Testmanagement Define 6 2 3 Iteration Details 6 2 3 1 Iteration Overview Projects Requirements Test Environments Systems under Test Test Cases Test Suites Plan LS Execute pl Evaluate X Configure webapp E L J ITRO0001 Setup phase are Back Overview Properties User Defined Attachments Test Environments 2 Systems under Test 2 Requirements 3 Results Changes Start Date 2 weeks ago Description Setup of the infrastructure including development tools and Cl Due Date 2 days from now Execution Time manual 00 00 31 Execution Time automated 0 ms Success KA Progress 10 Compliance KA Coverage 16 System under Test Developer local IDE integrated tomcat ad hoc 0 1 D des Par 0 1 SNAPSHOT D D Created 2 years ago by Ted Steve Manager Last changed moments ago by John Doe Back Figure 6 9 The Iteration Overview Tab e Start Date The point in time when the iteration starts e Due Date The point in time when the iteration ends s Execution Time manual and Execution Time automated The overall execution times from manual and automated test executions of the iteration are summed up and shown as execution time manual an
175. ave to be provided see Sec tion 10 3 3 User Details for more information on system users 4 If custom properties are to be used they have to be defined for the project prior to starting the import process Please note that custom properties are only supported in Klaros Testmanagement Enter prise Edition 12 1 3 Execution To import Excel based test cases a REST interface is available which allows you to upload your data from the command line or other applications The following example shows how to import an Excel sheet containing test cases into the project named P00001 using the curl command line application Curl should be available in every Linux distribution and as part of the Cygwin http www cygwin com distribution or as a command line tool from http curl haxx se download html for the Microsoft Windows operating system family curl v T TestCases xls lt klaros app url gt seam resource rest import testcase xls config P00001 Example 12 1 Excel Test Case Import via Command Line If the Klaros Testmanagement installation requires authentication for import username and password arguments have to be appended to the curl call 198 Import Export curl v T TestCases xls lt klaros app url gt seam resource rest import testcase xls config P00001 amp username user amp password secret Example 12 2 Excel Test Case Import via Command Line with authentication 00000000 Note Ea All artifacts which
176. be edited jm It is possible to move an issue from one test case to another Pressing the sw icon opens up the issue in the appertaining issue management systems in a new tab Pressing the icon removes the issue from the test case r Important This does not delete the issue in the issue management system only the refer ence to the test case in Klaros Testmanagement Pressing the New button opens up the Section 9 7 2 Issue Details Creating a new Issue page Pressing the Link button opens up the Link Issues page in which existing issues from issue management systems can be linked to this test case The Issues by Test Case page lists all test cases that have linked issues or results with linked issues Figure 9 31 The Issues by Test Case Screen Clicking the button opens the Browse Issues page for the corresponding test case Figure 9 33 The Issues by Test Case Details Screen The issue ID is a hyperlink to the corresponding issue in the issue management system 157 Evaluate 9 7 3 Link Issues While most issues get detected during execution of a test case sometimes it is necessary to defer the creation of an issue in the issue management system and some issues are raised on an ad hoc basis In order to preserve a relation to test cases it is possible to link issues created in an issue management system to test cases in Klaros Testmanagement The Link Issues page lists all test cases
177. blic Date getTimestamp Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 302 Model API Reference KlarosTag getRevisions Set lt KlarosRevision lt gt gt getTagld String getlimestamp Date B 1 1 57 KlarosTestCase This class provides access to the information stored for a test case B 1 1 57 1 Synopsis public final class KlarosTestCase extends KlarosRevision lt KlarosTestCase TestCase gt implements IKlarosTestCase lt KlarosTestCase TestCase gt Comparable lt KlarosTestCase gt Public Methods public int compareTo KlarosTestCase o public boolean equals Object o public TestAreatopic getArea public Set lt KlarosAttachment gt getAttachmentsO public KlarosTestCase getBranchRoot public Set lt KlarosRevision lt KlarosTestCase TestCase gt gt getBranches public Set lt KlarosTestCaseCategoryNode gt getCategories public KlarosConfiguration getConfiguration public Set lt KlarosRequirement gt getCovers public String getDependencyO public String getDescription public TestDesignTechnique getDesignTechnique public List lt KlarosIssue gt getDetectedIssues public String getDocbase public String getEvaluation public TestExecutionMethod getExecution 303 Model API Reference public String getExpe
178. bserved or measured value or condition and the true specified or theoretically correct value or condition An error is the inability of the system to perform the test correctly For each error or failure Klaros Testmanagement will show the following dialog Figure 8 6 The Continue tothenextstepwhilethe Finish button saves the comment and completes the test case run 118 Execute Tabular View 7 Edit step result Result Action Expect The project did not appear in the Jenkins window Summary Step Description Test Case Result Summary Description Upload Attachment Finish Test OK Cancel gt AEOD 040 Figure 8 6 The Error or Failure Detected Dialog g The Description and Summary fields appear in all comment dialogs The test case results screen allows the user to write a description and summary for the test case run as well as for each individual test step in the test run Figure 8 7 119 Execute Test Run Overview Test Case Result TCR0000017 Test Run TRU0000011 Start 11 20 13 8 17 PM Execution time 1 Second s Summary Description Upload Aftachment Steps sos ER B Step 1 Start IDE Description Link Issue Create Issue Finish Figure 8 7 The Test Case Results Screen gt Note If there are any issue management systems configured for this project the Create Issue button will be enabled For details on creating an issue with Klaros Testmanagement
179. bstract KlarosExternalImplementation getImplementationO Get implementation Parameters return The object describing the location of the implementation of this test case revision B 1 1 21 17 getLevel public abstract TestLevel getLevelQ The level of this test case Parameters return The level B 1 1 21 18 getNote public abstract String getNote The note of this test case Parameters return The note B 1 1 21 19 getPostcondition public abstract String getPostcondition The postcondition of this test case Parameters return The postcondition 255 Model API Reference B 1 1 21 20 getPrecondition public abstract String getPrecondition The precondition of this test case Parameters return The precondition B 1 1 21 21 getPriority public abstract TestPriority getPriorityO The priority of this test case Parameters return The priority B 1 1 21 22 getResults public abstract Set lt KlarosTestCaseResult gt getResultsO Get test case results Parameters return Set of results of executions of this test case revision B 1 1 21 23 getShortname public abstract String getShortnameO The short name title of this test case Parameters return The short name B 1 1 21 24 getState public abstract String getState The type of this test case Parameters return The type B 1 1 21 25 getStateName KlarosSUTImplementation public abstract String getStateName
180. c abstract Date getTimestampO Get timestamp Parameters return The time of the creation of the tag as a Date object 250 Model API Reference B 1 1 21 IKlarosTestCase This class provides access to data of a test case B 1 1 21 1 Synopsis public interface IKlarosTestCase lt T S extends Revision gt extends IKlarosRevision lt T S gt I Public Methods public public public public public public public public public public public public public public public public public public public public public public public public public public public public public abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract TestAreatopic getArea Set lt KlarosAttachment gt getAttachmentsO Set lt KlarosTestCaseCategoryNode gt getCategories KlarosConfiguration getConfiguration Set lt KlarosRequirement gt getCovers String getDependencyQ String getDescription TestDesignTechnique getDesignTechnique List lt KlarosIssue gt getDetectedIssues String getDocbase String getEvaluationO TestExecutionMethod getExecution String getExpectedResultO Set lt String gt getExternalNames KlarosExternalimplementation getImplementation TestLevel getLevelQ
181. c long getExecutionTime public String getExpectedResult public String getPostcondition public String getPrecondition public String getSummaryO public KlarosTestCase getTestCase public KlarosTestCaseResult getTestCaseResult public KlarosTestRun getTestRunQ public int hashCode public boolean isErrorQ public boolean isFailureQ public boolean isPassed public boolean isSkippedO 310 Model API Reference Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait TT S S extends LabeledObject pject lt T S gt wy S S extends NamedEntity KlarosNamedEntity lt KlarosTestCaseStepResult TestCaseStepResult gt 1 KlarosTestCaseStepResult getTestRun KlarosTestRun getTestCaseResult KlarosTestCaseResult getTestCase KlarosTestCase isPassed boolean isError boolean isFailure boolean isSkipped boolean compareTo o KlarosTestCaseStep Result int equals o Object boolean hashCode int getSummary String getDescription
182. ct String getRoleO public abstract String getUsername 276 Model API Reference B 1 1 31 2 getEmail public abstract String getEmailO The email address of this user Parameters return the email address B 1 1 31 3 getRole public abstract String getRoleQ The role name of this user Parameters return the role name B 1 1 31 4 getUsername public abstract String getUsernameQ The user name of this user as used when logging in Parameters return the user name B 1 1 32 KlarosAttachment This class provides access to binary attachment B 1 1 32 1 Synopsis public final class KlarosAttachment extends KlarosWrapper lt KlarosAttachment Attachment gt implements IKlarosAttachment Public Methods public String getMimeTypeO public String getNameO public long getSizeqQ public String getUuid public String getVersion Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 277 Model API Reference KlarosAttachment getUuid String getName String getMimeType String getSize long getVersion String B 1 1 33 KlarosCategoryNode A generic category node B 1 1 33 1 Synopsis public abstract class KlarosCategoryNode lt I T W extends KlarosCategoryNode lt I T W P gt P extends CategoryNode gt extends KlarosWrapper
183. ctedResultO public Set lt String gt getExternalNamesO public KlarosExternalImplementation getImplementationo public TestLevel getLevelQ public String getNote public String getPostconditionQ public String getPrecondition public KlarosTestCase getPredecessor public TestPriority getPriorityO public Set lt KlarosTestCaseResult gt getResultsO public KlarosTestCase getRoot public String getShortname public String getState public String getStateName KlarosSUTImplementation sut public Map lt KlarosSUTImplementation KlarosTestCaseState gt getStates public KlarosTestCase getSuccessor public String getTeam public List lt KlarosTestCaseStep gt getTestCaseSteps public String getTraceabilityO public KlarosTestCase getTrunkRoot public TestVariety getVarietyO public int hashCodeO Methods inherited from de verit klaros core model KlarosRevision getRevisionComment getRevisionld Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 304 Model API Reference S Se
184. ction log for this user This shows all login attempts of this user from a mobile device with the Klaros Testmanagement Mobile Edition Android Client installed The time that each login attempt has happened is also displayed as is the device from which the synchronization login has been attempted Clicking the device name open up the details page for this mobile device E Define Ra Pn po Execute q Evaluate y Configure Testing the email ciient amp Erika Mustermann KJE Overview Report Templates users Properties Project Roles Results Connection Log Changes Mobile Devices Date Mobile Device Status S ke 10 29 13 2 31 20 PM MD00001 Nexus S Ok 10 29 13 4 06 51 PM MD00001 Nexus S Ok Integration 10 31 13 11 01 08 AM MD00002 Nexus S Ok Backup 10 31 13 3 39 56 PM MD00003 Android SDK built for x86 Ok 10 31 13 3 40 00 PM MD00003 Android SDK built for x86 Ok 10 31 13 3 40 30 PM MD00003 Android SDK built for x86 Ok 10 31 13 3 42 15 PM MD00003 Android SDK built for x86 Ok 10 31 13 3 50 52 PM MD00003 Android SDK built for x86 Ok 11 6 13 9 51 07 AM MD00005 Nexus S Device deactivated 11 8 13 4 37 18 PM MD00009 Nexus S Ok 11 8 13 4 37 44 PM MD00009 Nexus S Ok Last changed by John Stewart on 11 8 13 4 37 PM Back Figure 10 10 The Mobile Device Connection Log Tab 10 4 Mobile Devices mobile edition Only available in Klaros Testmanagement Mobile Edition The Mobile Devices page gives the user an
185. cycle in a project This helps synchronizing the test process with an agile development process e g Scrum The Iterations page allows management of the iterations in the selected project An iteration can be selected for the current project by selecting it in the toolbar on the top of the page see Figure 6 7 The Iteration and Project Selection Toolbar When an iteration is active only test objects relevant to the test cycle represented by the iteration are visible All test runs executed while an iteration is active are automatically linked to the iteration This helps to quickly assess the test progress and success rates for a given test cycle Sprint 2 Figure 6 7 The Iteration and Project Selection Toolbar Iterations may be created removed updated and assigned to categories on this page Fig ure 6 8 The displayed iterations may be filtered and sorted as described in Section 5 2 5 Filtering and Sorting 73 Define EZ Define Plan e Execute Pl evaluate X Configure S Webap 2 Iterations Projects Categories Fiter Sort 10 v is Name Start Date Due Test Runs Action Test Environments J ITRO0005 Sprint 04 03 11 2013 19 09 EA m 0 gt A AGE Systems under Test ITR00004 Sprint 03 09 12 2013 10 00 23 12 2013 10 00 FJ 0 gt 2208 Test Cases ITR00003 Sprint 02 25 11 2013 10 00 09 12 2013 10 00 PH 0 gt 22808 Test Suites J ITR00
186. d This database is not reduired to run on the same physical machine as the Klaros Testman agement server Name Reeta Apache Derby Version 10 10 1 1 and above embedded and preconfigured Microsoft SOL Microsoft SOL Server 2012 SOL Server 2008 R2 SOL Server 2008 Server Installation Name Description OOOO S MySQL Version 5 5 and above with InnoDB as the storage engine MyISAM is not supported as the storage engine since it doesn t provide referen tial integrity PostgreSQL Version 8 4 and above Oracle Version 10g 119 12c Table 3 2 Supported Databases 3 2 2 1 Installing Java If your system is not yet equipped with an Oracle Java 7 runtime environment you need to download a JRE or JDK distribution from http www oracle com technetwork java javase downloads index html Both JRE and JDK installations are supported For maximum perfor mance choose a distribution matching your system architecture x86 x64 Alternative Java Runtime Environments Out of the box most Linux distributions do not come with an Oracle Java instal lation but some alternative Java implementation like GC or OpenJDK Klaros Testmanagement is not supported in such an environment as there are known issues with some of these implementations Make sure that the JAVA HOME JRE HOME environment variable is set A common caveat is that although Java is installed on your machine the installer or launch script will complain that neither the J
187. d deactivated or blocked e Activated devices amp can receive test artifacts and also send test results back to Klaros Testmanagement If a mobile device connects to Klaros Testmanagement for the first time it is automatically activated if enough free mobile device slots are available Deactivated devices 3 cannot access any resources When a user tries to connect to Klaros Testmanagement he receives an error message If a mobile device connects to Klaros Testmanagement for the first time and if there are no free mobile device slots avail able then the mobile device is deactivated It can later be activated if another mobile de vice gets deactivated first Blocked devices amp cannot access any resources When a user tries to connect to Klaros Testmanagement he receives an error message Above the table two numbers are displayed Licensed Mobile Devices and Activated Mobile Devices Licensed Mobile Devices shows the maximum number of mobile devices that can be activated on this Klaros Testmanagement installation Activated Mobile Devices shows the number of mobile devices that are currently activated This number is less or equal to the number of licensed mobile devices The column labeled Device Name shows the model name of the mobile device To further distinguish multiple mobile devices of the same model the Comment column can be used The last two columns show the user name of the last user that has synchronized wi
188. d execution time automat ed e Success Tip Those values can be used for further investigation An extremely high manual execution time for example could indicate a high rate of retesting or a need for more automated test cases Execution Time manual 00 00 31 Execution Time automated 0 ms SUCCESS 3 20 test cases have been executed with passed result Progress 20 Compliance Coverage 16 Figure 6 10 The Iteration Success Rate 75 Define All test cases which are included in this iteration contribute to this metric if none are explicitly registered for this iteration then all test cases are considered A Success rate of 100 means that the latest test run for every test case has been successful Note I Even if a test case has been successfully executed in the past only the latest result is considered for the success rate e Progress The progress rate shows how many test cases which are considered for this iteration have been executed Note Ea In contrast to the success rate the progress rate considers only if a test case has been executed at least once in the iteration regardless of the result Compliance The compliance rate shows how many test cases which are part of this iterations require ments have been successfully executed Coverage The coverage rate shows how many test cases which are part of this iteration s require ments have been executed at least once
189. ded or on other machines The installation can be completed by clicking the Done button 3 4 Console based installation The Klaros Testmanagement installer also supports a GUI less variant which only needs a Shell command window and can be invoked as follows java jar Klaros Setup jar console This displays the content of the installer panels in the shell window and lets the user input her choices via keyboard The UI controls are replaced by short key sequences Enter shows the next page of a text panel or accepts a default value 1 Enter selects a checkbox 0 Enter deselects a checkbox n Enter chooses the nth item from a list 3 4 1 Step 1 Welcome U The Welcome Panel Section 3 3 1 Step 1 Welcome is displayed and wants to be commit ted by 1 Enter 28 Installation Please read the following information Version 4 3 0 c Copyright 2009 2015 verit Informationssysteme GmbH All Rights Reserved Press 1 to continue 2 to quit 3 to redisplay 1 3 4 2 Step 2 Information The Information Panel Section 3 3 2 Step 2 Information needs some paging Just press Enter to see the next page until a choice is requested Please read the following information Release Notes for Klaros Testmanagement version 4 3 0 Klaros Testmanagement is an AJAX based web application for the clear and concise management of the quality assurance process in software development projects Press Enter to con
190. del KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait EEE TTT l 0 S Sextends LabeledObject KlarosLabeledObject lt T S gt KlarosNamedEntity getAssignee KlarosUser getProperties Lists IKlarosProperty gt isDefinedProperty propertyName String boolean B 1 1 47 KlarosProperty The Klaros property class B 1 1 47 1 Synopsis public final class KlarosProperty implements IKlarosProperty Public Methods public String getName public String getValueO Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 293 Model API Reference KlarosProperty getName String getValue String B 1 1 48 KlarosRequirement This class provides access to the information stored for requirements B 1 1 48 1 Synopsis public final class KlarosRequirement extends KlarosRevision lt KlarosRequirement Requirement gt implements IKlarosRequirement lt KlarosRequirement Requirement gt Public Methods public public public public public public public public public public public public public public public public public public Set lt KlarosAttachment gt getAttachments KlarosRequirement getBranchRoot Set lt KlarosRevision lt KlarosRequirement Requirement gt gt getBranches Set lt KlarosRequirementCategoryNode
191. der test is used to represent a version of a software product that can be tested The Systems under Test page allows the creation removal and updating of systems under test and assigning them to categories The displayed systems under test may be filtered and sorted as described in Section 5 2 5 Filtering and Sorting Figure 6 18 CH Denne BEET TA TRA TR RO Systems under Test Projects Ee Iterations gt 2 E B Categories Filter Sot El 70 v Requirements ID e Version Issues Action Test Environments SUTO00020 G 02 1 8g Systems under Test SUTO0019 3 Test Cases SUT00018 0 4 alpha ote a aa a aa a aa Version Action Test Suites SUT00017 0 4 SUT00016 Test SUT00006 3 0 2 SNAPSHOT6 SUT00005 0 2 SUT00004 amp 0 3 SNAPSHOT SUT00003 0 3 SUT00002 0 1 N N NN NN N N N N N DBL SUT00001 0 1 SNAPSHOT 11 Elements found Page 1 of 1 1 70 Y Figure 6 18 The Systems under Test Screen The Systems under Test screen shows a table with all of the systems under test in current project The version of the system under test can be changed by clicking on the text field and editing it directly Define The leftmost column allows system under test to be selected for bulk actions The uppermost checkbox is a global select button which selects or deselects all elements shown in the table Please note that the displayed elements are subject to the current search and catagorization
192. ds KlarosCategoryTree lt 1 W P X Y gt I P Pextends CategoryTree 1 X X extends KlarosCategoryNode lt l W X Y gt 1 Y Y extends CategoryNode 1 L KlarosCategoryTree lt KlarosTestEnvironment KlarosTestEnvironmentCategoryTree TestEnvironmentCategoryTree KlarosTestEnvironmentCategoryNode TestEnvironmentCategoryNode E KlarosTestEnvironmentCategoryTree B 1 1 67 KlarosTestExecutable This class provides access to the information stored for test cases B 1 1 67 1 Synopsis public final class KlarosTestExecutable extends KlarosWrapper lt KlarosTestExecutable TestExecutable gt implements IKlarosTestExecutable Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait I KlarosTestExecutable 314 Model API Reference B 1 1 68 KlarosTestRun This class provides access to the information stored for test runs B 1 1 68 1 Synopsis public final class KlarosTestRun extends KlarosNamedEntity lt KlarosTestRun TestRun gt implements IKlarosTestRun Comparable lt KlarosTestRun gt Public Methods public public public public public public public public public public public public public public public public public public public int compareTo KlarosTestRun 0 boolean equals Object o KlarosConfiguration getConfiguration KlarosTe
193. e Locale void L B 2 1 1 2 KlarosContext Context UUID UUID KlarosQueryFactory Parame terContext public KlarosContext Context context UUID activeProjectId UUID activelterationld KlarosQueryFactory factory ParameterContext parameters Create a KlarosContext 323 Model API Reference Parameters context Gets passed by the relating servlet activeProjectId the active project id activelterationId the active iteration id if available factory the factory parameters the parameters B 2 1 1 3 KlarosContext Context UUID UUID Klaros ueryFactory Parame terContext Locale public KlarosContext Context context UUID activeProjectld UUID activelterationld KlarosQueryFactory factory ParameterContext parameters Locale locale Create a KlarosContext Parameters context Gets passed by the relating servlet activeProjectId the active project id activelterationlId the active iteration id factory the factory parameters the parameters locale the locale B 2 1 2 KlarosQueryFactory This factory lets the user execute queries B 2 1 2 1 Synopsis public class KlarosQueryFactory Public Static Fields public static final String WRAPPER_PREFIX klaros Public Constructors public KlarosQueryFactory Session session Public Methods public List lt gt execute String query public List lt gt execute String query ParameterContext params Methods inherited
194. e klaros folder in the home folder of the user running Klaros Testmanagement To allow a simple upgrade the installation upgrade process will only change files in the in Stallation folder and leaves the content of the home folder untouched On Microsoft Windows systems by default the home folder is located at C Documents and Settings lt username gt klaros for Microsoft Windows XP and earlier or C Users lt username gt klaros for Microsoft Windows Vista 7 and 8 This can also be opened by entering UserPro file klaros in an explorer window address bar or by entering cd UserProfile klaros on the command line On Linux systems this folder can be found using the path klaros and is generally located at home lt username gt klaros On Mac OS X systems this folder is located at Users lt username gt klaros and can be found using klaros Q Relocating the Klaros Testmanagement home folder By setting the environment variable KLAROS HOME before starting the application the location of the home folder can be moved to another folder specified herein export KLAROS_HOME var application data klaros AN Heads up when moving the home folder If the application does not find a previous installation in the home folder it will bootstrap an empty default installation including a new local database If this happens by accident e g by providing a wrong home folder location it appears to the user that all previous data is gone
195. e Management System Integration F2 a Report Template Details AU Revision 1 0 Report Templates Name Iteration PDF Overview Report PE Description Lists a defined Iteration in a Project Template Type PDF vw Edit the Script Mobile Devices System Name Label Type Description Value Action Integration l x iterationName Iteration ID Text v The ID ofthe Iteration to generate I Backup New Parameter pan A The Class IterationsReport A Java snippet to create an Iteration Report Template ay public class IterationsReport implements KlarosScript Override Groovy Script oy P public void execute final KlarosContext context final String iterationName String context getParameterValue iterationName String query select g from KlarosIteration g where g name query iterationName query if context getActiveProject null query and g configuration name v query context getActiveProject getName Upload Script Template Edit the Template Preview Save Discard Figure 11 4 Specifying Parameters Clicking the icon removes the parameter from the list The type of the parameters can be specified by selecting the appropriate value from combo box Supported types are Text Number Date Boolean Enumeration and Multi enumeration The passed parameters can be accessed by the Groovy script by either calling the getPara meterValue String name or the getP
196. e following elements lt testcase gt C 26 lt priority gt The priority of this test case This element may occur inside the following elements lt testcase gt C 27 lt shortname gt The editable title of the test case This element may occur inside the following elements lt testcase gt C 28 lt state gt The state of this test case This information is ignored for import operations This element may occur inside the following elements lt testcase gt C 29 lt team gt The team this test case is assigned to 349 Test Case Import File Specification This element may occur inside the following elements lt testcase gt C 30 lt traceability gt The traceability information for this test case This element may occur inside the following elements lt testcase gt C 31 lt variety gt The result expectation of the test Whether a positive or negative result is expected This element may occur inside the following elements lt testcase gt C 32 lt name gt The name of the custom attribute This element may occur inside the following elements lt attribute gt C 33 lt value gt The value of the custom attribute This element may occur inside the following elements lt attribute gt 350 Appendix D Requirement Import File Specification The following table gives a short overview of the available elements name pnan O lt external
197. e of this state B 1 1 23 4 getSut public abstract KlarosSUTImplementation getSut Get related system under test version Parameters return The related SUT version B 1 1 23 5 getTestCase public abstract KlarosTestCase getTestCase Get test case Parameters return The test case whose state is defined by this state object B 1 1 24 IKlarosTestCaseStep This interface provides access to a test case step B 1 1 24 1 Synopsis public interface IKlarosTestCaseStep Public Methods public abstract String getAction public abstract String getExpectedResult public abstract String getPostcondition public abstract String getPrecondition 262 Model API Reference B 1 1 24 2 getAction public abstract String getAction Get the action Parameters return The action of this test case step B 1 1 24 3 getExpectedResult public abstract String getExpectedResultO Get the expected result Parameters return The expected result of this test case step B 1 1 24 4 getPostcondition public abstract String getPostconditionO Get the postcondition Parameters return The postcondition of this test case step B 1 1 24 5 getPrecondition public abstract String getPrecondition Get the precondition Parameters return The precondition of this test case step B 1 1 25 IKlarosTestCaseStepResult This interface provides access to data of a test case step resul
198. e other system under tests can be viewed by pressing the Show All button e Latest Issues This list shows the latest issues which have been created in conjunction with this system under test during test execution or linked to this system under test after its creation gt Note This table is limited to five entries The other system under tests can be viewed by pressing the Show All button 6 5 3 2 User Defined Properties Ka edition y Feature only available in Klaros Testmanagement Enterprise Edition 90 Define User defined properties can be used to customize systems under test within Klaros Test management by adding custom fields This process is described in Section 5 2 11 User De fined Properties 6 5 3 3 Attachments Attachments may be added to systems under test This process is described in Section 5 2 12 Attachments 6 5 3 4 Issues EZ Define Plan Execute Pl Evaluate 3X Configure WebApp Z a Sl SUTO0006 0 2 SNAPSHOT 6 aE Projects l Back ro Overview Properties User Defined Attachments Issues 2 Results Changes Requirements Test Environments a r H i ID System Summary PLAYGROUND 14407 E 00001 Project not appearing in Jenkins list PLAYGROUND 5374 IM00001 Error during login Systems under Test Test Cases Created Created By Assigned To Priority State Action 11 20 2013 admin admin Blocker Open Q 11 28 2010 hudson hudson Blocker Open Fi D Test Suites Ne
199. e results in this test suite B 1 1 30 IKlarosTestSuiteResult This interface provides access to data of a test suite result B 1 1 30 1 Synopsis public interface IKlarosTestSuiteResult extends IKlarosNamedEntity Public Methods public abstract Set lt KlarosTestCaseResult gt getResultsO public abstract KlarosTestRun getTestRun public abstract KlarosTestSuite getTestSuite public abstract boolean isPending B 1 1 30 2 getResults public abstract Set lt KlarosTestCaseResult gt getResultsO Gets the test case results for this test suite result The list is sorted by the position in which the test cases appear in the test suite Parameters return the results 275 Model API Reference B 1 1 30 3 getTestRun public abstract KlarosTestRun getTestRun Get the test run for this result Parameters return the test run B 1 1 30 4 getTestSuite public abstract KlarosTestSuite getTestSuite Get the related test suite Parameters return The test suite that has been executed to get this result B 1 1 30 5 isPending public abstract boolean isPending Checks if the test suite result is pending This means that it has not yet been completely executed Parameters return true if the test suite result is pending B 1 1 31 IKlarosUser The user object B 1 1 31 1 Synopsis public interface IKlarosUser Public Methods public abstract String getEmailO public abstra
200. e standard fields provided for requirements users of the Klaros Testman agement Enterprise Edition are also able to import data for user defined fields For this it is necessary to prepare the project according to what is listed in Section 12 3 2 Prerequisites The import interface consists of a simple REST interface which can be accessed by command line tools as well as custom applications This is further detailed in Section 12 3 3 Execu tion 12 3 1 Import Format The Excel sheet used to import requirements has to follow this strict format 1 Each requirement is located on a separate sheet 2 Each sheet is divided into two sections general properties and custom properties A B C D E G 1 Shortname Test Requirement Department Internal 2 Revision 1 0 Category Security 3 Description Unauthorized users cannot access the server Dev BETA 4 Priority HIGH During alpha development phase it is possible User Defined P roperti es to access the server without providing a 5 user password combination The Server should be secured against unauthorized access Summary during beta phase 6 E General Properties 9 Figure 12 2 Requirement Excel Sheet Sample 200 Import Export 12 3 1 1 General Properties The table below lists the cell coordinates for the general requirement properties None of these values are mandatory Some fields can take only predefined values
201. eState 261 IKlarosTestCaseStep 262 IKlarosTestCaseStepResult 263 IKlarosTestEnvironment 267 Index IKlarosTestExecutable 268 IKlarosTestRun 268 IKlarosTestSuite 272 IKlarosTestSuiteResult 275 IKlarosUser 276 KlarosScript 326 Iterations 73 IterationsReport 330 J JobReport 332 K KlarosAttachment 277 KlarosCategoryNode 278 KlarosCategoryTree 279 KlarosConfiguration 280 KlarosContext 322 KlarosContextParameter 329 KlarosEnumValue 281 KlarosExternallmplementation 282 KlarosIssue 283 KlarosIteration 284 KlarosIterationCategoryNode 285 KlarosIterationCategoryTree 286 Klarosjob 287 KlarosjobTimeBlock 289 KlarosjobUpdateAction 290 KlarosLabeledObject 291 KlarosNamedEntity 292 KlarosProperty 293 KlarosQueryFactory 324 KlarosRequirement 294 KlarosRequirementCategoryNode 295 KlarosRequirementCategoryTree 296 KlarosRequirementGroup 297 KlarosRevision 298 KlarosScript 326 KlarosSUTImplementation 299 KlarossUTImplementationCategoryNode 301 KlarossUTImplementationCategoryTree 301 KlarosTag 302 KlarosTestCase 303 KlarosTestCaseCategoryNode 305 KlarosTestCaseCategoryTree 306 KlarosTestCaseResult 307 KlarosTestCaseState 308 KlarosTestCaseStep 309 KlarosTestCaseStepResult 310 360 KlarosTestEnvironment 311 KlarosTestEnvironmentCategoryNode 312 KlarosTestEnvironmentCategoryTree 313 KlarosTestExecutable 314 KlarosTestRun 315 KlarosTestSuite 316 KlarosTestSuiteCatego
202. eated Test Case Results Test Suite Results Description The window to put in the issue data does not open therefore no issues can be created Issues Result A gt Failure Start 11 19 13 3 13 54 PM Executor John Doe Execution time 00 01 28 Second s Test Run TRUO000009 11 19 13 3 13 54 PM Test Case TC00001 Testing the file upload of the ticket system Test Environment ENV00002 OpenBSD 5 3 System under Test SUT00001 Ticket System v1 56 Steps Number Action Result Summary Description A 2 3 So 3 1 Log into the ticket system Press the button Create new Ticket Press the button Attach file to ticket The window doesnt open The window to put in the issue data does not open Select the file test zip for uploading and press OK S SOO SNNNQN n amp wU N Press the button Save Ticket Upload Attachment Back Figure 9 23 The Test Case Results Details Screen This page shows the individual step results of the test case result Users may also edit the Summary Description and Result of the test case result and of each individual step result All changes are logged and any change to results is cascaded to the test case result test suite result and test run If a test case result has been changed the icon is displayed on this page and in all tables where the result is displayed The Result field of a test case result may only be changed in Klaros Testmanagement Enterprise Edition Figu
203. ebApp A Projects Iterations Fiter Sort El 10 v gear Description TestCases Test Suites Test Runs Created Action Test Environments P00012 WebApp 3 3 6 11 19 13 2 17 PM 2 B Systems under Test P0001 P2 2 1 3 11 19 713 2 17PM X Test Cases P00010 P1 1 0 0 11 19 13 2 17 PM Test Suites gt P00005 Test GPS Tracking 3 0 3 11 18 13 5 24PM 2 B gt P00004 Bestellprozess 2 1 0 11 18 13 5 24PM 2 E P00003 Issue Management System Integration 1 0 8 11 18 13 5 24PM O 2 B P00002 Testing the email client 1 0 2 11 18 13 5 24PM O 2 G gt P00001 Einrichten des neuen Rechenzentrums 2 1 0 11 18 13 5 24PM 2 E Description TestCases Test Suites TestRuns Created Action 8 Elements found Page 1 of 1 1 10 vw Figure 5 2 Maintain Projects Page Klaros Testmanagement uses a horizontal menu on the top of the screen These categories resemble activities in the testing project The function categories presented in this menu are Define In the Define section of Klaros Testmanagement all arti facts that are needed in a project can be defined and viewed These artifacts are the project itself the test envi ronments the systems under test the test cases and the test suites For the Klaros Testmanagement Enterprise Edi tion and Klaros Testmanagement Mobile Edition this list also includes project iterations and requirements Plan The Plan section of Klaros Testmanagement is used to de fine and maintain jobs
204. ecuting a O see 105 TS JOD DEAN o E 106 7 R JOBS from TestiEases se 111 7 1 7 JOOS ROM Test SUITES sesiuni BE eee bee 111 PAG Jobs DV USET ASer 112 FEE 114 EA VO RE EE EE EE 114 8 2 RUN VES A NN 114 8 21 BEING a siridle Test FE eee 114 8 3 Run TESTE ee ee be 120 030 TEEN a TESE SUIE LA 120 PANNEN 123 8 4 1 CONTINUING a Suspended Test RUN sss esse eee eee 124 2 5 Import Test Results vvs 124 0 0 Creatina ISSUES TN 127 8 7 R TIS lee REVIEW ODS ee 132 vil Klaros Testmanagement User Manual Ma M R EE di 134 de Sn ele ie EE A A 134 9 1 1 Tne Overview REDOMS se 134 9 1 2 The Dashboard Reports cesses esec ss ses sesse ee Ne ee Ge AG ee Ne AG ee ee Ge ee 137 9 2 Report Templates as 142 9 3 Test RUNESON RENT eee 143 TETRIS diia 144 JAN TE Test RUM RENO ri a iia 146 MEGET ENE EEE ET EE 147 951 single Test Case Results Lue 148 TENNENE 152 SG SIGE Lest SUE Results 153 THUE 154 9 7 Ne ISSUES by TestiEasE Fe 155 9 7 2 Issue Details Creating a new ISSUE esec ecce ee ee de ee de ee de 155 ZE DNR ISSUES SS 158 9 8 I BOOKMarKING RESUS irea te dae ac 159 Vo NN 160 TOM ON io 160 10 2 Report Template S sois aii Ee OG EG N EG DE N GE DE pois 160 10 2 T REDON Details 4 161 LO SUS E E RS GE A E Ge 162 EEG EEE RA ER RS DS EE RE ES EE EE IERE DE 163 10 3 2 Deletinida User sis ie ee EE GE SE 164 1933 User Details eee 164 10 4 Mobile DEVICES re 166 19 41 MODE Device D tails LE 168 ENE EEE ETE EE EE E EG see mee
205. ed Update Test Case State State Execute IM00004 Redmine Server E Bug e Low ly httplocalhost8080 klaros web browse jsp type testCaseResult uuid df e1a01 2849 42ca alda c7f 8048cea7 Save Back The following fields are available for the Bugzilla issue management system Summary Platform Importance Components Version Milestone Description A short summary of the issue The platform the issue appears on The priority and type of the issue The components of the issue The version of the system that is affected The milestone of the system that is affected A detailed description of the issue 130 Issue Management System Summary Platform Operating System Priority Importance Components Version Milestone Description cf large text cf drop down cf multiple selection cf date time cf free text Mandatory fields must be filled Update Test Case State State Execute IM00002 Bugzilla Server E Al e Al P1 blocker Is Left Component 1 0 E hftp localhasta0a0 klaros web ibrowse jsp type testCaseResult uuid df e1a01 2849 42ca alda c7f7 8048cea7 Skip Save Back Figure 8 18 Bugzilla Issue Page The following fields are available for the Mantis issue management system Summary Reproducibility Importance Version Category Status Resolution Description Additional Information A sho
206. ed and clicking the End Test button finishes the test execution Clicking the Finish button causes Klaros Testmanagement to show the test run result of the test case Figure 8 7 8 2 1 2 The Tabular Step Instructions Screen Tabular View O T500001 Sprint Null Test Case dors Thor Passed Fi Action Start IDE n unknown 4 OOAO Action Check installed plug ins Expected Result There is support for Git Maven4 JEE web Profile WTP is enough DB Access via JDBC aeeoa gt Figure 8 5 The Tabular Step Instructions Screen 117 Execute The tabular step instructions screen shows the Description Expected Result Precondition Postcondition and result of all steps the default result being Unknown The following actions can be carried out at any time Skip Skip the current test step without changing the result of the test case i Create Issue Create an issue related to this test case in an issue management system Finish Run Finish the test run Passed Mark the test step as successfully completed Error Mark the test step result as Error Failure Mark the test step result as Failure Clicking on the result of individual steps allows the user to directly set them Clicking the Finish Run button causes Klaros Testmanagement to show the test run result of the test case Figure 8 7 Z What is the difference between a failure and an error A failure is a discrepancy between a computed o
207. ed and assigned to categories on this page The displayed test cases may be filtered and sorted as shown in Section 5 2 5 Filtering and Sorting Figure 6 21 EA Define MA Fi Evaluate 3X Configure webapp 7 Test Cases Projects New iterations Aa ETE B Categories Filter Sort El 70 Y Traceability iori Execution Steps Issues Requirements Test Environments TC00004 E 11 IDE check Low Draf Y Manual v 2 o 22808 Systems under Test TCoooo3 3 11 Medium Approved y Manual v 3 3 Sua Tcoooo2 8 10 High v Locked v Manual v 1 o RSB Test Suites TCoooo1 E 10 IDE check Low Draf Y Manual v 2 o au Traceability iori Execution Steps Figure 6 21 The Test Cases Screen The Test Cases screen shows a table with all of the test cases defined for the current project Each row of the table represents a test case the columns represent attributes of the test case Clicking on the fields of the table allows some of the most important values of a test case Name Traceability Priority State and Execution to be directly edited More attributes of a test case and its steps can be edited in on the test case details page by clicking on the Edit icon Section 6 6 3 Test Case Details The leftmost column allows test cases to be selected for bulk actions The uppermost check box is a global select button which selects or deselects all elements shown in the table Please note that the displayed elements a
208. ed from JUnit and NUnit but introducing some new functionalities that make it more powerful and easier to use TestNG is able to pro duce Unit compatible test results which can be imported into Klaros Testmanagement TUSAR stands for Thales Unified Sofware Analysis Report It is a generic metric format composed of 4 categories Cov erage Measure Test and Violations 125 Execute UnitTest UnitTest is a lightweight unit testing framework for C It was for test driven development on a wide variety of platforms Simplicity portability speed and a small foot print are all very important aspects Valgrind Valgrind is an instrumentation framework for building dy namic analysis tools xUnit net xUnit net is a free open source community focused unit testing tool for the NET Framework xUnit net works with ReSharper CodeRush TestDriven NET and Xamarin gt Support for Frameworks not listed here Even if you did not find your favorite testing framework here this does not mean that it is not already supported Many tools offer to export their result files in the JUnit XML format e g Selenium Robot and others which is a supported format If you like to see an additional format supported please contact support verit de To start the import an XML file with results from a supported test framework must be up loaded When the file upload is completed it is mandatory to select the system under test and the test en
209. ee getProperties isDefinedProperty 297 Model API Reference Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait S Sextends NamedEntity KlarosNamedEntity lt KlarosRequirementGroup RequirementGroup gt l KlarosRequirementGroup getParent KlarosRequirementGroup getChildren Set lt KlarosRequirementGroup gt getRequirements Set lt KlarosRequirement gt getAllRequirements Set lt KlarosRequirement gt getCoverage double getDepth Integer getDescendants List lt KlarosRequirementGroup gt getFamily List lt KlarosRequirementGroup gt getNumberCovered Requirements int getNumberRequirements int B 1 1 52 KlarosRevision This class encapsulates the revision related information of a klaros object B 1 1 52 1 Synopsis public abstract class KlarosRevision lt T S extends Revision gt extends KlarosNamedEntity lt T S gt implements IKlarosRevision lt T S gt Public Methods public final String getRevisionCommentO public final String getRevisionIdO 298 Model API Reference Direct known subclasses de verit klaros core model KlarosRequirement de verit k
210. een can also be viewed as a printer friendly page Figure 9 25 150 Evaluate Test Case Result TCR0000094 TC00055 Log into system Summary Description Result Timestamp Executor Execution time Test Run Test Case Test Environment System Under Test Steps Step Description Summary Action Expected Result Precondition Postcondition Step Description Summary Action Expected Result Precondition Postcondition Step Description Summary Action Expected Result Precondition Postcondition Login step failed A Failure Login step failed Apr 29 2011 2 28 PM Felix Mustermann 35 25 Second s TRUOOOOOSE Apr 29 2011 2 28 PM TCODOSS Log into system EN Y00002 Windows 7 SUTO0003 LadyPurse RCS 1 9 Passed Start browser Running OS installed internet browser Browser shows up 2 Passed Type the address of the system into the address bar and press enter Browser open Browser shows login page ES A Failure Browser displayed 404 page Enter username and password and press enter Browser shows login page Browser shows Logged in successfully page Figure 9 25 The Test Case Results Print Screen 9 5 1 2 1 Location mobile edition JE If location tracking has been enabled on the Klaros Testmanagement Mobile Edition An droid Client this tab displays an interactive map for every test case step result there is a marker displayed on
211. efined properties can be used to customize test suites within Klaros Testmanagement by adding custom fields This process is described in Section 5 2 11 User Defined Proper ties 6 7 3 2 2 Attachments Attachments may be added to test suites This process is described in Section 5 2 12 At tachments 6 7 3 2 3 Revisions Test suites are revisionable The process of revisioning an object is described in Sec tion 5 2 13 Revisions 6 7 3 2 4 Jobs Plan 1 Execute pm Evaluate X Configure Webapp 75 1 0 T500001 Sprint Null 8 Ege Projects Iterations Overview Properties User Defined Attachments Revisions Jobs 3 Results Changes Requirements Test Environments Systems under Test Summary Priority Status Progress Success Test C JOB00014 a Major New Mia mm Harald Martens vidas est Cases Test Suit JOB00013 A Major New 0 sr John Doe v EA Y est Suites JOB00005 Minor Reopened MESA 29052015 00 00 EX Torsten Divers v Zee Created 2 years ago by Devon Manager Last changed 2 years ago by John Doe Back Figure 6 30 The Test Suite Jobs Screen This tab lists all jobs in which this testsuite is included These jobs can be directly executed from within this tab See Section 7 1 Maintain Jobs for more information on how to manage jobs 102 Define 6 7 3 2 5 Results The result tab is further divided into a Test Runs and Test Suite Results tab showing the
212. egoryNode gt Methods inherited from de verit klaros core model KlarosCategoryTree getDescrip tion getRootNode getShortname Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped 319 Model API Reference Methods inherited from java lang Object equals getClass hashCode notify notifyAll B 1 1 toString wait ITT S S extends LabeledObject KlarosLabeledObject lt T S gt EE ERA RAD GEE N 8 Sextends NamedEntity KlarosNamedEntity lt W P gt EE EE EE EN TEE EG N EE EE EN EE N EE EE rl I W Wextends KlarosCategoryTree lt l W P X Y gt P P extends CategoryTree y X X extends KlarosCategoryNode lt W X Y gt 1 Y Y extends CategoryNode L KlarosCategoryTree lt KlarosTestSuite KlarosTestSuiteCategoryTree TestSuiteCategoryTree KlarosTestSuiteCategoryNode TestSulteCategoryNode gt i A KlarosTestSuiteCategoryTree 72 KlarosTestSuiteResult This class provides access to the information stored for test suite results B 1 1 72 1 Synopsis public final class KlarosTestSuiteResult extends KlarosNamedEntity lt KlarosTestSuiteResult TestSuiteResu
213. eleting the criterion on the current line 5 2 5 2 Specifying Sorting Criteria The objects displayed in Klaros Testmanagement can be sorted The criteria for the sorting are specified in the right hand table in the Filter Sort panel It is possible to specify more than one sorting option If there is more than one sorting option the uppermost row in the sorting criterion table has the highest priority and the lowest row has the lowest priority When the icon is clicked a new empty row for a sorting criterion is appended at the bottom of the table Each row in the sorting options table has a delete button i in the Action column Pressing this button removes the sorting criterion The sorting options table contains three columns The Order By column denotes the field in the results table that the sorting applies to The fields that can be sorted vary from page to page but generally include most attributes of the objects being displayed 55 Functional Overview The Type column defines the direction of the sorting sequence i e descending or ascend ing The Action column contains a button for deleting the sorting criterion 5 2 6 Print Pages Ca Sd 5 Feature only available in Klaros Testmanagement Enterprise Edition edition Most objects in Klaros Testmanagement may be viewed on a printer friendly page This print page is viewed by clicking on the print icon This icon appears in the Action column of the
214. ement getRoot KlarosRequirement getSuccessor KlarosRequirement getPredecessor KlarosRequirement getBranches Set lt KlarosRevision lt KlarosRequirement Requirement gt gt getBranchRoot KlarosRequirement getShortname String getSummary String getDescription String getPriority RequirementPriority getState String getlterations Set lt Klaroslteration gt getExternalNames Set lt String gt getAttachments Set lt KlarosAttachment gt B 1 1 49 KlarosRequirementCategoryNode An category node for requirement implementations B 1 1 49 1 Synopsis public final class KlarosRequirementCategoryNode extends KlarosCategoryNode lt KlarosRequirement KlarosRequirementCategoryTree KlarosRequirementCategoryNode RequirementCategoryNode gt 295 Model API Reference Public Constructors public KlarosRequirementCategoryNode RequirementCategoryNode wrapped Public Methods public List lt KlarosRequirement gt getReferences Methods inherited from de verit klaros core model KlarosCategoryNode getCatego ryTree getDescription getParent getShortname getSubCategories Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait IATA ET 1 W W extends KlarosCategoryNode lt l T W P gt I P Pextends CategoryNode E
215. ent Before starting this we need to update the test host Created By Changed Add Comment Created 2 years ago by John Doe Last changed 1 year ago by John Doe Save Discard Back Add Comment Close Figure 7 5 The Add a Comment Dialog The text entered in this dialog will be saved as a comment on the job once the Add Com ment button is clicked and saved To modify the comment use the icon to remove it click the icon 7 1 5 2 5 Work Log Every executed test run related to this job is logged in the Work log tab It is also possible to add own work logs to the job When clicking the Log Work button a dialog is shown where all the information can be set 110 Plan E Define da Pen LS Execute pl Evaluate X Configure 2 Issue Management System Integration F a JOB00001 Test the file upload of the ticket system FreeBSD 6828 H Maintain Jobs Save Discard Back Jobs from Test Cases Overview Properties User Defined Attachments Results Comments 1 Work Log Changes Jobs from Test Suites Jobs by User Total Time spent 0 ms Edit Work Log Entry iption pier Son 5 15 Work description Prepared test host Created By finished FER FRERE E John Doe 5 13 2015 EA Created By Finished iption Changed Log work Finished Created 2 years ago by John Doe 13 08 2013 Te 00 S Last changed 1 minute ado by John Doe Duration 00 10 00 Save Discard Back Estimated Time Left 00 50 00 Apply Close Figure 7 6 T
216. ep 3 Licensing Agreements Previous next _ Las Quit button Clicking Previous proceeds with the installation goes The third step shows information about the license agreement for Klaros Testmanagement The license must be accepted to continue the installation Figure 3 3 21 Installation ern Y klaros Please read the following license agreement carefully Limited Use Software License Agreement PLEASE READ THIS AGREEMENT CAREFULLY BEFORE ATTEMPTING TO USE THE SOFTWARE OF verit Informationssysteme GmbH AND RELATED DOCUMENTATION COLLECTIVELY THE SOFTWARE AND BEFORE INSTALLING OR USING THE SOFTWARE BY INSTALLING OR USING THE SOFTWARE YOU ARE CONSENTING TO BE BOUND BY THIS AGREEMENT Subject to the terms and conditions of this Agreement verit Informationssysteme GmbH verit grants vou a personal non exclusive and non transferable right to use the Software Any copies made must contain all copyright notices that appear on the furnished Software Except in the context of Art 69e of the German Copyright Act vou may not do any of the following 1 modify the Software 2 reverse assemble reverse engineer reverse compile or otherwise attempt to create a source code equivalent of the Software 3 remove any proprietary notices or labels pertaining to the Software or 4 transfer sell publish sublicense rent I accept the terms of this license agreement I do not accept the
217. er Parameter 11 3 Example Report This section provides an example report which shows how to retrieve test case results and how to display them depending on their status 11 3 1 Creating the Groovy Script The following code snippet shows the frame for a Groovy script with the required imports The code to retrieve the data must be implemented in the execute method A more detailed description of the Klaros Testmanagement API can be found in de verit klaros core model import de verit klaros scripting import de verit klaros core model x import java util x public class TestScript implements KlarosScript public void execute KlarosContext context The next step in the data retrieval process is to actually get the required data The following code snippet shows how to build a query string and how to get the data StringBuffer query new StringBuffer query append select tcr from KlarosTestCaseResult tcr List lt gt tcr context executeQuery query toString The data is returned in a List object that must be stored in the context so that it can later be accessed from the report template The code snippet below shows how to store the list in the context For more information on building queries please consult the HQL documentation context add results tcr The List object is stored in the context with the name results and can be accessed from the report template by this name If more data is
218. eration public KlarosConfiguration getActiveProject 322 Model API Reference public String getAttachmentUrl String attachmentId public String getAttachmentUrlcUUID attachmentId public String getBrowsePageUrl KlarosLabeledObject lt gt artifact public Locale getLocale public Parameter getParameter String name public Object getParameterValue String name public String getPrintPageUrl KlarosLabeledObject lt gt artifact public void setLocale Locale locale Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait KlarosContext context Context activeProjectld UUID activelterationld UUID factory KlarosQueryFactory parameters ParameterContext KlarosContext context Context activeProjectld UUID activelterationld UUID factory Klaros ueryFactory parameters ParameterContext locale Locale add name String value Object void getActiveProject KlarosConfiguration getActivelteration Klaroslteration ex ecuteQuery query String List lt gt ex ecuteParameterizedQuery query String List lt gt getParameter name String Parameter getParameterValue name String Object getAttachmentUrl attachmentld UUID String getAttachment Url attachmentld String String getBrowsePageUrl artifact KlarosLabeledObject lt gt String getPrintPageUrl artifact KlarosLabeledObject lt String getLocale Locale setLocale local
219. ernate properties must be edited as shown below 37 Installation The hibernate connection ur1 property must match the location of the database in your net work Please consult your database administrator for the hibernate connection username hibernate connection password credentials to use To use a Microsoft SOL Server change the content of the file to hibernate dialect org hibernate dialect SQLServer2008Dialect hibernate connection driver_class com microsoft sqlserver jdbc SQLServerDriver hibernate connection url jdbc sqlserver localhost 1433 database ame KLAROS hibernate connection username root hibernate connection password root For MariaDB MySQL change the content of the file to hibernate dialect org hibernate dialect MySQL5InnoDBDialect hibernate connection driver class com mysql jdbc Driver hibernate connection url jdbc mysql localhost 3306 klaros hibernate connection username root hibernate connection password root For Oracle please use the following hibernate dialect org hibernate dialect Oraclel0gDialect hibernate connection driver_class oracle jdbc driver OracleDriver hibernate connection url jdbc oracle thin localhost 1521 klaros hibernate connection username root hibernate connection password root To use PostgreSQL change the content of the file to hibernate connection driver_class org postgresql Driver hibernate connection url jdbc postgresql localhost klaros hibernate dialect o
220. est 00000000 A Changing User Roles Users can not change their own System Account flag or Role 164 Configure Issue Management System Integration E Define Plan po Execute fm Evaluate E Configure amp 3 Lisa Ricardi Overview Back Report Templates users Properties Project Roles Results Connection Log Changes Mobile Devices Full Name Lisa Ricardi New Password User Name tester2 Retype new Password System E Mail Role Tester v Integration System Account Backup Mandatory fields must be filled Created by John Doe on 11 18 13 5 44 PM Last changed by John Doe on 11 18 13 5 47 PM Back Figure 10 7 The Edit User Screen Clicking the Save button submits the changes while clicking the Cancel button dis cards them 10 3 3 1 Results This section contains a Results tab as described in Section 5 2 14 Related Test Runs and Results 10 3 3 2 Project Roles cnierprise Feature only available in Klaros Testmanagement Enterprise Edition 7 edition j The Project Roles tab shows the project roles the user has for all project with secured access see Section 6 1 6 4 Securing access to the Project for more information on how to secure access to projects Administrators can change the project roles for all users and projects here ws SN E Plan Execute Fi Evaluate E Configure Sprint1 Test GPS Trackng amp l Erika Mustermann Overview
221. etConverter Set lt gt testrun Converts Collections into a ArrayList Parameters testrun the testrun return the converter B 2 3 2 4 getDate Date public String getDate Date date Return the formatted date string of the given date Parameters date the date return the formatted date string 333 Model API Reference B 2 3 3 TestRunReport The Class TestRunReport A java snippet to create an Test Run Report Template B 2 3 3 1 Synopsis public class TestRunReport implements KlarosScript Public Constructors public TestRunReportO Public Methods public void addResult String verdict KlarosTestCaseResult testResult Map lt String List lt KlarosTestCaseResult gt gt resultMap public final void execute KlarosContext context public final String getColor int index public final List lt gt getConverter Set lt gt testrun public final String getDate Date d public final String getDateOnlydlong d public final List lt gt getSortTestRuns List lt gt testRuns KlarosContext context public final int getTestCaseError KlarosTestCaseResult result public final String getTestCaseResult KlarosTestCaseResult result public final int getTestCaseStepError KlarosTestCaseStepResult result public final String getTestCaseStepResult KlarosTestCaseStepResult result Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait TestRunReport TestR
222. etStartDate public abstract Date getStartDateQ Gets the start date Parameters return the start date B 1 1 9 11 getSuccessCriteria public abstract String getSuccessCriteria Gets the success criteria Parameters return the success criteria B 1 1 9 12 getSuts public abstract Set lt KlarosSUTImplementation gt getSuts Gets the systems under test associated with this iteration Parameters return the systems under test B 1 1 9 13 getTestRuns public abstract Set lt KlarosTestRun gt getTestRuns Gets the test runs associated with this iteration Parameters return the test runs B 1 1 10 IKlarosjob This interface provides access to the data of a job B 1 1 10 1 Synopsis public interface IKlarosJob extends IKlarosNamedEntity Public Methods public public public public public public public public public public public public public abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract Set lt KlarosAttachment gt getAttachmentsO KlarosConfiguration getConfiguration String getDescription Date getDueDate KlarosTestEnvironment getEnvO String getEstimatedTime Long getEstimatedTimeInMilliseconds JobPriority getJobPriorityO JobStatus getJobStatus JobType getJobTypeO KlarosJob getParentO Integer getProgress Date getStartDate 231 public public
223. eters return the priority B 1 1 16 10 getRequirementGroup public abstract KlarosRequirementGroup getRequirementGroup Get reduirement group Parameters return The requirement group the requirement belongs to B 1 1 16 11 getShortname public abstract String getShortname Gets the shortname Parameters return the shortname B 1 1 16 12 getState public abstract String getState Gets the state Parameters return the state B 1 1 16 13 getSummary public abstract String getSummary Gets the summary Parameters return the summary B 1 1 17 IKlarosRequirementGroup The interface to retrieve the information about a requirement group B 1 1 17 1 Synopsis public interface IKlarosRequirementGroup extends IKlarosNamedEntity 242 Model API Reference Public Methods public public public public public public public public public public abstract abstract abstract abstract abstract abstract abstract abstract abstract abstract Set lt KlarosRequirement gt getAllRequirementso Set lt KlarosRequirementGroup gt getChildren double getCoverage Integer getDepthO List lt KlarosRequirementGroup gt getDescendants List lt KlarosRequirementGroup gt getFamilyO int getNumberCoveredRequirements int getNumberRequirements KlarosRequirementGroup getParent Set lt KlarosRequirement gt getRedguirementsO B 1 1 17 2 getAllRequirements public abstract Set lt K
224. eters 330 user 330 WRAPPER PREFIX 325 Finish Run 118 I IKlarosAttachment 216 IKlarosCategoryNode 217 IKlarosCategoryTree 219 IKlarosConfiguration 220 IKlarosContext 326 IKlarosEnumValue 224 IKlarosExternallmplementation 224 IKlarosExternalLink 225 IKlarosIssue 226 IKlarosIteration 228 IKlarosjob 231 IKlarosjobTimeBlock 233 359 IKlarosjobUpdateAction 235 IKlarosLabeledObject 236 IKlarosNamedEntity 237 IKlarosProperty 238 IKlarosRequirement 239 IKlarosRequirementGroup 242 IKlarosRevision 245 IKlarosSUTImplementation 247 IKlarosTag 250 IKlarosTestCase 251 IKlarosTestCaseResult 257 IKlarosTestCaseState 261 IKlarosTestCaseStep 262 IKlarosTestCaseStepResult 263 IKlarosTestEnvironment 267 IKlarosTestExecutable 268 IKlarosTestRun 268 IKlarosTestSuite 272 IKlarosTestSuiteResult 275 IKlarosUser 276 imageProvider 330 Interfaces IKlarosAttachment 216 IKlarosCategoryNode 217 IKlarosCategoryTree 219 IKlarosConfiguration 220 IKlarosContext 326 IKlarosEnumValue 224 IKlarosExternallmplementation 224 IKlarosExternalLink 225 IKlarosIssue 226 IKlarosIteration 228 IKlarosjob 231 IKlarosjobTimeBlock 233 IKlarosjobUpdateAction 235 IKlarosLabeledObject 236 IKlarosNamedEntity 237 IKlarosProperty 238 IKlarosRequirement 239 IKlarosReduirementGroup 242 IKlarosRevision 245 IKlarosSUTImplementation 248 IKlarosTag 250 IKlarosTestCase 251 IKlarosTestCaseResult 257 IKlarosTestCas
225. evice gets deactivated the only thing that happens is that subsequent logins are denied for that user The complete history of that user as well as any testing data related to that user is kept in the connected database Installation 3 2 Prerequisites Since Klaros Testmanagement is a web based application the client and the server side have different installation prerequisites which are explained in detail in the next sections 3 2 1 Client Prerequisites To access Klaros Testmanagement modern web browser supporting JavaScript is required name en Microsoft Internet Explorer Version 7 and above Mozilla Firefox Version 3 5 and above Google Chrome Version 4 and above Safari Version 4 and above Table 3 1 Supported Browsers Please note that Konqueror is currently not a supported browser due to issues with the provided JavaScript engine A Caution Klaros Testmanagement requires a minimum screen resolution of 1280x1024 pixels 3 2 2 Server Prerequisites To run the Klaros Testmanagement server a Microsoft Windows or Linux operating system running Oraclejava version 7 or 8 is required Warning 4 There are known issues when using alternative Java implementations like GCJ or IcedTea OpenJDK which can per default be found in common Linux distributions Using these implementations is strongly discouraged and not supported For optimal performance using a separate database installation is highly recommende
226. exception must be added for Klaros Testmanagement in order to execute tests manually 8 2 1 1 The Step by step Instructions View Tabular View K TS00001 Sprint Null Test Case dors TC00001 IDE check step TT Result O Action Check installed plug ins Expected Result There is support for Git Mavend JEE web Profile WTP is enough DB Access via JDBC AE AEO ASO Figure 8 4 The Step by step Instructions View The step by step instructions screen shows the Action Expected Result Precondition and Post condition values of the current test step Depending on the results of the step the user can click the following buttons Mark the test step as successfully completed Mark the test step result as Error Mark the test step result as Failure Skip the current test step without changing the result of the test case 116 Execute Skip all test steps without changing the result of the test case Create Issue Create an issue related to this test case in an issue management system Link Issue Link an existing issue from an issue management system to this test case Back Go back to the last test step to repeat it again or to edit it lt Note The verdict e g Passed Skipped etc of already executed test steps is shown in the test runner The same process is applied for each test step of the test case Clicking the Next Step button continues the test even if an error or failure occurr
227. external applications on a regular basis The synchronization supports creating and updating as well as revisioning of require 203 Import Export ments Changes to the requirements will be reflected in the Klaros Testmanagement data base on a per field basis for each synchronization action A Y Y Synchronization overrides local changes Be aware that all data received via synchronization will overwrite any changes made to the requirements stored in Klaros Testmanagement Required Synchronization Element externalrd Supplying the externalld element See Section D 7 lt externalld gt will identify a requirement for subsequent synchronisation attempts It is required field when using this interface If you change this value a new requirement object will be created instead of replacing the content of the previously created requirement Optional Synchronization Element externalrevision Supplying the externalRevision element See Section D 8 lt externalRevision gt will identify a new revision of a requirement for subsequent synchronisation at tempts It is optional when using this interface If you add this value and it does not match a previous revision of yet existing requirement matching the supplied externalld a new requirement revision will be created instead of replacing the content of the existing requirement The following example shows how to synchronize an XML file containing requirements into the pr
228. f public abstract KlarosTestCase getImplementation0f O Get related test case Parameters return The test case for which this is an implementation B 1 1 7 IKlarosExternalLink This interface provides access to externally stored information about an object B 1 1 7 1 Synopsis public interface IKlarosExternalLink Public Methods public abstract String getReference B 1 1 7 2 getReference public abstract String getReference Get the reference to the externally stored information Parameters return The reference to the information 225 Model API Reference B 1 1 8 IKlarosIssue This interface provides access to a software issue B 1 1 8 1 Synopsis public interface IKlarosIssue Public Methods public abstract KlarosSUTImplementation getAcceptedIn public abstract Date getCreationDate public abstract String getDescription public abstract String getExternalld public abstract Date getLastSynched public abstract String getOwner public abstract String getPriorityO public abstract String getReporter public abstract String getResolution public abstract String getState public abstract String getSubjectO public abstract Set lt KlarosTestCase gt getTestCases B 1 1 8 2 getAcceptedIn public abstract KlarosSUTImplementation getAcceptedInQO Gets the system under test this issue has been accepted detected in Parameters return the system under te
229. from java lang Object equals getClass hashCode notify notifyAll toString wait 324 Model API Reference KlarosQueryFactory WRAPPER PREFIX String KlarosQueryFactory session Session execute query String List lt gt execute query String params ParameterContext List lt gt B 2 1 2 2 KlarosQueryFactory Session public KlarosQueryFactory Session session Create a KlarosQueryFactory Parameters session Passed by the relating servlet B 2 1 2 3 WRAPPER PREFIX public static final String WRAPPER PREFIX Klaros The prefix for klaros interfaces B 2 1 2 4 execute String public List lt gt execute String query Prepares the given query string with our KlarosOdaQuery and returns a KlarosList with the results of the query Parameters query the query return the list of query results B 2 1 2 5 execute String ParameterContext public List lt gt execute String query ParameterContext params Prepares the given query string with our KlarosOdaQuery and returns a KlarosList with the results of the query Parameters query the query params the parameters 325 return Model API Reference the list lt gt B 2 1 3 KlarosScript Public interface that all seam pdf template scripts must implement be work properly B 2 1 3 1 Synopsis public interface KlarosScript Public Methods public abstract void execute KlarosContext context
230. ge Figure 6 23 allows the user to view or change the following attributes of the selected test case e ID Assigned automatically s Revision Assigned automatically and incremented every time a test case is changed e Name 94 Define The editable name of the test case Description The textual description of the test case Precondition The precondition for this test case describing the requirements for executing the test case e g It is required that the database is initialized Postcondition The postcondition defines the criteria that must be fulfilled after the test case has been executed e g the postcondition of a successful login test case is that the user is authen ticated and the home page of the application appears Area The area this test case covers Functional Non Functional Structural Regression Retest Design Technique The test design view on the system under test Black Box or White Box Variety The result expectation of the test Whether a positive or negative result is expected Team The team that is responsible for the test case Level The test level of the test case for example unit integration or system test Priority The priority of the test case Low Medium or High Docbase A reference to the document this test case is based on which may e g contain the re quirements this test case is related to Note A note that may contain additional information regarding the test
231. gement proper discards all changes WebApp Het RO This tab contains settings which govern the behavior of Klaros Testmanagement The fol lowing settings can be controlled here s Application URL This URL must be set if the application runs behind a proxy The proxy is responsible to redirect the user reduest to a physical URL More information about rewriting URLs can be found at http httpd apache org docs 2 0 mod mod_proxy html Press the Check Application URL link to test if the URL has been entered correctly s Maximum Upload File Size Byte The maximum attachment size which can be uploaded Changing this value requires a restart of the application server 169 Configure Use the default container session timeout If checked the default tomcat session timeout will be used 30 minutes e Session Timeout Minutes If the checkbox above is unchecked this value is used as the session timeout delay Authentication required for import If true user credentials are required to import results e g using Jenkins Hudson plugin See also Section 12 5 2 1 Jenkins Hudson Plugin for Klaros Testmanagement s Create test suite results when importing test case results If true test suite results are automatically created for the corresponding test suite infor mation contained in the result file This information may vary with the import format Ad ditionally a corresponding test suite is created for the test s
232. getTestSuiteCategoryTrees Set lt KlarosTestSuite gt getTestSuites Boolean isSecured 220 Model API Reference B 1 1 4 2 getDescription public abstract String getDescription Returns the project description Parameters return The description of the project B 1 1 4 3 getEnvs public abstract Set lt KlarosTestEnvironment gt getEnvs Returns the project test environments Parameters return Set containing the test environments of the project B 1 1 4 4 getIterationCategoryTrees public abstract Set lt KlarosIterationCategoryTree gt getIterationCategoryTrees Returns the project requirement category trees Parameters return Set containing the iteration category trees of the project B 1 1 4 5 getIterations public abstract Set lt KlarosIteration gt getIterations 221 Model API Reference Returns the project iteration Parameters return KlarosSet containing the iteration objects of the project B 1 1 4 6 getjobs public abstract Set lt KlarosJob gt getJobsO Returns the project jobs Parameters return KlarosSet containing the job objects of the project B 1 1 4 7 getRequirementCategoryTrees public abstract Set lt KlarosRequirementCategoryTree gt getRequirementCategoryTrees Returns the project requirement category trees Parameters return Set containing the requirement category trees of the project B 1 1 4 8 getRequirements public abstract Set lt Klaros
233. goryTree getShortname String getDescription String getRootNode KlarosCategoryNode lt l W X Y gt B 1 1 35 KlarosConfiguration This class provides access to the information stored for project s configuration B 1 1 35 1 Synopsis public class KlarosConfiguration extends KlarosLabeledObject lt KlarosConfiguration Configuration gt implements IKlarosConfiguration Comparable lt KlarosConfiguration gt Public Methods 280 Model API Reference public int compareTo KlarosConfiguration 0 public boolean equals Object o public String getDescription public Set lt KlarosTestEnvironment gt getEnvs public Set lt KlarosIterationCategoryTree gt getIterationCategoryTrees public Set lt KlarosIteration gt getIterations public Set lt KlarosJob gt getJobsO public Set lt KlarosRequirementCategoryTree gt getRequirementCategoryTrees public Set lt KlarosRequirement gt getRequirements public Set lt KlarosSUTImplementation gt getSuts public Set lt KlarosSUTImplementationCategoryTree gt getSystemUnderTestCategoryTrees public Set lt KlarosTestCaseCategoryTree gt getTestCaseCategoryTrees public Set lt KlarosTestCase gt getTestCases public Set lt KlarosTestEnvironmentCategoryTree gt getTestEnvironmentCategoryTrees public Set lt KlarosTestRun gt getTestRuns public Set lt KlarosTestSuiteCategoryTree gt getTestSuiteCategoryTrees public Set lt KlarosTestSuite gt getTestSuites
234. gt Figure 5 3 The Help Menu The help menu provides quick links to various Klaros Testmanagement resources Pressing the help menu icon opens a menu appears displaying the following links The Help Menu Documentation Opens up the section of the Klaros Testmanagement docu mentation corresponding to the currently displayed page Tutorial Opens up the Klaros Testmanagement tutorial Message Boards Opens up the Klaros Testmanagement message boards Contact Support Prepares an e mail to be sent to the Klaros Testmanage ment support team This option should be used when ex periencing an issue using Klaros Testmanagement which can t be solved using the documentation or the message boards 51 Functional Overview 5 2 2 The User Menu John Doe Administrator VE informationssysteme ie a J Figure 5 4 The Help Menu Button The user menu button on the upper right of Klaros Testmanagement displays the full name of the user that is currently logged in G John Doe Administrator veril informationssysteme ES English en_US German de DE ES Logout Figure 5 5 The Help Menu Pressing the user menu button opens up the user menu where the user can change the language and log out of Klaros Testmanagement 5 2 3 Search Quick Select Depending on the Klaros Testmanagement edition the upper right corner see Figure 5 6 either contains a search field for fast navigation to elements with a given I
235. gt lt p paragraph gt lt p text value failure gt lt p paragraph gt lt p cell gt lt ui fragment gt sui fragment rendered tcr passed gt lt p cell backgroundColor rgb 0 255 0 verticalAlignment top horizontalAlignment center gt lt p paragraph gt lt p text value passed gt lt p paragraph gt lt p cell gt lt ui fragment gt lt p cell verticalAlignment top horizontalAlignment left gt lt p paragraph gt lt p text value tcr description gt lt p paragraph gt lt p cell gt lt p cell verticalAlignment top horizontalAlignment left gt lt p paragraph gt lt p text value tcr summary gt lt p paragraph gt lt p cell gt lt Print the testcase description below the result row To differ from the next row use a bigger border for the bottom gt lt p cell colspan 4 verticalAlignment top horizontalAlignment left borderWidthBottom 1 paddingBottom 3 gt lt p paragraph gt sp font size 6 style bold gt lt p text value Testcase description gt lt p font lt p font size 6 gt 357 Reporting Resources lt p text value tcr testCase description gt lt p font lt p paragraph gt lt p cell gt lt ui repeat gt lt p font lt p table lt p document 358 Index A applicationBaseUrl 330 B Back 117 C Categories 57 Classes IterationsReport 330 JobReport 332 Klar
236. guage to become available in Klaros Testmanagement A valid language file has a name of the form messages language COUNTRY variation properties where language is the two letter ISO 639 code for the language in lower case COUNTRY is the two letter ISO 3166 code for the country in upper case and variation is an optional user definable code for the variation of the language e g dialect e Language File Encoding The language file must use ISO 8859 1 encoding with Unicode escapes NuXXXX If you prefer editing these files as UTF 8 please use a converter like native2ascii or iconv to translate them to a proper format After Klaros Testmanagement is run for the first time the American English German and fallback language files will be copied to the klaros resources messages folder In order to create a new language file the text should be copied out of one of these files into an appro priately named file The contents of the file consist of key value pairs in the form key This sentence is the value None of the keys should be altered The values the text after the should be translated into the target language When Klaros Testmanagement is started the default language files messages properties messages_en_US properties and messages_de_DE properties are copied to the klaros re sources messages folder overwriting any changes made to these files Therefore it is ad vised that any user changes to the American Eng
237. gure 2 2 Test Case Step Introduction A test case step consists of a Precondition the state of the System under Test before the test starts an Action explains what the user has to do test try out After the action the outcome should be the Expected Result and a Postcondition the state of the system un der test after the action Klaros Testmanagement guides the user through the test case step by step During the test execution every step will be assigned a Test Case Step Result which contains the verdict of the test case step Passed Failed Error or Skipped are the pos sible verdicts which are available to the user If the precondition postcondition or expected result does not match the description the User should choose Failure If an unexpected error in the system prevents the user from carrying out the step for example a button is missing they should choose Error If one of the test case step result verdicts is marked as Error or Failure the whole test case result is also marked with that particular verdict Only if every test case step is marked as passed the encapsulating test case result is marked as passed Automated test cases usually have no test case steps because they are executed with an automated test program e g JUnit These test case results can be imported and stored with the other test related data into the database Requirements are another type of artifact in Klaros Testmanagement which represent a con diti
238. hanges Requirements Test Environments Source Project P00002 XyPlanner 0 R 5 ENV 2 SUT 2 TC 1 TS v Systems under Test z y R E 3 E 7 Q Relations between copied objects will be preserved however previously copied objects will be ignored Test Cases Test Suites Requirements 0 Test Environments 5 Systems under Test 2 Test Cases 2 Test Suites 1 70 v ENV00005 Windows 2000 ENVOOOO4 Windows XP ENV00003 Windows XP SP1 ENV00002 Windows XP SP2 ENV00001 Windows XP SP3 ID Description OOR S S Selected 3 test environments 1 SUT 2 test cases 1 test suite Copy Created by Felix Mustermann on 7 23 14 10 17 AM Last changed by Felix Mustermann on 7 23 14 10 17 AM Back Figure 6 3 Copying Objects to the Current Project After selecting the desired objects pressing the Copy button opens up a popup with a summary of all objects that are going to be copied to the current project Pressing the yes button closes the popup and starts the copy operation see Figure 6 4 Copying Objects from another Project Plan G Execute pil Evaluate Configure 17R00002 Traffic controller system t L DB P00010 a as erations Properties User Defined Requirements a d A The following objects will be copied to this project Test Environments Source Project P00002 XyPlal Systems under Test c sg 2 Q Relations between copied Test Environments Description ENV00005 Windows 2000
239. hat is running the Klaros Testmanagement application server During the indexing process the amount of open files may exceed the predefined limit in the Linux operating system The command ulimit n shows the configured number of open files allowed which should be set to a value of at least 4096 Please consult your system documentation on how to set this value Usually by editing etc security limits conf 3 2 2 5 Disc Space Klaros Testmanagement stores binary attachments in a file based repository inside the klaros folder in home directory of the user account that is running the Klaros Testmanage ment application server Depending on the usage pattern a sufficient amount of disk space should be reserved for this account If the file based Derby database is active the database files will per default also be located in the user home directory 00000000 Note El Reserving 10GB of disc space should be enough for typical usage patterns 3 3 Installation Process Under Windows the installer is invoked by running Klaros Setup exe Under Linux the installer can be started by entering java jar Klaros Setup jar in a user shell The following screens show each step involved in installing Klaros Testmanagement 3 3 1 Step 1 Welcome The initial step shows a welcome screen to the user Figure 3 1 Installation Information Step 1 of 10 ATOS 4 community edition enterprise edition mobile edition Version 4 3 2
240. he test case Execute Test Case TC00001 Test the file size limitation when attaching large files to emails Test Case Details ID TC00001 Revision 1 0 Name Test the file size limitation when attaching large files to emails Description There is a configurable file size limit when attaching files to emails When uploading a file whose size exceeds this limit a warning message should be displayed to the user and the operation should be cancelled Precondition Postcondition Expected Result Team State Approved Area Functional Design Technique Variety Level Priority High Docbase Note Dependency Evaluation Execution Manual Traceability TestEnvironment Ubuntu 12 10 v System under Test email client v Execute Cancel Figure 8 3 The Single Test Case Execution Dialog Before a test run can be started the test environment the test is run in and the system under test itself have to be defined User defined properties may also be set for the test run here Creating Test Environments and Systems under Test For information on how to create a test environment or a system under test please refer to Chapter 6 Define Pressthe Execute button to run the test case By default the step by step instructions screen will open but this can be changed to the tabular step instructions view by marking the tabular view checkbox 115 Execute lt Note Pop ups must be enabled in your browser or an
241. he Log Work Dialog The duration field must contain a number greater than zero in order for the work unit to be logged Then click Add and hen Save to save you log work To modify a work log entry use the icon to remove it click the Ef icon 7 1 5 2 6 Bookmarking Jobs Jobs may be linked to from outside of Klaros Testmanagement using the link on the bookmark icon Right click the icon and choose Copy Link Location Firefox Chrome or the equivalent option 7 1 6 Jobs from Test Cases On this page the user can generate jobs from the selected test cases pad E Detine amp Pan ES Execute ffi evaluate X Configure Sywebapp p Jobs from Test Cases Maintain Jobs Jobs from Test Cases Jobs from Test Suites Fitter Sot 15 ID Revision Name Traceability Priority State Execution Medium Draft Manual E TC00003 1 0 Continuous Integration check AL EL F Tcooo02 1 0 Project setup check High Locked Manual TCO0O0001 1 0 IDE check Low Draft Manual Schedule Execution Schedule Review Figure 7 7 The Jobs from Test Cases Screen When the Generate button is clicked Klaros Testmanagement generates a job for every selected test case using the specified Assignee System under Test and Test Environment Each generated job is created with the corresponding test case set in its Test Case field 7 1 7 Jobs from Test Suites On this page the user can generate jobs from the selected
242. he icon this job can have a test case or test suite Here you can choose witch job should be the parent then click Assign Next to the job ID the number of subordinate jobs in this parent is shown The success and progress rate shown on the parent job is derived from the contained jobs Warning Jobs which have a test case or test suite assigned to them may not have sub jobs and so will not be available as possible parent jobs in the New Parent Dialog 7 1 4 Executing a Job Clicking the icon executes the job A user in the role tester is only able to execute or jobs which are assigned to him If the job is associated with a test case the Run Single Test Case dialog will be opened A detailed description of how to run a test case can be found in Section 8 2 Run Test Case If the job is associated with a test suite the Run Test Suite dialog will be opened A detailed description of how to run a test suite can be found in Section 8 3 Run Test Suite 105 Plan Note If the job is associated with an automated test case or the test suite contains only automated test cases Klaros Testmanagement will display the page to im port test results More information about importing results can be found in Sec tion 8 5 Import Test Results 7 1 5 Job Details 7 1 5 1 Job Overview Define eo Execute p Evaluate KN Configure _ JOB00005 Manual iteration test Jobs from Test Cases Overview Propertie
243. he installation 3 3 9 Step 9 Setup Shortcuts The ninth step requests the options for shortcuts The installer can create shortcuts in the Start Menu and on the desktop Figure 3 10 26 Installation Setup Shortcuts Step 9 of 10 Create shortcuts in the Start Menu Select a Program Group for the Shortcuts create shortcut for 5 current user 9 all users Klaros Testmanagement Made with IzPack http izpack org Figure 3 10 Setup Shortcuts Screen This step looks different on Linux installations but has the same functionality The installation may be aborted by clickingthe Quit button Clicking Previous goes back to the Perform External Processes step and clicking Next proceeds with the instal lation 3 3 10 Step 10 Installation Finished The tenth step notifies the user that Klaros Testmanagement was installed successfully and shows the path to the uninstaller program Figure 3 11 27 Installation Installation Finished gt Y klaros Installation has completed successfully An uninstaller program has been created in C Users gidley Klaros Testmanagement Uninstaller Generate an automatic installation script Made with IzPack http izpack org Figure 3 11 Installation Finished Screen The Generate an automatic installation script button saves a complete script of the installation with the selected user choices so that the same installation could be repeated unatten
244. he project data that has previously been exported The user can browse for a backup file and upload it The screen will show the projects contained in the uploaded file and the user is able to select one or more projects or click the Select all option to select all the projects for restoration Figure 10 31 4 Define Plan po Execute qa Evaluate E Configure Test GPS Tracking Backup Overview Export import Report Templates U oe Q Version 3 29 Mobile Devices 3 Created by Felix Mustermann on 11 3 13 5 01 PM System 10 v Integration Description Test Cases Test Runs Einrichten des neuen Rechenzentrums 2 0 Testing the email client 1 0 C Issue Management System Integration 1 0 Bestellprozess 2 0 Test GPS Tracking 3 3 Description Test Cases Test Runs Upload Backup File Discard Figure 10 31 The Import Tab Clicking the Import button imports the selected project data and clicking the Can cel button cancels the restore Note The import action will not overwrite existing projects or other existing artifacts therein 184 Configure Important If you try to import a backup file from a previous Klaros database version this import will be rejected with a corresponding error message You need to import that backup in a compatible Klaros release installation first and update that to your current release A subsequent export will then yield a compatible backup file 185
245. his product uses icons from the Tango Desktop Project http tango freedesktop org which are released to the Public Domain We thank the authors for their worthwhile efforts This product uses icons from the Fugue Icon Set http www pinvoke com which are available un der a Creative Commons Attribution 3 0 license This product uses icons from Patricia Clausnitzer s pc de Icon Sets http pc de icons which are available under a Creative Commons Attribution 3 0 license Table of Contents Eee EED ED EE EE E ed EE EE et 1 1 1 Klaros Testmanagement Community Edition Features sees eee eee e eee see ses ee de 1 1 2 Klaros Testmanagement Enterprise Edition Features esse eee sesse see de see ee dee 2 1 3 Klaros Testmanagement Mobile Edition Features sisie ss ss see see see de ee ee ee 3 ZOO UE ON ED rr REE TE 5 2 1 What is Klaros Testmanagement esse ss se se ek AG ee Ne AE Sk AG ee Ne AG ee ee 5 2 2 Test Cases The Basis of Testing esec eee 5 2 5 TESE Suites Organizing Test Cases a ll 6 2 4 Test Runs Executed Tests with their Results siese eee eee 7 2 5 Test Environment and System under Test Influences of Test Results 7 2 6 Iterations Subdividing your project into phases sese eee eee 7 2 7 Requirements Meeting Quality Standards siese see eee eee ee de 8 2 8 Jobs Planning the test Process sinesmenei iee E E 8 2 9 User Roles Every User has his Rights
246. his test run if available Parameters return The test suite executed with this test run B 1 1 28 15 getTimestamp public abstract Date getTimestamp Get timestamp Parameters return The time the test run has been executed as Date object B 1 1 28 16 getWork public abstract Set lt KlarosJobTimeBlock gt getWork Get the job time blocks of this test run Parameters return Set of job time blocks B 1 1 28 17 isPending public abstract boolean isPendingO Checks if the test run is pending This means that it has not yet been completely executed Parameters return true if the test run is pending B 1 1 29 IKlarosTestSuite This interface provides access to data of a test suite B 1 1 29 1 Synopsis public interface IKlarosTestSuite lt T S extends Revision gt extends IKlarosRevision lt T S gt Public Methods public abstract Set lt KlarosAttachment gt getAttachments public abstract Set lt KlarosTestSuiteCategoryNode gt getCategories public abstract KlarosConfiguration getConfigurationO public abstract List lt KlarosTestSuiteResult gt getResults public abstract String getShortnameO public abstract KlarosSUTImplementation get Sut 1 public abstract List lt KlarosTestCase gt getTestCases public abstract Integer getlestSuiteResultCountO 272 Model API Reference B 1 1 29 2 getAttachments public abstract Set lt KlarosAttachment gt getAttachmentsO Gets the attachmen
247. ically assigned by Klaros Testmanagement 6 4 3 Test Environment Details This section allows in depth editing of an individual test environment including user defined properties The executed test results and change history for the test environment are also visible in this section 6 4 3 1 Test Environment Overview Plan 44 Execute ffl Evaluate X Configure wm ENV00011 Solaris 11 2011 11 SES Projects iterations Overview Properties User Defined Attachments Results 17 Changes Requirements Test Environments Success History Systems under Test Test Cases Success NE Progress MET MO METER Test Suites Success Results N Progress E Compliance E Coverage Compliance Coverage CW 9 CW 13 CW 14 Test Run Most unstable Systems under Test ID System under Test TestRuns Success Progress Compliance Coverage Action SUTO0006 0 2 SNAPSHOT 6 s EE HEM SUTO0020 02 gt EE HE N EM ee Show all Latest failing Test Cases ID e Name Start Executor Test Run System under Test Duration Result Action TC00004 Kopie von IDE check 4 2 15 5 55 11 PM John Doe TRU0000064 0 2 00 00 09 A Q TC00001 IDE check 3 24 15 11 17 53 AM John Doe TRUO0000053 0 2 SNAPSHOT 6 00 00 08 A Q Show all Created 3 months ago by John Doe Last changed 3 months ago by John Doe Back Figure 6 17 The Test Environment Overview Tab e Success The success rate shows how many test cases have been successfully executed in this
248. iew Job during Execution sees eee eee ee eee eee 133 The DESSE 134 9 2 The Test Environment Overview Report Layout sse eee eee ee eee e eee e eee ee de ee ee 135 9 3 Tie SUT Overview Report Layout Laser 136 9 4 The Test Suite Overview Report Layout sese eee eee ee eee eee 137 9 5 The Project Overview Report cesses eee ee eee e eee eee eee 138 9 6 The Latest Success Rate Report sissies sesse se ee Sk AG ee Ne ee a ee Ne ee ee ee 139 9 7 IMe Test AAN RED sees 140 9 8 The Project Health Matrix Report rowrnnrrnnnnernnrrnnnnernnnrnnennrennnnnvnnnrnnnnnnnnnnnnnnnennnsnee 140 39 9 The Test Progress Revus See 141 9 10 The Test Progress History Report ii SS DS es naa 142 9 11 User Defined Reports Screens sisie de de AA Ak ede de ee Ge ede de 142 9 12 Generate a parameterized Report esse ecce eee eee 143 9 13 me Test RUM History REP sp 143 9 14 The Test Run History Report Lao conidios 144 915 TE TOSTRUP Screen ai aiii 145 9 16 The Test Run Details Screen ae 145 9 17 The Test Run Into EOIN idas AR ene 145 9 le The Single Test RUN Report iss Se SEERDE end 146 9 19 The Single Test Run Report continued ses eee 147 9 20 The Test Case Results Screen ati E E E 147 9 21 The Test Suite from Test Case Results POP UP see eee eee 148 9 22 The Single Test Case Results Screen sese ecce eee eee 148 9 23 The Test Case Results Details Screen issie ss ee Ek AG ee AG ee Ne AE ee ee 149 9 24 Editing Test Case S
249. if you choose the wrong Java architecture A typical error output for running a 32 Bit Tomcat installation in conjunction with a 64 Bit Java looks like the following Commons Daemon procrun 1 0 15 0 32 bit started Debugging tomcat7 service Starting service 1 is not a valid Win32 application Failed creating java C Program Files Java jrel1 8 0_45 bin server jvm dll 1 is not a valid Win32 application ServiceStart returned 1 1 is not a valid Win32 application Debug service finished with exit code 1 Commons Daemon procrun failed with exit value 3 Failed to run service as console application 1 is not a valid Win32 application You may update the Java virtual machine which the service uses in the Java tab of the tomcat8w administration interface 40 Installation Adjust the memory settings when updating older installations Klaros Testmanagement needs a larger amount of memory than the default Ja va installation suggests If you are using a version of Klaros Testmanagement prior to release 3 8 0 it is necessary to supply the following settings to the Tom cat configuration which can be set in the tomcat8w administration interface by adding the line XX MaxPermSize 128mto the Java Options text area in the Java tab as shown below In addition a reasonable amount of maximum memory should be defined here as well Later versions to not require this as the installer with allow to change these settings No Apache Tomca
250. ify notifyAll toString wait I Per SS KlarosWrapper lt T S gt I I I BE N S Sexten KlarosLabeledObject lt T S I Fen S Sextends NamedEntity KlarosNamedEntity lt W P gt I SS er rrr pd 1 W W extends KlarosCategoryTree lt l W P X Y gt P Pextends CategoryTree 1 X X extends KlarosCategoryNode lt l W X Y gt 1 Y Y extends CategoryNode L KlarosCategoryTree lt KlarosRequirement KlarosRequirementCategoryTree RequirementCategoryTree KlarosRequirementCategoryNode RequirementCategoryNode gt y KlarosRequirementCategoryTree B 1 1 51 KlarosRequirementGroup This class realizes the grouping of test requirements B 1 1 51 1 Synopsis public final class KlarosRequirementGroup extends KlarosNamedEntity lt KlarosRequirementGroup RequirementGroup gt implements IKlarosRequirementGroup Public Methods public Set lt KlarosRequirement gt getAllReguirementsO public Set lt KlarosRequirementGroup gt getChildrenO public double getCoverage public Integer getDepth public List lt KlarosRequirementGroup gt getDescendantsO public List lt KlarosRequirementGroup gt getFamilyO public int getNumberCoveredRequirements public int getNumberRequirements public KlarosRequirementGroup getParent public Set lt KlarosRequirement gt getRequirements Methods inherited from de verit klaros core model KlarosNamedEntity getAssign
251. ify notifyAll toString wait ParameterContext ParameterContext parameters List lt ScriptParameter gt getParameters Map lt String Parameter gt B 2 4 2 2 ParameterContext List lt ScriptParameter gt public ParameterContext List lt ScriptParameter gt parameters Create a ParameterContext Parameters parameters the jcr script parameters B 2 4 3 ParameterType The possible script parameter types B 2 4 3 1 Synopsis public final class ParameterType extends Enum lt ParameterType gt implements IKlarosEnum Public Static Fields public static final ParameterType BOOLEAN public static final ParameterType DATE public static final ParameterType INTEGER public static final ParameterType LIST public static final ParameterType MULTI_LIST public static final ParameterType STRING Public Static Methods public static ParameterType fromName String name 340 Model API Reference public static ParameterType parse String name public static ParameterType valueOf int value public static ParameterType valueOf String name public static ParameterTypeL values Public Methods public int getCode public String getResourceKey public boolean isListTypeO public String toLocaleString Locale locale Methods inherited from java lang Enum compareTo equals getDeclaringClass hashCode name ordinal toString valueOf Methods inherited from java lang Ob
252. ile the report template describes the layout of the report The Groovy Java script taking care of data retrieval and preparation is provided by a class that implements the Section E 2 KlarosScript Interface This interface defines a single method called execute and takes a de verit klaros scripting KlarosContext object as input parameter To retrieve the data from Klaros Testmanagement the report designer can access the de verit klaros core model via the HQL query language The main task of the class is to pro vide and prepare the data for the report The data for the report template must then be stored in the de verit klaros scripting KlarosContext object passed to the execute method To make reports more flexible for report users it is possible to pass parameters to the Groovy Java script The parameters are stored in the context and can be accessed from the script Predefined objects in the context The de verit klaros scripting KlarosContext object already contains predefined objects For a list please refer to Section E 1 Context Variables The report template must be implemented using SeamPDF Section Section 11 3 Example Report provides an example of how to define a custom report 11 1 Create A New Report Template Before reports can be applied to the test data they have to be defined To get to the Report Templates page click on the Configure icon and select Report Templates from the menu on the left
253. imes disabled Projects that already contain some test results can no longer be deleted by users so their delete icon is disabled Only an administrator can delete a locked project Locked projects may be restored as long as they have not yet been purged from the database 6 1 3 Restoring a Project When the restore icon is clicked a previously locked project is restored to the list of selectable projects Only an administrator is able to restore a locked project 6 1 4 Purging a Project When the purge icon is clicked a previously locked project is purged from the database Only an administrator is able to purge a locked project This operation cannot be undone 6 1 5 Editing the Description of a Project The project description can be used to give a short overview over the project Clicking on the Description field allows the user to directly change the current value Figure 6 1 6 1 6 Project Details This section allows in depth editing of an individual project including adding removing is sue management systems and user defined properties The executed test results and the change history of this project are also visible in this section 6 1 6 1 Editing the Issue Management Systems in a Project The list of issue management systems that are in use in the project can be edited on the project details page which may be reached by pressing the 1 edit icon beside a project on the projects page Figure 6 1
254. in the currently active project Clicking the amp icon opens the Link Issues page for the corresponding test case E Define E Plan po Execute pmi Evaluate y Configure Assign Issues TC00017 Dashboard Report Templates Filter Sort ll 70 v Test Run History ID System System under Test Summary Created Created By Assigned To Priority State Action SORR PLAYGROUND 18870 B M00001 0 1 SNAPSHOT Importante 12 2 2014 admin hudson Blocker Open QE PLAYGROUND 4173 Ed Mo0o01 0 2 de 8 23 2010 admin admin Blocker Open QE Test Case Results Test Suite Results ees System I1M00001 JIRA Server Y QD ID Q Back Figure 9 34 The Test Case Selection Screen To link a new issue to the test case an issue management system must be selected Pressing the Link button causes the issue with the entered ID to be attached to the test case E Define Plan 1 Execute i Evaluate KN Configure Eww S N Q issue PLAYGROUND 20859 has been found in the issue management system IM00001 Jira JIRA Server x Dashboard S l Link Issues TC00002 Project setup check E Report Templates Test Run History Fiter Sort E 70 v Test Runs ID System System under Test Summary Created Created By Assigned To Priority State Action Test Case Results No entries available Test Suite Results es System 1M00001 JIRA Server vr Q ID PLAYGROUND 20859 Issue PLAYGROUND 20859 ID PLAYGROUND 20859 D Summary Test Created 5 26 15 5 20 PM
255. inal KlarosContextParameter parameters public static final KlarosContextParameter user Public Static Methods public static KlarosContextParameter value0f String name public static KlarosContextParameter values 329 Model API Reference Methods inherited from java lang Enum compareTo equals getDeclaringClass hashCode name ordinal toString valueOf Methods inherited from java lang Object getClass notify notifyAll wait Enum lt KlarosContextParameter KlarosContextParameter values KlarosContextParam et er valueOf name String KlarosContextParameter B 2 2 2 2 applicationBaseUri public static final KlarosContextParameter applicationBaseUrl The application base url B 2 2 2 3 date public static final KlarosContextParameter date The current date B 2 2 2 4 imageProvider public static final KlarosContextParameter imageProvider The image provider B 2 2 2 5 parameters public static final KlarosContextParameter parameters The parameters B 2 2 2 6 user public static final KlarosContextParameter user The current user B 2 3 de verit klaros scripting custom B 2 3 1 IterationsReport The Class IterationsReport A Java snippet to create an Iteration Report Template B 2 3 1 1 Synopsis public class IterationsReport implements KlarosScript 330 Model API Reference Public Constructors public IterationsReport Public Methods
256. include Microsoft Windows Mac OS Linux BSD and Solaris See Operating System Environmental and state conditions that must be fulfilled after the execution of a test or test procedure Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure A project is the main unit that contains all other Artifacts that are needed to execute Test Cases QF Test is a professional tool for automated testing of Java and Web applications with a graphical user interface from Quality First Software 211 R Redmine Requirement Role S Selenium SUT System Account System under Test T Test Case Test Case Result Test Case Step Test Environment Glossary Redmine is an open source bug tracking issue tracking and project management system A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract standard specification or other formally imposed document After IEEE 610 A role defines the rights the rights a user has regarding the appli cation or selected projects In Klaros Testmanagement a user can take the role of an Adminis trator Manager Tester OF Guest Selenium is a web browser automation tool primarily used for au tomated testing of web apps Selenium is able to produce JUnit compatible test re
257. ine esse sesse ss se se se ee de AG ee ee Ge de 199 12 4 XML Test Case Import via Command Line with authentication sese eee sees ses see 200 12 5 Excel Requirement Import via Command Line sss sese eee eee eee eee eee ee 202 12 6 Excel Requirement Import via Command Line with authentication sees eee eee 202 12 7 XML Requirement Import via Command Line esse sees sees see see eee eee 203 12 8 XML Requirement Import via Command Line with authentication sees eee eee ee 203 12 9 XML Requirement Synchronization via Command Line sesse esse see see ee ee ee 204 12 10 XML Requirement Import via Command Line with authentication 205 121 OF Test Import URE SEAN DNG ss AE se Ee tai 207 12 12 aa EOmimaid line example aars 207 xvi Chapter 1 Key Features 1 1 Klaros Testmanagement Community Edition Features community edition Key features of Klaros Testmanagement Community Edition Management of Test related Artifacts Revisioning Saving Binary Attachments Reports and Statistics Report File Export Guided Manual Test Execution Continuation of Interrupted Work Security Interoperability with continu ous integration servers Jenk ins Hudson Integration with Issue Man agement Systems Klaros Testmanagement allows management of projects iteration requirements test cases test suites test envi ronments systems under test test runs and test results Kla
258. ings Windows I Enterprise System protection Copyright 2009 Microsoft Corporation All rights re Advanced system settings System Rating 33 Windows Experienc Processor Intel R Core TM 17 CPU Installed memory RAM 16 0 GB System type 64 bit Operating System Pen and Touch Mo Pen or Touch Input is OEM Info Website Online support Computer name domain and workgroup settings See also Action Center Computer name Windows Update Full computer name Performance Information and Computer description Tools Domain e Click on the panel Advanced then the button Environment Variables 15 Installation Computer Name Sustem Protection Tou must be logged on as an Administrator to make most of these changes Performance Visual effects processor scheduling memory usage and virtual memory Settings User Profiles Desktop settings related to your logon Settings Startup and Recovery System startup system failure and debugging information Settings Environment variables Then this Window should pop up P Environment Variables User variables for Jim Variable value path v CommonProgramFiles b Microsoft 5h TEMP USER DR OEILE AppDatallocallTemp TMD SLLUSERPROFILESS1AppDatalLocal Temp System variables variable value L CLASSPATH Program Files x86 Javaljre llible Ls Com pec Co Windowslsystem32Icmdexe DEFLOGDIR CAProgramDatalMcafee DesktopProtec
259. into the project named P00001 using the curl command line application curl is available in almost any Linux distribution and for the Microsoft Windows operating system family as part of the Cygwin http www cygwin com distribution or as a command line tool from http curl haxx se download html curl v T Requirements xml lt klaros app url gt seam resource rest import requirement xml config P00001 Example 12 7 XML Requirement Import via Command Line If the Klaros Testmanagement installation requires authentication for import username and password arguments have to be appended to the curl call curl v T Requirements xml lt klaros app url gt seam resource rest import requirement xml config P00001 amp username user amp password secret Example 12 8 XML Requirement Import via Command Line with authentication Note ZA All artifacts which are referenced during import like projects or test cases con tain five digits in their ID For example P00001 is a valid project ID while POT and POO1 are not 12 4 3 Synchronizing To synchronize XML based requirements a different REST interface is available ending with sync requirement xml It understands the same import format as defined for importing requirements but requires additional elements to be present for correct operation In contrast to an import a synchronization action is intended to update the set of require ments stored in Klaros Testmanagement from arbitrary
260. ion 1 0 Name iteration PDF Overview Report TR Description Lists a defined Iteration in a Project Template Type PDF vw Edit the Script Mobile Devices System New Parameter Integration ae package de verit klaros scripting custom A Backup import java text SimpleDateFormat import java util ArrayList import java util Date import java util Iterator import java util List Groovy Script import java util Map import java util Set import java util TreeMap import de verit klaros core model IKlarosIteration import de verit klaros core model KlarosSUTImplementation import de verit klaros core model KlarosTestCaseResult import de verit klaros core model KlarosTestEnvironment v import de verit klaros core model KlarosTestRun Upload Script Template Edit the Template Preview Save Discard Figure 11 3 The New Report Templates Page To enter the Groovy script which retrieves the data use the Groovy Script text area TO un fold the template text area click on the Edit the Template link next to the Template label The report s template code can then be entered into the unfolding text area To unfold the Groovy script text area again click on the Edit the script link gt Note For larger report templates it might be helpful to use a Java IDE e g Eclipse to develop the Groovy script and an XML editor to provide the report template The created files can then be uploaded into Klaros Testmanagement To avoid error
261. is disabled if there are any unsaved changes to the test suite 100 Define Plan kS Execute pi Evaluate y Configure S WebApp amp 1 0 Ts00001 Sprint Null N ET Projects Iterations Properties User Defined Attachments Revisions Results Changes Requirements Test Environments Name Sprint Null System under Test 0 2 SNAPSHOT v Systems under Test on Test Cases ID Revision Name Traceability Execution Action Test Suites TC00001 1 0 IDE check Manual Ay TC00002 1 0 Projekt setup check Manual ASV TC00003 1 0 Continuous Integration check Manual ASVe amp Filter Sort El 10 y 1D Revision Name Traceability Execution Action O TC00003 1 0 Continuous Integration check Manual op O TC00002 1 0 Projekt setup check Manual dh O TC00001 1 0 IDE check Manual db Back Figure 6 28 The Test Suite Details Screen Warning sign in the ID column A manual test case which contains no steps is not executable To indicate this a warning sign 115 displayed in the ID column 6 7 3 1 Test Suite Overview E Plan gt Execute Pl Evaluate X Configure weap E p J 1 0 T500001 Sprint Null Eek Back Projects iterations Overview Properties User Defined Attachments Revisions Jobs 1 Results 10 Changes Requirements System under Test 0 2 SNAPSHOT 6 TestE ts A Latest Executor John Doe Systems under Test Test Cases Latest Test Runs Execution Time Test Suites 4
262. ite KlarosTestSuite getRelatedSummary String hashCode int compareTo o KlarosTestRun int equals o Object boolean getlteration Klaroslteration isPending boolean get Work Set lt KlarosbbTimeBlock gt B 1 1 69 KlarosTestSuite This class provides access to the information stored for test suites B 1 1 69 1 Synopsis public final class KlarosTestSuite extends KlarosRevision lt KlarosTestSuite TestSuite gt implements IKlarosTestSuite lt KlarosTestSuite TestSuite gt Public Methods public Set lt KlarosAttachment gt getAttachmentsO public KlarosTestSuite getBranchRoot public Set lt KlarosRevision lt KlarosTestSuite TestSuite gt gt getBranches public Set lt KlarosTestSuiteCategoryNode gt getCategories public KlarosConfiguration getConfiguration public KlarosTestSuite getPredecessor public List lt KlarosTestSuiteResult gt getResults public KlarosTestSuite getRootO public String getShortnameO public KlarosTestSuite getSuccessor 316 Model API Reference public KlarosSUTImplementation getSutO public List lt KlarosTestCase gt getTestCases public Integer getTestSuiteResultCount public KlarosTestSuite getTrunkRoot Methods inherited from de verit klaros core model KlarosRevision getRevisionComment getRevisionld Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Me
263. ited are shown in Figure 10 26 lt Note Please consult your system administrator about the values to enter here 178 Configure SMTP Server The host name of your mail server SMTP Server Port The port where your mail server is listening This value usu ally depends on the security setting chosen below The de fault value is 25 for no security Sender Address The From address field of the mails generated by the ap plication User Name A user name needed to authenticate against the SMTP server This field is only present if SMTP or POP authenti cation is selected in the Authentication field below Password A password needed to authenticate against the SMTP serv er This field is only present if SMTP or POP authentication is selected in the Authentication field below Authentication Some mail servers require users to authenticate them selves before they allow them to send mails to prevent or identify spammers This option chooses whether no au thentication is required or a username password combi nation via SMTP or POP is used If one of the latter two is selected the User Name and Password fields are shown in the user interface Security This setting defines the transport layer security used to access the SMTP mail server Each transport security set ting may require a different port value above The options are None Port 25 Secure Socket Layer SSL Port 465 or Transport Layer Security TLS aka STARTTLS
264. iteration number B System under Test y Enumeration v Z webbrowser Firefox Iy B New Created by John Doe on 11 18 13 5 24 PM Last changed by John Doe on 11 19 13 3 43 PM Save Discard Back Figure 5 20 The User Defined Tab Pressing the New button adds a new user defined property to the list After adding a new property the entity and property type must be chosen There are seven possible entity types s Iteration Job e Requirement System under Test e Test Environment Test Case s Test Suite Test Run The four possible property types are Text The property will be a single line text field Text Field The property will be a multi line text field True False The property will be a simple check box Enumeration The property will be a drop down box to select a single entry from a prede fined list of values The default value of the property can also be set here After the new property is saved the entity type and property type can no longer be changed The name of the property and the list of enumeration values can always be changed 5 2 11 1 Enumeration Values The Edit button beside the enumeration property names opens the menu to edit the values of the enumeration property as shown in Figure 5 21 62 Functional Overview E Plan 4 Execute fi Evaluate Configure Issue Management Systemine N P00003 Issue Management System Integration a rec a HEER GE Iterations ES q Prope
265. ition The environmental and state conditions that must be fulfilled after the execution of the test Case e g The user is authenticated and has access to the system Plan po Execute pi Evaluate y Configure Testing the email cien L p 1 0 TC00001 Test the file size limitation when attaching large files to emails E Projects Iterations f Properties User Defined Steps 4 Attachments Revisions Results Changes Requirements Test Environments New Toggle View Mode xx 57 Page Size 3 v Systems under Test Step 1 Login to your intranet email account with the email client Description Login to your intranet email account with the email client Test Suites Expected Result You can see the list of your emails in the email client Precondition You are in one ofthe terminal rooms at one of the UNIX terminals Postcondition You are logged into your email account Step 2 Click on the button Compose a new email Step 3 Click the button Add an attachment New Created by John Doe on 10 29 13 10 22 AM Last changed by John Doe on 8 18 14 2 41 PM Back Figure 6 24 The Edit Test Steps Screen To change the order of the test steps the icon is used This opens a dialog which allows the test step to be inserted in another position in the list To add a new test step to the end of the list click the icon Test steps are inserted before or after a given step using the and icons The cl
266. ject getClass notify notifyAll wait E Eextends Enum lt E gt Se Sr Enum lt ParameterType gt hem mm m m EE EE EE EE EE EE EE EE EE w EE EE w EE w w ma ParameterType values ParameterTypel valueOf name String ParameterType getCode int valueOf value int ParameterType parse name String ParameterType getResourceKey String toLocaleString locale Locale String isList Type boolean B 2 4 3 2 fromName String public static ParameterType fromName String name Create enum from a name string Parameters name the name return An enum by its name B 2 4 3 3 getResourceKey public String getResourceKey Gets the resource key 341 fromName name String ParameterType Model API Reference Parameters return the resource key B 2 4 3 4 isListType public boolean isListTypeO Checks if this type is a list type Parameters return true if list type B 2 4 3 5 parse String public static ParameterType parse String name Parse an instance from a name string Parameters name the name of the enumeration as returned from toString or name methods return The enumeration or null if no match B 2 4 3 6 valueOf int public static ParameterType value0f int value Create from a code value Parameters value the code value return Returns the value of the given code B 2 5 Constant field values B 2 5 1 de verit klaros sc
267. k Ge Ge Ne AG ee Ge 41 5 16 Reanine PludinSeEtIOM iaa E ETE E 43 3 17 Redmine Authentication SEAN HHR 44 18 TE PU STONES 45 5 19 TE6 Perinissions SEAN T 45 Salis LON STEEN ara pi 49 SA Ma tala POE PE 4 se AE N ED ee Ee ee 50 3 TE Help MEN save 51 5 4 he Help Menu BUTON espen 52 5 5 TE Rel MEN vvs 52 TENNENE 52 STRAE Search Results PIL ee 53 59 The status Bar SEAN REDON serer EE GE GE 53 ST The PP 54 5 10 TN amp LOG Panel es 54 SITTE FE ana Sort Panel ee 54 512 The Test Suite Print PAG re 57 HS TE Categorizaci n Edit VIEW see 58 5 14 The Categorization Tree View 0 58 515 Me Categorization Menu VIEW varslene 59 516 THE Contlict Resolution DialOd ars Re GR RR AR RE De Ge Se 59 3 17 10e Delete OP EG PONG 60 5 18 The Bulk Actions on the Test Case List Page esse ese ee ee de ee de ee de ee 61 SE BRENN DENN 61 520 The User DE MEN TED pe 62 5 2 l Editing an Entimelation Property vasse 63 5 22 The Test Suite User Defined Tab see 63 Xi Klaros Testmanagement User Manual 5 23 116 ASSIGN Attachments STEEN Lan 64 6 24 The Test Suite REVISIONS Tab sa 64 SS ME RUE Tai dia 65 5 26 The Test Case Changes Tab rranenerrnnnnnvnnrrnnnnennnnrnnennnnnnnnnennernnnnnnnnennnnnnnnnnnnnenneennese 66 521 The Test Case Overview Tab EDE ED Ra 67 671 TRES POE SEN 68 62 116 Project Properties Page Lae 70 6 3 Copying Objects to the Current Project sees eee eee ee eee 71 6 4 Copying Objects from another Project sese eee eee eee
268. laros core model KlarosTestCase de verit klaros core model KlarosTestSuite Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait ER T S Sextends LabeledObject KlarosLabeledObject lt T S getRevisionld String getRevisionComment String B 1 1 53 KlarosSUTImplementation 299 Model API Reference This class provides access to the information stored for systems under tests SUT B 1 1 53 1 Synopsis public final class KlarosSUTImplementation extends KlarosNamedEntity lt KlarosSUTImplementation SUTImplementation gt implements IKlarosSUTImplementation Comparable lt KlarosSUTImplementation gt Public Methods public int compareTo KlarosSUTImplementation o public boolean equals Object o public Set lt KlarosAttachment gt getAttachments public Set lt KlarosSUTImplementationCategoryNode gt getCategories public KlarosConfiguration getConfiguration public Set lt KlarosIssue gt getIssues public Set lt KlarosIteration gt getIterations public String getProductversio
269. larosRequirement gt getAllReguirementsO Get all requirements of this group hierarchy Parameters return List containing own requirements and all requirements of groups which are descendants of this group 243 Model API Reference B 1 1 17 3 getChildren public abstract Set lt KlarosRequirementGroup gt getChildrenO Get the children of this requirement group Parameters return Set containing the requirement groups that are children of this requirement group B 1 1 17 4 getCoverage public abstract double getCoverageQ Get test requirement coverage for the group Parameters return the coverage in percent If no requirements are found 1 0 is returned B 1 1 17 5 getDepth public abstract Integer getDepthO Get depth in tree of this node Parameters return The depth in the tree B 1 1 17 6 getDescendants public abstract List lt KlarosRequirementGroup gt getDescendants Get all descending subgroups of this group Parameters return List containing all groups which are descendants of this group B 1 1 17 7 getFamily public abstract List lt KlarosRequirementGroup gt getFamilyO Get whole family with this group as root Parameters return List containing this group and all of its descendants B 1 1 17 8 getNumberCoveredReduirements public abstract int getNumberCoveredReguirementsO Get number of test requirements covered by at least one test case 244 Model API Reference
270. lass hashCode notify notifyAll toString wait TT l S Sextends LabeledObject KlarosLabeledObject lt ee eee ee ee ee ee ee SEE EE TT S Sextends NamedEntity KlarosNamedEntity lt KlarosTestCaseResult TestCaseResult gt KlarosTestCaseResult getTestRun KlarosTestRun getTestCase KlarosTestCase getTestSuiteResult KlarosTestSuiteResult getStepResults List lt KlarosTestCaseStep Result gt isPassed boolean isError boolean isFailure boolean isSkipped boolean compareTo o KlarosTestCaseResult int equals o Object boolean hashCode int getSummary String getDescription String getExecutionTime long isPending boolean getTestSuitePosition Integer getAttachments Set lt KlarosAttachment gt B 1 1 61 KlarosTestCaseState This class provides access to the information stored for test case states B 1 1 61 1 Synopsis public final class KlarosTestCaseState extends KlarosWrapper lt KlarosTestCaseState TestCaseState gt implements IKlarosTestCaseState Public Methods 308 Model API Reference public String getStateDescriptionQ public String getStateNameO public KlarosSUTImplementation getSutO public KlarosTestCase getTestCase Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll
271. ld gt The external id of this requirement the format of this string can be chosen deliberately lt externalRevision gt The external revision of this requirement the format of this string can be chosen deliberately Table D 1 Element summary 351 Requirement Import File Specification D 1 lt attribute gt A custom attribute This element may occur inside the following elements lt attributes gt Table D 2 lt attribute gt elements D 2 lt attributes gt The list of custom attributes Table D 3 lt attributes gt elements D 3 lt container gt The container element for requirements This is the root element of this schema ear at Table D 4 lt container gt elements D 4 lt requirements gt The list of custom attributes This element may occur inside the following elements lt container gt ET un Table D 5 lt requirements gt elements D 5 lt requirement gt A requirement definition This element may occur inside the following elements lt requirements gt eee e 352 Requirement Import File Specification name anas Description Table D 6 lt requirement gt elements D 6 lt triggers gt The list of triggers for this object This element may occur inside the following elements lt requirement gt Table D 7 lt triggers gt elements D 7 lt externalIld gt The ex
272. lease make sure that this test envi ronment already exists in the project before starting the import SUL The ID of the system under test in which the tests have been run e g SUT00001 Please make sure that this sys 205 type time createTestSuiteResults Import Export tem under test already exists in the project before starting the import The type of the import format The following types are sup ported aunit boost Check cpptest cppunit ctest cunit fpunit jubula junit mbunit mstest nunit phpunit aftest qtestlib ranorex testcomplete tusar cpptestunit valgrind xUnit net AUnit Boost Test Check CppTest CppUnit ctest CUnit Free Pascal Unit Jubula GUIdancer JUnit Selenium TestNG MBUnit MSTest NUnit PHPUnit QF Test QTestLib Ranorex TestComplete TUSAR UnitTest Valgrind xUnit net The time of the import Please make sure the fixed format for the time is dd MM yyyy HH mm If set to true test suite results are automatically created for the corresponding test suite information contained in 206 Import Export the result file This information may vary with the import format Additionally a corresponding test suite is created for the test suite result if it did not yet exist username since plugin ver The user name for the import If Klaros Testmanagement sion 1 1 is configured to use authentication for the import a valid user name must be passed to the
273. lect Installation Packages Select Installation Packages Section 3 3 5 Step 5 Select Installation Packages is more complex in console mode The required packages Tomcat 8 and Klaros Testmanagement are displayed for information only and the request targets the optional PDF Documentation Typing Y chooses to install the PDF Documentation where N omits it After this choice you are requested to commit the selection by typing 1 and then Enter Tomcat 7 Application Server required Klaros Testmanagement required PDF Documentation Enter Y for Yes N for No N Done Press 1 to continue 2 to quit 3 to redisplay 1 3 4 6 Step 6 User Data After that the installer requests user data Section 3 3 6 Step 6 User Data The installer presents default values which can be comitted by pressing Enter You can enter a different value in case the default is not suitable Checkboxes show x if the checkbox is set oth erwise Pressing Enteraccepts the current value which can be set and unset explicitly with 1and Orespectively In this example we adopt most of the default values Only the memory settings and the tomcat admin password withno default are entered and the two flags are unset Tomcat Server Settings Server Port 18005 HTTP Port 18080 AJP 1 3 Port 18009 Session Timeout 60 The minimum and maximum amount of memory available to the Tomcat process Minimum MB 256 400 Maximum MB 512 1024 30
274. lection of requirements and linking them to test cas es enables Klaros Testmanagement to track the test cov erage of the requirements Jobs to execute test cases and test suites can be generated assigned to users and tracked easily at all times With the help of tables and diagrams the workload dura tion and progress of test activity for each user can be clear ly displayed Jobs can be arranged hierarchically The success rate and progress of all jobs can be seen at any time Klaros Testmanagement Enterprise Edition allows multi ple categorization of requirements iterations systems un der test test environments test cases and test suites Every change to test data is recorded and displayed in the change history to enable better tracking of changes Klaros Testmanagement Enterprise Edition allows the de finition and usage of custom fields for requirements iter User Definable Reports Configurable Dashboard LDAP Support for User Au thentication Excel Export of Data Tables Print View Bulk Actions Key Features ations test cases test suites test environments and sys tems under test Klaros Testmanagement Enterprise Edition also supports definition and creation of individually designed reports in PDF or Excel format For this a simple but powerful pro gramming interface is integrated In Klaros Testmanagement Enterprise Edition users can organize their dashboard according to their individual re
275. lish and German interfaces be made in a file with the variation in the filename set e g messages en US companyName properties in order to persist changes As well as copying over the default files Klaros Testmanagement also merges any changes with user defined files If key value pairs are added to the default files during an update these will also be added to the end of any user defined language files along with a comment stating when the entries were added These entries should be translated by the creator of the custom language file 47 Customization 4 2 Custom Ouotes Klaros Testmanagement allows the use of a custom quotes file This allows the customiza tion of the Quote of the Day field shown on the login screen A custom quotes file can be uploaded to Klaros Testmanagement using the form on the General Settings page can be placed directly in the klaros resources folder in the home directory of the user running Klaros Testmanagement A custom quotes of the day file is simply a text document with the extension txt which uses ISO 8859 1 encoding with Unicode escapes and contains one quote per line The quote displayed changes each calendar day The process of uploading a custom quotes file is de scribed in Section 10 5 System 48 Chapter 5 Functional Overview This Chapter gives a coarse overview of the usage of the application Warning The browser back button is not supported by Klaros Testmanagement The be
276. ll horizontalAlignment center verticalAlignment top gt lt p paragraph gt lt p text value Name gt lt p paragraph gt lt p cell gt lt p cell horizontalAlignment center verticalAlignment top gt lt p paragraph gt lt p text value Result gt lt p paragraph gt 356 Reporting Resources lt p cell gt lt p cell horizontalAlignment center verticalAlignment top gt lt p paragraph gt lt p text value Testrun description gt lt p paragraph gt lt p cell gt lt p cell horizontalAlignment center verticalAlignment top gt lt p paragraph gt lt p text value Summary gt lt p paragraph gt lt p cell gt lt p font lt display the attributes of the test results gt lt p font size 8 gt lt ui repeat value results var tcr gt lt p cell verticalAlignment top horizontalAlignment left gt lt p paragraph gt lt p text value tcr testCase name gt lt p paragraph gt lt p cell gt lt decide which color has to be displayed based on the testresult gt sui fragment rendered tcr error gt lt p cell backgroundColor rgb 255 0 0 verticalAlignment top horizontalAlignment center gt lt p paragraph gt lt p text value error gt lt p paragraph gt lt p cell gt lt ui fragment gt sui fragment rendered tcr failure gt lt p cell backgroundColor rgb 255 215 0 verticalAlignment top horizontalAlignment center
277. lt gt artifact Gets the browse page url to the given klaros artifact Will return null if the artifact type is not supported Parameters artifact the artifact return the browse page url B 2 2 1 10 getParameter String public abstract Parameter getParameter String name 328 Model API Reference Gets the parameter Parameters name the name return The parameter with the given name or null B 2 2 1 11 getParameterValue String public abstract Object getParameterValue String name Gets the parameter value Parameters name the name return The value of the parameter with the given name or null B 2 2 1 12 getPrintPageUrl KlarosLabeledObject lt gt public abstract String getPrintPageUrl KlarosLabeledObject lt gt artifact Gets the print page of the given klaros artifact Will return null if the artifact type is not supported Parameters artifact the artifact return the print page url B 2 2 1 13 setLocale Locale public abstract void setLocale Locale locale Parameters locale The locale to set B 2 2 2 KlarosContextParameter The available context parameters B 2 2 2 1 Synopsis public final class KlarosContextParameter extends Enum lt KlarosContextParameter gt Public Static Fields public static final KlarosContextParameter applicationBaseUrl public static final KlarosContextParameter date public static final KlarosContextParameter imageProvider public static f
278. lt gt implements IKlarosTestSuiteResult Comparable lt KlarosTestSuiteResult gt Public Methods public int compareTo KlarosTestSuiteResult o public boolean equals Object o public Set lt KlarosTestCaseResult gt getResultsO public KlarosTestRun getTestRun public KlarosTestSuite getTestSuite public int hashCodeO public boolean isPendingO Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 320 Model API Reference KlarosTestSuiteResult getTestSuite KlarosTestSuite getTestRun KlarosTestRun compareTo o KlarosTestSuiteResult int equals o Object boolean hashCode int isPending boolean getResults Set lt KlarosTestCaseResult gt B 1 1 73 KlarosUser The user object B 1 1 73 1 Synopsis public class KlarosUser extends KlarosLabeledObject lt KlarosUser User implements IKlarosUser Comparable lt KlarosUser gt Public Methods public int compareTo KlarosUser o public boolean equals Object o public String getEmailO public
279. ly have been failed during a test run in this test environment alongside with the appertaining test case result Note Ea This table is limited to five entries The other system under tests can be viewed by pressing the Show All button 6 4 3 2 User Defined Properties Ca enterprise Feature only available in Klaros Testmanagement Enterprise Edition edition y User defined properties can be used to customize test environments within Klaros Testman agement by adding custom fields This process is described in Section 5 2 11 User Defined Properties 86 Define 6 4 3 3 Attachments Attachments may be added to test environments This process is described in Section 5 2 12 Attachments 6 4 3 4 Results The result tab is further divided into a Test Runs Test Case Results and a Test Suite Results tab showing the test results related to this test environment as described in Section 5 2 14 Related Test Runs and Results 6 4 3 5 Bookmarking Test Environments enterprise Feature only available in Klaros Testmanagement Enterprise Edition J edition Test environments may be linked to from outside of Klaros Testmanagement using the link on the bookmark icon Right click the con and choose Copy Link Location Fire fox Chrome or the equivalent option 6 5 Systems under Test The systems under test section allows maintenance of the systems under test in the selected project A system un
280. management Enterprise Edition Some Details sections show test runs and test results which are related to the artifact being displayed e g executed in the displayed test environment or executed by the displayed user An example of a Test Results tab is shown in Figure 5 25 64 Functional Overview Plan dj Execute pi Evaluate X Configure B o WebApp Mor e L fm SUT00006 0 2 SNAPSHOT EES Projects Iterations Properties User Defined Attachments Results Changes Requirements Test Environments Test Case Results Test Suite Results Test Runs Fiter Sort El 10 v ina 1D e Start Test Run Test Case Test Environment Executor Duration Result Action Test Suites TCR0000047 11 21 13 1 13 52 PM TRUO0000041 TC00003 tomcat ad hoc John Doe 1ms A Q TCRO000046 11 20 13 8 31 36 PM TRU0000040 TC00003 tomcat ad hoc John Doe ims Q TCR0000045 11 20 13 8 31 27 PM TRU0000039 TC00003 tomcat ad hoc John Doe ims TCR0000044 11 20 13 8 31 16 PM TRU0000038 TC00003 tomcat ad hoc John Doe ims Q TCR0000043 11 20 13 8 31 08 PM TRUO0000037 TC00003 tomcat ad hoc John Doe 1ms A TCR0000042 11 20 13 8 30 59 PM TRU0000036 TC00003 tomcat ad hoc John Doe ims Q TCR0000041 11 20 13 8 30 52 PM TRU0000035 TC00003 tomcat ad hoc John Doe 1ms TCR0000040 11 20 13 8 30 44 PM TRU0000034 TC00003 tomcat ad hoc John Doe ims TCR0000039 11 20 13 8 30 36 PM TRU0000033 TC00001 tomcat ad hoc John Doe ims TCR0000038 11 20 13 8 30 27 PM TRU0000032 TC
281. mann Test Environments 5 Date Jul 16 2010 5 30 PM Id ENYODOO Name Win 7 Test Run Execution Date Executed by Passed Failure Error POO002 TRUOOOO037 POO002 TRUOOOO0S6 P00002 TRUO000067 P00002 TRUO000069 P00002 TRUO000072 Oct 8 2009 5 17 PM Oct 9 2009 8 54 AM Oct 9 2009 11 06 AM Oct 9 2009 11 58 AM Oct 9 2009 1 08 PM Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann POOOO2 TRUOOOOO71 P00002 TRUO000086 P00002 TRUN0000087 Oct 10 2009 12 22 AM Oct 11 2009 10 44 PM Oct 11 2009 10 45 PM Felix Mustermann Felix Mustermann Felix Mustermann POOOO2 TRUODOO10S POOOO2 TRUODOO133 POOOO2 TRUOOOO136 POOOO2 TRUOOOO138 POOOO2 TRUOOOO177 POOOO2 TRUODOO178 POODO2 TRUODDO180 Oct 12 2009 7 12 PM Oct 15 2009 6 54 PM Oct 18 2009 5 11 PM Oct 18 2009 5 15 PM Oct 28 2009 7 51 PM Oct 29 2009 11 48 AM Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Oct 29 2009 11 49 AM Nov 2 2009 2 19 PM Nov 4 2009 8 43 AM Nov 4 2009 8 58 AM Nov 4 2009 10 53 AM Nov 13 2009 11 06 AM Dec 8 2009 12 27 PM Dec 8 2009 5 14 PM P00002 TRU0000189 P00002 TRU00001 97 P00002 TRU0000202 P00002 TRU0000205 P00002 TRU0000223 P00002 TRU0000273 P00002 TRU0000274 Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann Felix Mustermann oa M OOO G AA ONO ada
282. ments lt requirement gt D 12 lt revision gt The revision of this requirement This field is used only for exporting requirements imported requirements always have the revision ID 1 0 This element may occur inside the following elements lt requirement gt D 13 lt shortname gt The short name code of this object This element may occur inside the following elements lt requirement gt D 14 lt summary gt The summary of this requirement This element may occur inside the following elements lt requirement gt D 15 lt name gt The name of the custom attribute This element may occur inside the following elements lt attribute gt D 16 lt value gt The value of the custom attribute This element may occur inside the following elements lt attribute gt 354 Appendix E Reporting Resources E 1 Context Variables Name Description The current locale set in the web frontend activeProject The currently selected KlarosConfiguration If no project is se lected this variable contains the null object A KlarosUser object representing the active user parameters A Map of parameter objects representing the entered parame ters when running the report The map key consists of the pa rameter name attribute the value is of type de verit klaros scripting model Parameter Table E 1 Context Variables The context variables can be accessed via SeamPDF by e g
283. meter implements Serializable I Public Constructors public Parameter ScriptParameter source Public Methods public public public public public public public public public public public String getDefaultValueQ List lt String gt getDefaultValues String getDescriptionQ String getLabel String getNameO List lt String gt getOptions String getOptionsStringO ScriptParameterType getType String getValue List lt String gt getValues boolean isMandatory Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 4 4 Parameter Parameter source ScriptParameter getName String getDescription String getType ScriptParameterType get Value String get Values List lt String gt getDefaultValue String getDefaultValues List lt String gt isMandatory boolean getLabel String getOptions List lt String gt getOptionsString String B 2 4 1 2 Parameter ScriptParameter public Parameter ScriptParameter source 337 Model API Reference Instantiates a new parameter Parameters source the source script parameter B 2 4 1 3 getDefaultValue public String getDefaultValueO Gets the default value Parameters return the default value B 2 4 1 4 getDefaultValues public List lt String gt getDefaultValuesO Gets the default values Parameters retu
284. mmended requirements Remote Database 4GB RAM 3GHz Dual Core CPU s Recommended requirements Local Database 8GB RAM 3GHz Quad Core CPU Operating system Microsoft Windows XP Microsoft Windows Server 2003 Microsoft Windows Vista Mi crosoft Windows Server 2008 Microsoft Windows 7 Microsoft Windows Server 2012 Mi crosoft Windows 8 or Microsoft Windows 8 1 Java Runtime Environment Oracle Java Runtime Platform Standard Edition 7 or 8 3 2 2 4 Linux To run Klaros Testmanagement on Linux operating systems the following requirements should be met s Minimum requirements 2GB RAM 2GHz Single Core CPU s Recommended requirements Remote Database AGB RAM 3GHz Dual Core CPU Recommended requirements Local Database 8GB RAM 3GHz Quad Core CPU Operating system Linux IA32 Intel 32 bit architecture or Intel64 x86 64 Intel 64 bit architecture distribu tion containing Version 2 2 1 or better of the GTK widget toolkit and associated libraries Note I The GTK libraries are only needed to run the Klaros Testmanagement in staller in windowed mode Running the installer in console mode will work without this requirement Java Runtime Environment Oracle Java Platform Standard Edition 7 or 8 18 Installation Open file limitation A Caution Klaros Testmanagement Enterprise Edition stores database search indices in the file system in the klaros indexes folder in home directory of the user ac count t
285. n public Set lt KlarosTestRun gt getTestRuns public int hashCodeO Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait TT S Sextends LabeledObject KlarosLabeledObject lt T S gt i KlarosSUTImplementation getConfiguration KlarosConfiguration getProductversion String getTestRuns Set lt KlarosTestRun gt getlssues Set lt Klaroslssue gt getCategories Set lt KlarosSUTImplementationCategoryNode gt compareTo o KlarosSUTImplementation int equals o Object boolean hashCode int getlterations Set lt Klaroslteration gt getAttachments Set lt KlarosAttachment gt 300 Model API Reference B 1 1 54 KlarosSUTImplementationCategoryNode An category node for SUT implementations B 1 1 54 1 Synopsis public final class KlarosSUTImplementationCategoryNode extends KlarosCategoryNode lt KlarosSUTImplementation KlarosSUTImplementationCategoryTree KlarosSUTImplementationCategoryNode SUTCategoryNode gt Public Constructors public Klar
286. n 11 12 13 5 12 PM B 24 Mobile Devices Job Excel Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM S 4 Gar Job PDF Overview Report 1 0 Lists the defined Jobs in a project grouped by selectable parameters admin 11 12 13 5 12 PM B EA ys IIEEE 829 Testrun Deviation Report Template v1 1 0 IIEEE 829 Testrun Deviation Report Template v1 admin 11 12 13 5 12 PM B Fi a Integration IEEE 829 Test Plan Template v1 1 0 IEEE 829 Test Plan Template v1 admin 11 12 13 5 12 PM B a San IEEE 829 Test Case Specification Template v1 1 0 IEEE 829 Test Case Specification Template v1 admin 11 12 13 5 12PM BR EZ Please enter all needed parameters ments found Page 1 of 1 1 10 w Start Date 11 19 2013 New page Sort By Test Environment Sort By System Under Test End Date 11 19 2013 Sort By Test Result C Cancel Figure 10 3 Generate a parameterized Report Note The Generate button becomes visible after entering all required parame ters To create a new report click the New button A new report is created and the Report Details page is shown To edit an existing report click the icon Clicking the S icon removes the corresponding report from the report repository 10 2 1 Report Details On the Report Details page it is possible to set the name and description of the report A valid script and a report template must also be provided in order to save the user defined repor
287. n Detected coocoonconcncnccnnoccnnrcancnaccnnnnacos 33 362 MENNENE ee 34 36 3 Database Migration a 35 3 7 Important FE LOCATIONS ss es EE he DR GE ie Ed 36 A AI PEER DE EED EE EE HE RES 36 3 42 Ver Hibernate Properties File ss lenin 37 3 4 3 NTS HE ae 37 ST The QUOtes File NRS 37 57 5 INe Derby Database orure 37 3 7 6 The Attachment Repository aone e E 37 3 8 Running Klaros Testmanagement esec ecce eee eee ecce e eee eee eee ee eee 37 3 9 Changing the Default Database i e eee eee eee 37 3 10 Installing Klaros Testmanagement as a Service see eee eee ee ee de ee de 39 3 10 1 Installing Klaros Testmanagement as a LINUX Service eee eee ee ee ee 39 3 10 2 Installing Klaros Testmanagement as a Windows Service esses 39 3 11 Monitoring Klaros Testmanagement sese eee eee eee eee eee eee eee eee 41 3 12 Configuring External Issue Management Systems eee eee eee see eee ee ee eee 42 E E JRA CONAGUA id 42 3122 REGMING COMMMOUPAUON var 42 512 3 Tac Server EON 44 A ME EIS A o NE EN TER NE EP 46 SE FU REE EE EEE TE N 46 LOEN are 47 21 MAG AGC se ie Re ee DE oe ie Eg 47 FT DENG ENEEIER 47 2 2 UO OO CSS TT 48 FUNCIONA NEMNE 49 EN Ese oa EIE EE RE N 49 5 22 MAA PUACUONS oda 51 52 Tie Hep MEN 51 522 TNE User MEN 52 B2 Searcld 7 OUST 52 524 ME Eas Panel ER ER ED IE GE GE Ge SG GE ED N Ee aac 54 5 25 FIteNNg and SANG sen 54 e PIPE is HR E E 56 5227 HET Za UON na ina e EE EET E E 57 52 03 CONCE HINAING cin 59
288. n addition it is possible to control the startup of the application during the installation If the Launch Application Server checkmark is set the application server will be launched automatically during the installation process If the Launch Browser checkmark is set a native web browser instance will be redirected to the application login page Both of these actions happen during the Section 3 3 8 Step 8 Perform External Processes phase The installation may be aborted by clicking the Quit button Clicking Previous but ton goes back to the Select Installation Packages step and clicking Next button proceeds with the installation 3 3 7 Step 7 Installation The seventh step starts the installation of Klaros Testmanagement and shows its progress The following screenshots show the Installation in Progress Screen and the Installation fin ished screen Figure 3 7 24 Installation Installation maan Y klaros Pack installation progress C Users gidley Klaros Testmanagement ib annotations api jar omcat 8 Application Server Overall installation progress Previous Next Quit Installation m Y klaros ov Pack installation progress Finished Overall installation progress g ETE Made with IzPack http izpack org Figure 3 8 Installation Finished Screen The installation may be aborted by clickingthe Quit button Clicking Next proceeds with the ins
289. n issue management system to a project Clicking on the Create Issue button on the results page which is displayed after the execution of a test case or test suite opens the Create Issue page By default the system uses the credentials entered at the login screen to authenticate the user against the issue management system If the credentials entered at login do not work and the issue management system has not yet been used during the session Klaros Test management will request new authentication information in a dialog The content of the Issue Management page is mostly dependent on the issue management system in use and its capabilities but all of the pages for the various issue management systems have some elements in common Issue Management System When there are more than one issue management systems configured for the project the issue management system where the new issue will be created can be selected in the issue management system drop down field Save The Save button creates or updates an issue in the se lected issue management system Cancel The Cancel button discards unsaved changes and di rects the user back to the test execution New After an issue has been saved an additional New but ton is provided to allow the creation of more than one issue e g in another issue management system 127 Execute The following fields are available for the JIRA issue management system Summary Issue Type Priority
290. n name and port of the remote JMX server you want to deliver messages to 3 12 Configuring External Issue Management Systems Depending on the type of Issue Management System some configuration is needed to con nect it to Klaros Testmanagement This section describes the needed installation steps for each system mme feen 1 x and up Users of previous Redmine ver sions are strongly encouraged to upgrade their Redmine installations and their WS AP I plugins Table 3 3 Supported External Issue Management Systems 3 12 1 JIRA Configuration To allow the connection of Klaros Testmanagement to the JIRA server instance the JIRA RPC Plugin has to be activated in your JIRA installation You find this option as Accept remote API calls in General Configuration under Global Settings Then you need to enable the JIRA RPC Plugin in Plugins under System in the left hand menu 3 12 2 Redmine Configuration 3 12 2 1 Redmine1 x The Klaros Testmanagement Redmine Integration for Redmine 1 x requires the installation of the Redmine Mylyn Connector 2 7 6 for Redmine 1 0 1 4 Prerequisites 1 Redmine 1 0 x STABLE with enabled RESTFUL API Procedure 3 1 Installation 1 Open a shell in your Redmine directory 2 Execute ruby script plugin install force N 42 Installation git redmin mylyncon git sourceforge net gitroot redmin mylyncon redmine mylyn connector gt Note These steps require the ruby git bindings
291. ncluded in a test suite a popup will be displayed before deleting the object see Figure 5 17 EZ Define BEET YF Execute Evaluate SET Ho WebApp S E gt p 7 Requirements Projects Iterations GEE HB Categories Fiter Sort El 10 v R irements ID e Revision Name Priority Action Test Environments C R00011 1 0 Integration Test Project Low EEB Systems under Test Y R00010 g 10 Continuous Integration High Sa Test Cases RO0009 g 10 Project Setup High 22308 TestSutes 7 me 7 A un Gee R00007 1 0 Ui Low 22808 A Do you really want to delete this requirement gt R00006 1 0 U Low Ban M inn JR This requirement is linked to one or more test cases Aus Gan C R00003 1 0 ci R00010 1 0 Continuous Integration Medium 2 eB R00002 1 0 Ri l i EE High 208 These objects will be removed from the following iteration ITRO0001 Setup phase found Page 1 of 2 1 2 gt gt bi 10 vw Figure 5 17 The Delete Objects Popup 5 2 10 Bulk Actions gt edition Feature only available in Klaros Testmanagement Enterprise Edition ition Pages in Klaros Testmanagement which allow editing of a list of objects often also allow bulk actions on these objects These allow the user to select multiple entries in the list and e g display the print page for them or delete duplicate or revision them Assigning objects to a category is also carried out through a bulk action
292. nder Test C T800002 10 Sprint02 0 3 SNAPSHOT y 0 EFE Test Cases Ts00001 8 1 0 Sprint Null 0 2 SNAPSHOT y 3 22808 Test Suites Revision Name System under Test Test Cases Action Figure 6 27 The Test Suites Screen The Test Suites screen shows all of the test suites in the current project Direct editing of the displayed attributes is possible here The leftmost column allows test suites to be selected for bulk actions The uppermost check box is a global select button which selects or deselects all elements shown in the table Please note that the displayed elements are subject to the current search and catagorization criteria Test Suites may be viewed on a printer friendly page as described in Section 5 2 6 Print Pages as well as categorized as described in Section 5 2 7 Categorization 6 7 1 Bulk Actions Ka enterprise Feature only available in Klaros Testmanagement Enterprise Edition edition dl Define Some bulk actions are available on the Test Suites page Bulk actions are described in Sec tion 5 2 10 Bulk Actions The bulk actions available on this page are Edit Print Delete Duplicate selected Items Create new Revisions Add Test Cases and Assign to Category The bulk action buttons can be found above the table on the left 6 7 2 Create Test Suites New test suites can be created by clicking the New button Figure 6 27 The test suite ID is automatically assig
293. nds to the Klaros Testmanagement account password e g userPassword Full Name Attribute The LDAP attribute containing the full name of the user account e g cn If specified this will be automatically be transferred into the Klaros Testmanagement database upon first successful login Email Attribute The LDAP attribute containing the email address of the user account e g mail If speci fied this will automatically be transferred into the Klaros Testmanagement database up on the first successful login Enabled Attribute If specified this boolean LDAP attribute decides whether a user will be able to be authen ticated Not all directory servers provide such an attribute 182 Configure If the Set as default checkmark is activated the login screen will default to LDAP authenti cation for all users It is still possible for existing users to authenticate against the Klaros Testmanagement user database if selected in the login screen Upon the first successful login a matching password hash is created in the local user data base so that users can also authenticate themselves against the local user database with their LDAP password If the Disable Password Synchronization checkmark is activated this synchronization will not be performed and users will only be able to login locally when an administrator assigns them a local password interactively Pressing the Test LDAP access link tests whether the parameters entered on thi
294. ned and the Description and System under Test may be specified by the user The test suite is created in the currently selected project Clicking the Edit icon opens the Test Suite Details section Section 6 7 3 Test Suite Details Clicking the duplicates a test suite 6 7 3 Test Suite Details Clicking the Edit icon opens the Test Suite Details page and allows editing of the test suite s description and its system under test and of the list of the test cases in this test suite also changing their order Figure 6 28 00000000 The assigned System under Test of a Test Suite P gt The assignment of a test suite with a system under test does not affect the func tionality of Klaros Testmanagement The test suites can be still run with other systems under test This attribute is just a guideline for the user Clicking the icon adds the test case to the test suite clicking the icon removes the test case from the test suite and clicking the opens a dialog which allows the user to change the order of the test cases The icon allows to quickly find and remove all duplicate test case entries in the test suite After invocation it displays a dialog listing all duplicates found If the dialog is confirmed all duplicates are removed from the test suite and the test suite is saved 00000000 How to create a new revision of a test suite Ea Clicking the New Revision button creates a new revision of the test suite This button
295. ned test environments The number of test cases The number of test suites The number of test case results The number of test suite results The average of the number of test case steps The average of the test case execution times The only configurable property of the report is its display name al Project Overview Systems Under Test T Test Environments 3 Test Cases 40 Test Suites 26 Test Case Results 445 Test Suite Results T Average Steps per Test Case 1 Average Test Execution Time 32 Second s Figure 9 5 The Project Overview Report 138 Evaluate 9 1 2 2 The Latest Success Rate Report The Latest Success Rate report shows the ratio of the newest test runs for a selected combi nation of system under test and test environment The configurable properties of the report are The display name of the report A boolean value indicating that this report always uses the active project Klaros Testman agement Enterprise Edition only Alternatively the fixed project that this report will display A boolean value indicating that this report always uses the active iteration if available Alternatively the fixed iteration that this report will display if available The system under test to display The test environment to display Success Rate E Success rate of the executed tests for SUT KLAROS 1 0 and Test Environment 1 6 0 13 Tomcat 6 0 18 Sun Microsystems Inc Windows XP
296. ng of the attributes The leftmost column allows test environments to be selected for bulk actions The upper most checkbox is a global select button which selects or deselects all elements shown in the table Please note that the displayed elements are subject to the current search and catagorization criteria Test Environments may be viewed on a printer friendly page as described in Section 5 2 6 Print Pages as well as categorized as described in Section 5 2 7 Categorization Clicking on the delete icon removes the test environment A Why is the Delete button sometimes disabled Test environments that are referenced by test runs cannot be deleted so their delete icon is disabled Clicking on an edit icon displays the Test Environment Details page of the corresponding test environment 6 4 1 Bulk Actions Ke editi n Feature only available in Klaros Testmanagement Enterprise Edition edition _d Some bulk actions are available on the Environments page Bulk actions are described in Section 5 2 10 Bulk Actions The bulk actions available on this page are Edit Print Delete and Assign to category The bulk action buttons can be found above the table on the left Define 6 4 2 Creating a Test Environment Clicking on the New button creates a new test environment in the currently selected project Figure 6 16 The description field can then be specified The test environment ID is automat
297. ninstall Klaros Testmanagement select Uninstall Klaros Testmanagement Server from the Start menu if running under Windows or just delete the installation folder manually If you have added an installation as a service as described in Section 3 10 Installing Klaros Testmanagement as a Service please remember to deactive the Windows service or Linux init script AR Home Folder Just like during the upgrade process uninstalling Klaros Testmanagement will not touch your home folder user home klaros So if you uninstalled by accident re installing will let you restore your system safely else remove feel free to remove that folder manually 46 Chapter 4 Customization Some parts of Klaros Testmanagement may be customized by the user including the display languages and the quote of the day file 4 1 Languages Klaros Testmanagement supports the addition of custom languages To add a language to Klaros Testmanagement a language file must first be added to the klaros resources messages folder in the home directory of the user running Klaros Testmanagement The available languages can be enabled disabled using the Languages page in the system parameters section The process of enabling and disabling available languages is described in Section 10 5 4 1 Enabling and Disabling Languages 4 1 1 Defining Language Files Adding a valid language file to the klaros resources messages directory causes the lan
298. nish successfully Ea Note It is highly recommended to create a backup of your database before starting the Klaros Testmanagement update process Most database products offer util ities for backing up database schemes please refer to the relevant sections in the database vendor documentation If you are using the pre configured derby database you may skip this step but you should make sure to execute the fol lowing instructions In addition to the database Klaros Testmanagement stores various data like con figuration files attachments and logs in the klaros folder located in the home directory of the user running the Klaros Testmanagement application server In case of using the pre configured derby database this includes the database as well For a safe upgrade process you should create a backup of this folder as well before starting the update 3 6 1 Incompatible Installation Detected If you re trying to install a new version of Klaros Testmanagement in some cases you will re ceive the message Incompatible installation detected see Figure 3 12 Incompatible In stallation detected In this case Klaros Testmanagement needs to be uninstalled first be 33 Installation fore a new version can be installed As with the update process all of your settings database settings and the content repository will remain untouched by the uninstallation process Made with lzPack hitp izpack orgl Cre
299. ntent to Excel 12 7 Backup Recovery To move data between different database installations or to selectively import data Klaros Testmanagement provides the functionality to import and export database content via XML files Section 10 7 Backup explains the import and export functionality in detail 208 Glossary A Admin Administrator Artifact Bugzilla C Category C Coverage Compliance D Database Defect Defect Management Sys tem E E Mail Error See Administrator User role that has access to all functionalities in Klaros Testman agement An Artifact is a definable object like a Project Iteration Require ment Test Environment System under Test Job Test Case Test Suite or Test Case Bugzilla is an open source bug tracking and testing tool Artifacts can be assigned to any number of user defined cate gories Using Categories Users can group related Artifacts togeth er A database is a collection of information organized into interrelat ed tables of data and specifications of data objects A database is a collection of information organized into interrelat ed tables of data and specifications of data objects See Issue See Issue Management System Electronic mail often abbreviated as e mail is any method of creat ing transmitting or storing primarily text based communications with digital communications systems An error is the inability of the sy
300. nts a REST interface is available which allows you to upload your data from the command line or other applications The following example shows how to import an Excel sheet containing requirements into the project named P00001 using the curl command line application curl is available in almost any Linux distribution and for the Microsoft Windows operating system family as part of the Cygwin http www cygwin com distribution or as a command line tool from http curl haxx se download html curl v T Requirements xls lt klaros app url gt seam resource rest import requirement xls config P00001 Example 12 5 Excel Requirement Import via Command Line If the Klaros Testmanagement installation requires authentication for import username and password arguments have to be appended to the curl call curl v T Requirements xls lt klaros app url gt seam resource rest import requirement xls config P00001 amp username user amp password secret Example 12 6 Excel Requirement Import via Command Line with authentication P Note All artifacts which are referenced during import like projects or test cases con tain five digits in their id For example P00001 is a valid project ID while PO1 and P001 are not 12 4 Importing and Synchronizing Requirements from XML Klaros Testmanagement allows to both import and synchronize requirements from XML Files An import is limited to a one time action which will always create new instances
301. nts found Page 1 of 2 1 2 gt 10 y Figure 10 5 The Maintain Users Page 10 3 1 Creating a User Clicking the New button creates a new user account Figure 10 5 The User Name Full Name E Mail Address and Role attributes can be set here directly When the Save button is clicked a dialog will appear for each new user account to set the Password and System Account flag Figure 10 6 Per default users of role Administrator or Manager are able to create new user accounts Users of role Manager can only create accounts of role Tester or Guest Limit account creation to administrators If a more stringent approach is desired the Only Administrators can create Users setting can be used to limit user creation to the administrator role See Sec tion 10 5 1 Miscellaneous Settings for more information Define SL S WebAapp L verview S Oveme New Save Discard Report Templates Fiter Sort El 10 v User Name e Full Name E Mail Role Action Mobile Devices LMiller Leon Miller Tester v 4 System O admin AN John Doe doe company com Administrator 2e Integration C devManager Devon Manager Test Manager 2 a Backup manager A Max Mustermann max mustermann company com Test Manager a E O peter Additional Input Required Tester Ga susan N p Tester 2 E A To create this new user a password has to be assigned system Tester 2 E tester ann company com Tester Fi User Name LMiller
302. ocked 2 TC00002 amp 1 0 Project setup check Manual Locked 1 TC00003 1 0 Continuous Integration check Manual Draft 2 Test Environment tomcat ad hoc 9 R System under Test 0 2 SNAPSHOT Execute Cancel Figure 8 9 The Detailed Information about the Test Suite Screen Before a test run is started a test environment and a system under test must be chosen user defined properties may also be set for the test run here Press the Execute button to run the test suite Klaros Testmanagement will show the following pop up window 121 Execute Tabular View 2 T500001 Sprint Null Test Case dors Test Suite TS500001 Name Sprint Null Revision 1 0 Test Cases 3 System under Test 0 2 SNAPSHOT Test Environment tomcat ad hoc Test Case Overview Test Case TC00001 Name IDE check Description Revision 10 Precondition Postcondition Steps 2 System under Test 0 2 SNAPSHOT Test Environment tomcat ad hoc Start Skip Test Case Cancel Figure 8 10 The Overview Screen Note Pop ups must be enabled in your browser or an exception must be added for Klaros Testmanagement in order to execute tests manually This screen shows the test suite overview and the attachments of the test suite if it has any Clicking the icon starts the download of the corresponding attachment Clickthe Start button to begin the manual test run By default the step by step instruc tions screen will open but this can
303. oe im A Q TCR0000015 11 8 13 8 03 30 PM TC00002 tomcat ad hoc 0 2 SNAPSHOT John Doe 1ms A Q IGRT RIE TCR0000014 11 8 13 8 03 30 PM TC00001 tomcat adhoc 0 2 SNAPSHOT John Doe 1ms Test Suite R It est Suite Results Back Issues Figure 9 16 The Test Run Details Screen mobile edition d Only available in Klaros Testmanagement Mobile Edition If a test run has been executed on a mobile device an info icon will be displayed in the info column Pressing this icon will open up the Mobile Device Details page of the mobile device see Section 10 4 Mobile Devices B 16 14 11 05 43 AM TCRODODO12 61614 11 05 43 AM Figure 9 17 The Test Run Info Column 145 Evaluate 9 4 1 The Test Run Report This type of report is generated in PDF format and its layout is shown in Figure 9 18 It details the date of execution of a test run and its result specifying the test cases executed and whether they were successful failed or ended in error Additionally a pie chart summarizes the result is shown Y klaros Test Run Report Y klaros Feb 11 2014 5 15 FM Reported Test Runs ra SUT Po0004 T74 00900 14 2111114 5 15 45 FM BUTODOO Klarss Tesimanssemerd 4 0 ENYDDDD3 Windows E Test Result Summary Passed OG Failed Error Skipped Test Result Details Enter Usezmame Fassad Ermer password Fassed Click login Passed TCO Beleci a project Fassed e 2 455 FOGG TRUDOO
304. of the supplied requirements On the other hand synchronisation allows to update existing re quirements with the content in the XML file and create new revisions of them when needed The format of the XML file is described in Appendix D Requirement Import File Specification For validation purposes an XML schema is also available from the following URL http www klaros testmanagement com files schema klaros requirements 1 0 xsd 12 4 1 Prerequisites To import XML based requirements the following prerequisites have to be met 1 The file that is going to be imported has to be in XML format matching the given XML schema 2 The project that should contain the imported requirements has to be already created 202 Import Export 3 If the Authentication required for import flag is set see Section 10 5 1 Miscellaneous Set tings username and password of a system user have to be provided see Section 10 3 3 User Details for more information on system users 4 If custom properties are to be used they have to be defined for the project prior to starting the import process Please note that custom properties are only supported in the Klaros Testmanagement Enterprise Edition 12 4 2 Importing To import XML based requirements a REST interface is available which allows you to upload your data from the command line or other applications The following example shows how to import an XML file containing requirements
305. of a single job the executed test results and change history for the Job are also shown in this section Figure 7 4 The Job Properties page allows the user to change the following attributes Name The name or summary of the Job Description The description of the Job s Priority The priority of the job Possible values are in order of severity Trivial Minor Major Critical and Blocker Blocker means that the job should be executed before further progress in the project can be made e Status The status of the job Possible values are New In Progress Resolved Closed Reopened and Rejected mnn The job is being The job is being executed rejected The job can be executed again m EED Figure 7 3 The Job States e Estimated Time 108 Plan The estimated time in hours that the job will take Finished The current percentage of completion of the job Start Date The date when the job should be started Due Date The deadline when the job should be finished Assignee The user responsible for the job Test Case The test case that should be executed with this job Either a test case or a test suite can be assigned to a job This field is unavailable if the job contains sub jobs Test Suite The test suite that should be executed with this job Either a test case or a test suite can be assigned to a job This field is unavailable if the job contains sub jobs System under
306. oint in time where the execution of the job has to be completed at the latest Test Case Test Suite The test case or test suite which is covered by this job System under Test The system under test which has to be used when executing this job Test Environment The test environment which has to be used when executing this job Estimated Time The estimated time needed to complete this job Progress The progress rate shows how many test cases which are covered by this job have been executed regardless the result Success The success rate shows how many of the test cases which are covered by this job have been successfully executed in the latest test run Total Time Spent How much time has actually been spent testing This value is calculated by adding up the individual execution times from the work log Latest Executor The executor which has executed the latest test run of this job Latest Test Runs This graph displays the accumulated test case results of the latest test runs for this job in descending order Executon Time This graph shows the minimum average and maximum execution times for this job Latest Test Runs This table shows the latest completed test runs for this job 00000000 gt Note By default this table shows only five entries Pressing the Show all button opens up the results tab in which all test runs are listed 107 Plan 7 1 5 2 Job Properties This section allows in depth editing
307. oject named P00001 using the curl command line application curl is available in al most any Linux distribution and for the Microsoft Windows operating system family as part of the Cygwin http www cygwin com distribution or as a command line tool from http curl haxx se download html curl v T Requirements xml lt klaros app url gt seam resource rest sync requirement xml config P00001 Example Requirements xml input lt xml version 1 0 encoding UTF 8 standalone yes gt lt r container xmlns r http klaros testmanagement com export requirement 1 0 gt lt r requirements gt lt r requirement gt lt lt lt lt lt lt lt cy oy r r 3 PE attributes gt externalId gt RTM 00001 lt r externalId gt externalRevision gt 1 0 lt r externalRevision gt priority gt MEDIUM lt r priority gt shortname gt Remote controlled door panels unlocking lt r shortname gt summary gt Doors must me remote controllable lt r summary gt requirement gt lt r requirements gt lt r container gt Example 12 9 XML Requirement Synchronization via Command Line 204 Import Export If the Klaros Testmanagement installation requires authentication for import username and password arguments have to be appended to the curl call as shown below curl v T Requirements xml lt klaros app url gt seam resource rest import requirement xml config P00001 amp username user amp pas
308. om several test frameworks If the related test cases are not already defined in the Klaros Testmanagement database they will be automatically created The following frameworks are supported AUnit AUnit provides mechanisms by which developers can test their Aspect aspects in isolation in support of Test Driven Development Boost Test The Boost Test library provides a matched set of compo nents for writing test programs organizing tests into sim ple test cases and test suites and controlling their runtime execution Check Check is a unit testing framework for C CppTest CppTest is a portable and powerful yet simple unit testing framework for handling automated tests in C The focus lies on usability and extendability CppUnit CppUnit is a C unit testing framework ctest ctest is the testing driver provided by CMake CUnit CUnit is a lightweight system for writing administering and running unit tests in C Free Pascal Unit Free Pascal Unit is a port to Free Pascal of the JUnit core framework 124 GUIdancer Jubula JUnit MbUnit MSTest NUnit PHPUnit QF Test QTestLib Ranorex Selenium Test Complete TestNG TUSAR Execute GUIdancer is an Eclipse based tool for automated function al testing through the Graphical User Interface GUI Jubula provides automated functional GUI testing for vari ous types of applications JUnit is a simple framework to write repeatable tests It is an
309. om within this tab See Section 7 1 Maintain Jobs for more information on how to manage jobs 98 Define 6 6 3 9 Results The result tab is further divided into a Test Runs and Test Case Results tab showing the test re sults related to this test case as described in Section 5 2 14 Related Test Runs and Results 6 6 3 10 Bookmarking Test Cases Ka edition y Feature only available in Klaros Testmanagement Enterprise Edition Test cases may be linked to from outside of Klaros Testmanagement using the link on the bookmark icon Right click the icon and choose Copy Link Location Firefox Chrome or the equivalent option 6 7 Test Suites A test suite is a set of test cases which can be executed sequentially The results of the test suite execution are grouped together in Klaros Testmanagement and can be used to verify and ensure that a system meets its design specifications and requirements Test suites may be created removed duplicated updated and assigned to categories on this page The displayed test suites may be filtered and sorted as described in Section 5 2 5 Filtering and Sorting Figure 6 27 Plan TF Execute qa Evaluate X Configure Swnp Test Suites Projects EE Iterations Ss _ E E ES B Categories Fiter Sort El 10 v ID e Revision Name System under Test Test Cases Action Test Environments TS00003 10 SprintO1 0 2 SNAPSHOT y 0 2 BEA Requirements Systems u
310. on B 1 1 19 5 getIssues public abstract Set lt KlarosIssue gt getIssues Gets the issues related to this system under test Parameters return the issues B 1 1 19 6 getIterations public abstract Set lt KlarosIteration gt getIterations Get the iterations this system under test is assigned to Parameters return Set of iterations this system under test is assigned to B 1 1 19 7 getProductversion public abstract String getProductversion Get product version Parameters return The version id of the system under test B 1 1 19 8 getTestRuns public abstract Set lt KlarosTestRun gt getTestRuns Get the test runs performed with this system under test Parameters return Set of test runs performed for this system under test 249 Model API Reference B 1 1 20 IKlarosTag This interface provides access to the data of a tag B 1 1 20 1 Synopsis public interface IKlarosTag Public Methods public abstract Set lt KlarosRevision lt gt gt getRevisions public abstract String getTagldO public abstract Date getTimestampQ B 1 1 20 2 getRevisions public abstract Set lt KlarosRevision lt gt gt getRevisions Get related revisions Parameters return Collection of revision objects which are related to this tag B 1 1 20 3 getTagId public abstract String getTagIdO Get tag id Parameters return The id of the tag B 1 1 20 4 getTimestamp publi
311. on 5 2 13 Revisions 6 3 3 7 Bookmarking Requirements Requirements may be linked to from outside of Klaros Testmanagement using the link on the bookmark icon Right click the icon and choose Copy Link Location Fire fox Chrome or the equivalent option 6 4 Test Environments 83 Define The Test Environments section allows the management of the test environments in the se lected project Test environments represent the extrinsic settings that may influence the test result Examples for components of a test environments are the operating system or an application server e g Tomcat 7 on Ubuntu 12 10 Test environments may be created removed updated and assigned to categories on this page Figure 6 16 The displayed test environments may be filtered and sorted as described in Section 5 2 5 Filtering and Sorting Plan TF Execute q Evaluate X Configure S weap P D Test Environments Projects Iterations 258 B Categories Fiter Sort El 10 v EE inaa ENV00005 amp tomcatad hoc 2 5 Systems under Test ENV00004 Produktion 2g Test Cases ENV00003 Staging e a Test Suites ENV00002 a Test 2 EE ENV00001 Developer local IDE integriert E a ID Description Action New Figure 6 16 The Test Environments Screen The Test Environments page shows all of the test environments defined for the current project Clicking on the table fields allows direct editi
312. on Edit View This view allows the creation and naming of category groups and categories as well as the organization of category hierarchies Pressing the add button at the top of this view creates a new category group and enables the use of the category group dropdown menu If a category group is selected it can be renamed in this view Categories may also be added and edited in this view Pressing the add button ona category adds a new sub category By default a new category tree contains one category and all future categories are added as sub categories of this Root Category Categories may be renamed by changing the value in the name field and also given a description through use of the edit button Changing the hierarchy of categories and ordering them is also possible in the editview through use of the arrow buttons 5 2 7 2 The Tree View Plan 4 Execute Evaluate Y Configure af FA Test Cases Projects New Iterations HE Requirements mar Accepted y m El Test Environments ER All 0 3 Systems under Test Management Development 3 3 Test Suites aero B Categories Fiter Sort 10 y Revision Traceability Priority State Execution Steps Action TC00003 8 1 0 Continuous Integration check Medium Approved w Manual 2 AALGE Tcooo002 a 1 0 Project setup check High Locked w Manual 1 Al O Tcoo001 8 10 IDE check Low M Draft v Manual vy 2 SDR Revision Traceability State
313. on or capability of the system under test Each test case can relate to one or more re quirements and vice versa More information regarding requirements is shown in Section 2 7 2 3 Test Suites Organizing Test Cases Figure 2 3 A Test Suite Multiple test cases can be combined into another artifact that is called Test Suite When ex ecuting a test suite all test cases that are part of this test suite are executed in a row by the tester The same test cases can be part of multiple test suites and changes to a test case will auto matically be reflected in all test suites referencing it Introduction 2 4 Test Runs Executed Tests with their Results Figure 2 4 Test Run with Test Results Every time a tester executes test cases or test suites a Test Run containing the correspond ing Test Case Results is created The test run consists of all test case results created during the execution of a test case or test suite and stores additional information about the circum stances of the test run shown in the next section The simplest case is the execution of a single test case This generates a test run with a single result the test case result If a test suite is executed there will usually be more than one test result one result for each test case The test suite result lists all the test results of the executed test suite Test runs can be paused and continued at a later time This means that it is possible that n
314. one icon is used to duplicate a step at another position Individual steps may be minimized while editing to help to keep track of Steps which are being edited Pressing the Toggle View Mode displays the individual test case steps in a tabbed view to save space The and 7 icons can be used to expand or collapse all test case steps 97 Define Test steps are removed by pressing on the delete icon The Save button must be pressed to persist this change Figure 6 23 6 6 3 5 Attachments Attachments may be added to test cases This process is described in Section 5 2 12 At tachments 6 6 3 6 Revisions Test cases are revisionable The process of revisioning an object is described in Sec tion 5 2 13 Revisions 6 6 3 7 Issues Plan Execute pi Evaluate y Configure WebApp 2 L TC00003 1 1 Continuous Integration check are Projects Back Iterations eee Overview Properties User Defined Steps 3 Attachments 3 Revisions Issues 5 Jobs Results Changes Requirements Test Environments E 70 v Systems under Test ID System System under Test Summary Created Created By Assigned To Priority State Action 1539 X IM00004 0 3 SNAPSHOT Capitalization doesnt work 11 7 2012 Redmine Admin Tim Tester Normal New EA D Test Suites PLAYGROUND 5374 Y M00001 Error during login 11 28 2010 hudson hudson Blocker Open Q PLAY GROUND 5373 IM00001 0 2 Exception while selecting an item 11 28 2010 hudson hudson Blocker
315. onsiders only if a test case has been executed at least once in this test environment regardless of the result passed failed error Compliance The compliance rate shows how many test cases which are part of this iterations require ments have been successfully executed in this system under test Coverage The coverage rate shows how many test cases which are part of arequirement have been executed at least once in this system under test 89 Define Note GA In contrast to the compliance rate the coverage rate considers only if a test case has been executed at least once in the iteration regardless of the result passed failed error e Success History This graph shows changes in the compliance coverage progress and success rates of this test environment over time The timeline is automatically adjusted depending on the given timeframe e Most unstable Test Environments This table displays the test environments which have the lowest success and progress rates in conjunction with this system under test 00000000 E Note e This table is limited to five entries The other test environments can be viewed by pressing the Show All button s Latest failing Test Cases This table lists the test cases which recently have been failed during a test run for this system under test alongside with the appertaining test case result 00000000 gt Note gt This table is limited to five entries Th
316. osAttachment 277 KlarosCategoryNode 278 KlarosCategoryTree 279 KlarosConfiguration 280 KlarosContext 322 KlarosContextParameter 329 KlarosEnumValue 282 KlarosExternallmplementation 282 KlarosIssue 283 KlarosIteration 284 KlarosIterationCategoryNode 285 KlarosIterationCategoryTree 286 Klarosjob 287 KlarosjobTimeBlock 289 KlarosjobUpdateAction 290 KlarosLabeledObject 291 KlarosNamedEntity 292 KlarosProperty 293 KlarosQueryFactory 324 KlarosRequirement 294 KlarosRequirementCategoryNode 295 KlarosRequirementCategoryTree 296 KlarosRequirementGroup 297 KlarosRevision 298 KlarosSUTImplementation 299 KlarosSUTImplementationCategoryNode 301 KlarosSUTImplementationCategoryTree 301 KlarosTag 302 KlarosTestCase 303 KlarosTestCaseCategoryNode 305 KlarosTestCaseCategoryTree 306 KlarosTestCaseResult 307 KlarosTestCaseState 308 KlarosTestCaseStep 309 KlarosTestCaseStepResult 310 KlarosTestEnvironment 311 KlarosTestEnvironmentCategoryNode 312 KlarosTestEnvironmentCategoryTree 313 KlarosTestExecutable 314 KlarosTestRun 315 KlarosTestSuite 316 KlarosTestSuiteCategoryNode 318 KlarosTestSuiteCategoryTree 319 KlarosTestSuiteResult 320 KlarosUser 321 Parameter 336 ParameterContext 339 Parameterlype 340 TestRunReport 334 Create Issue 117 118 D date 330 E Error 116 118 Expected Result 97 F Failure 116 118 Fields applicationBaseUrl 330 date 330 imageProvider 330 param
317. osSUTImplementationCategoryNode SUTCategoryNode wrapped Public Methods public List lt KlarosSUTImplementation gt getReferences Methods inherited from de verit klaros core model KlarosCategoryNode getCatego ryTree getDescription getParent getShortname getSubCategories Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait EEE ET 1 W W extends KlarosCategoryNode lt l T W P gt P Pextends CategoryNode KlarosCategoryNode lt KlarosSUTImplementation KlarosSUTImplementationCategoryTree KlarosSUTImplementationCategoryNode SUTCategoryNode gt DA KlarosSUTImplementationCategoryNode KlarosSUTImplementationCategoryNode wrapped SUTCategoryNode getReferences List lt KlarosSUTImplementation gt B 1 1 54 2 KlarosSUTImplementationCategoryNode SUTCategoryNode public KlarosSUTImplementationCategoryNode SUTCategoryNode wrapped Instantiates a new klaros sut implementation category node Parameters wrapped the wrapped class B 1 1 55 KlarosSUTImplementationCategoryTree An category tree for SUT implementations B 1 1 55 1 Synopsis public final class KlarosSUTImplementationCategoryTree extends 301 Model API Reference KlarosCategoryTree lt KlarosSUTImplementation KlarosSUTImplementationCategoryTree SUTCategoryTree KlarosSUTImplementationCategoryNode SUT
318. ot all results that are stored in the database already have a known verdict in this case the verdict is listed as Unknown 2 5 Test Environment and System under Test Influences of Test Results Whenever a test case or test suite is executed it needs to be executed in a defined Test Environment and one executes it against a defined System under Test The result of a test is influenced by the version of the system being tested system under test SUT since issues are detected in a particular software version but may then be fixed in a later version Test environments represent external conditions which may have impact on the test result like e g the operating system the system under test in running in To document this prop erly every test run is linked to a particular system under test and test environment 2 6 Iterations Subdividing your project into phases An Iteration can group jobs systems under test test environments and requirements within a project for a selectable time frame Every iteration represents a selected part of the project and its artifacts including all test results gathered during this phase Grouping the artifacts like this makes it easier to identify different test cycles of a project This allows for better integration of the test process especially with agile software development techniques Introduction 2 7 Reduirements Meeting Ouality Standards To confirm if the system under test meet
319. ow many of the test cases of this requirement are automated 81 Define Q Y Manual test cases can often be converted to automated test cases if they are frequently executed to save time Compliance History This graph shows how the compliance and the coverage for this requirement have changed since the requirement has been defined The timeline is automatically adjusted depending on the given timeframe Latest Failing Test Cases This table lists the test cases which recently have been failed during a test run for this requirement alongside with the appertaining test case result Note I This table is limited to five entries The other test case results can be viewed by pressing the Show All button 6 3 3 2 Requirement Properties This page Figure 6 15 allows the user to view or change the following attributes of the selected requirement s ID Assigned automatically Name The editable name of the requirement Priority The priority of the requirement Can be Low Medium High or empty State The requirement state determines whether it is editable or visible in reports Only require ment with the state Draft are editable A requirement with the state Skip is not shown in any reports Summary A short summary of the requirement 82 Define Plan YF Execute pa Evaluate X Configure S WebApp 2 a 1 0 RO0008 Development environment Q E Projects Back IGEREM E Properties Use
320. perties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 288 Model API Reference KlarosLabeled KlarosJob getConfiguration KlarosConfiguration equals o Object boolean hashCode int compareTo o Klarosbb int getbbType bbType getbbPriority bbPriority getbbStatus JobStatus getSummary String getDescription String getStartDate Date getDueDate Date getProgress Integer getSuccessRate Integer getTestCase KlarosTestCase getTestSuite KlarosTest Suite getSut KlarosSUTImplementation getEnv KlarosTestEnvironment getParent Klarosbb getSubbbs List lt Klarosbb gt getUpdateAction List lt KlarosbbUpdateAction gt get Work Lists KlarosJob TimeBlock gt getTestRuns Set lt KlarosTestRun gt getAttachments Set lt KlarosAttachment gt getEstimatedTimelnMilliseconds Long getEstimatedTime String B 1 1 43 KlarosjobTimeBlock The implementation of a job time block measuring a unit of work done for a job B 1 1 43 1 Synopsis public final class KlarosJobTimeBlock extends KlarosWrapper lt KlarosJob
321. played The title bar of the re port contains the reports name and an edit button When the edit button is clicked the parameters of the report can be configured in the resulting dialog The changes in the configuration can be applied to the report by clicking the Apply button or discarded by clicking the Cancel button Additionally the name of the report can be configured by clicking on the name in the title bar of the report The configured dashboard can be persisted by clicking the Save button in the upper right corner of the dashboard If the Cancel button is pressed the changes in the con figuration of the dashboard are discarded All reports can show data from the currently selected project or from a project selected in the report settings 137 Evaluate Klaros Testmanagement Community Edition comes with three predefined reports The Project Overview Report The Latest Success Rate Report The Test Activity Report These reports are described in the following sections In addition Klaros Testmanagement Enterprise Edition contains three additional reports The Project Health Report The Test Progress History Report The Test Progress Report These reports are also described in the following sections 9 1 2 1 The Project Overview Report The Project Overview Report shows the main properties of a project listed in a table The report Shows The number of defined systems under test The number of defi
322. pplication This setting must be changed to the account of the user you intend to use for running Klaros Testmanagement in the service account settings This change is needed due to the fact that the default location for the klaros folder in the user account home Skipping this vital step will lead to a newly created klaros home folder in the C Windows System32 systemuser folder this location may vary with your Windows version in use newer version may use C Windows system32 config systempro file instead containing a new empty database which will now be used by the service instead of the database present when starting Tomcat manually If you encounter this situation then shut down the service delete the klaros folder in the Windows System32 folder change the user account settings of the service and finally restart the service Make sure to use a Java architecture that matches with your Tomcat installation Upon first installation of Klaros Testmanagement the installer chooses a match ing Tomcat Windows installation 32 Bit vs 64 Bit for the Java runtime architec ture it was started with If you want to change the desired Java Runtime Architecture later e g switching from 32 Bit Java to 64 Bit Java please make sure that you re install your distri bution with the desired Java runtime in your system path If in doubt check by running javaw version from the cmd windows command line processor The service will refuse to start
323. r Defined Attachments Test Cases Revisions Results Changes Test Environments ID R00008 Name Development environment Priority High v Systems under Test Test Cases Summary The checks for the development enviornment IDE CI etc Test Suites Description Created by Devon Manager on 10 30 13 2 22 PM Last changed by John Doe on 11 20 13 7 23 PM Back Figure 6 15 The Requirement Details Screen 6 3 3 3 User Defined Properties User defined properties can be used to customize requirements within Klaros Testmanage ment by adding custom fields This process is described in Section 5 2 11 User Defined Properties 6 3 3 4 Attachments Attachments may be added to requirements This process is described in Section 5 2 12 Attachments 6 3 3 5 Test Cases Coverage of requirements is tested by test cases Users can link test cases to requirements in the Test Cases tab The test results of linked test cases count towards the execution and success rates of the requirement Test cases may be assigned to the requirement by clickingthe Assign button This opens a dialog which allows Test Cases to be selected Test cases may be removed from the re quirement one at a time by clicking the icon in the Action column or in bulk by selecting test cases and clicking the icon above the table 6 3 3 6 Revisions Requirements are revisionable The process of revisioning an object is described in Sec ti
324. r Sort 5 10 ID Summary Priority Status Progress Success Due Action JOB00007 Projekt aufsetzen a Major New EA 40800002 Ausf hrung TC00001 IDE check A Major Resolved ET 0 31 2013 2 Back Figure 7 10 The Jobs By User Screen 113 Chapter 8 Execute This chapter describes the processes of executing test cases and test suites continuing in terrupted test suite executions and creating issues for tests that failed 8 1 My Jobs eed Feature only available in Klaros Testmanagement Enterprise Edition ition _d The My Jobs page shows the jobs for the active user and allows them to be executed Figure 8 1 0 Execute Fi Evaluate X Configure IT TEE ae O Filter Sort El 10 Run Test Case Summary Priority Status Progress Success Due Action AUS JOB00011 Ausf hrung TC00003 Continuous Integration check y Minor Reopened TEEN 2 Y A JOBO00010 Ausf hrung TC00002 Projekt setup check w Minor Reopened TEEN 2 Y JOB00009 Ausf hrung TC00001 IDE check w Minor Reopened MC 2 Y Import Test Results Jobs without Assignee Fiter Sort El 10 lt ID Summary Priority Status Progress Success Due Action JOB00008 Execution TS00001 Sprint Null a Major InProgress ETE Nov21 2013 2 amp JOB00005 manual iter job A Major New 0 ae Figure 8 1 The My Jobs Screen Details such as the number of assigned jobs the total estimated time for the jobs the time frame for the jobs
325. ract KlarosTestCase getTestCase Get the associated test case Parameters return The test case that has been executed to get this result B 1 1 22 8 getTestRun public abstract KlarosTestRun getTestRun Get the associated test run 259 Model API Reference Parameters return The test run that created this result B 1 1 22 9 getTestSuitePosition public abstract Integer getTestSuitePosition Return the position in the the test suite result this test case result belongs to or null if this test case has not been executed by executing a test suite Parameters return the position of the test case in the test suite or null B 1 1 22 10 getTestSuiteResult public abstract KlarosTestSuiteResult getTestSuiteResult Return the test suite result this test case result belongs to or null if this test case has not been executed by executing a test suite Parameters return the test suite result or null B 1 1 22 11 isError public abstract boolean isError Check if this is an error result It is assumed that error results have a property type with the value E or error Parameters return true if this results represents an error B 1 1 22 12 isFailure public abstract boolean isFailure Check if this is a failure result It is assumed that failure results have a property type with the value F or failure Parameters return true if this results represents a failure B 1 1 22
326. rationCategoryNode IterationCategoryNode public KlarosIterationCategoryNode IterationCategoryNode wrapped Instantiates a new klaros iteration category node Parameters wrapped the wrapped class B 1 1 41 KlarosIterationCategoryTree An category tree for Iteration implementations B 1 1 41 1 Synopsis public class KlarosIterationCategoryTree extends 286 Model API Reference KlarosCategoryTree lt KlarosIteration KlarosIterationCategoryTree IterationCategoryTree KlarosIterationCategoryNode IterationCategoryNode gt Methods inherited from de verit klaros core model KlarosCategoryTree getDescrip tion getRootNode getShortname Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait LET S S extends LabeledObject KlarosLabeledObject lt T AAA E A E E E E E El I W W extends KlarosCategoryTree lt l W P X Y gt I P P extends CategoryTree X X extends KlarosCategoryNode lt l W X Y gt I Y Y extends CategoryNode L KlarosCategoryTree lt Klaroslteration KlaroslterationCategoryTree I
327. re A comma separated list of the LDAP object classes a user account must match to be in cluded in the search e g person posixAccount Enable naive DN Matching Mode If this option is enabled a returned DN of a user search is used to identify the user to be authenticated If it is disabled the following two parameters will be used in conjunction with the User Name Attribute to build a DN to authenticate with User DN Prefix The distinguished name prefix used to locate user accounts e g uid User DN Suffix The distinguished name suffix used to locate user accounts e g 0u Users dc acme dc com When locating user accounts the prefix the account id and the suffix are concatenated to form the distinguished name of the user account Parameters describing the attributes of a user account User Search Attribute The LDAP user name attribute which corresponds to the Klaros Testmanagement account name e g uid User Name Attribute The LDAP attribute which will be used in the DN bind action which authenticates the user if no naive DN Matching mode is active In simple scenarios this will match the User Search Attribute If your LDAP Server setup does not allow you to bind a user with the specified user search attribute you should specify the corresponding attribute here e g cn and use this in conjunction with the corresponding user DN prefix suffix User Password Attribute The LDAP password attribute which correspo
328. re 9 24 shows the individual step edit dialog 149 Evaluate Fi Define E Plan gt Execute iid Evaluate N Configure Test Case Result TCR0000009 TC00001 Testing the file upload of the ticket system Dashboard Report Templates Properties Changes Test Run History Summary The Issue cannot be created Test Case Results Test Suite Results z Description The window to putin the issue data does not open therefore no issues can be created Issues by Test Case Edit Test Case Step Result Link Issues Result A v Failure Create Issues gape A Summary The window doesn t open Start 11 19 13 3 11 Executor John Doe Execution time 00 01 28 Sed Description The window to put in the issue data does not open Test Run TRU000000 Test Case TC00001 T Test Environment ENV00002 System under Test SUT00001 Save Cancel Steps Number Summary Description 1 Log into the ticket system EA 2 Press the button Create new Ticket EA 3 Press the button Attach file to ticket A The window doesnt open The window to put in the issue data does not open EA 4 Select the file testzip for uploading and press OK 2 5 Press the button Save Ticket O 2 Upload Attachment Back Figure 9 24 Editing Test Case Step Results Clicking the icon starts a retest of the test case enterprise Feature only available in Klaros Testmanagement Enterprise Edition edition j This scr
329. re si WebApp L L Dashboard Report Templates Dashboard Test Run History Test Runs S Test Environment Report 5 PDF e HTML E csv Test Case Results S System under Test Report 5 POF e HTML E csv Test Suite Results D Test Suite Report B PDF le HTML E csv Issues by Test Case EE Project WebApp Latest results of the executed Test Cases for SUT 0 2 Create Issues Systems under Test 6 SNAPSHOT and Test Environment tomcat ad hoc Test Environments 5 Test Cases 3 Test Suites 3 Test Case Results 46 Test Suite Results 3 Average Test Execution Time 0 Second s Passed 1 Failure 1 Error 1 Latest Test Activity Test Activity Last 30 days for SUT 0 2 SNAPSHOT and Test Environment tomcat ad hoc ER w ma N f R Number of Results gt N 4 o N Passed W Failure M Error New Figure 9 1 The Dashboard Screen 9 1 1 The Overview Reports The upper part of the dashboard shows a table with the available overview reports The following three types of reports are available e Test Environment Overview The Test Environment Overview report shows the test runs that have been executed in each test environment containing the execution date and quantity of success failure and error results An example of the report is shown in Figure 9 2 134 Evaluate Test Environment Overview Y klaros Y klaros Project HORUS P00002 Author Felix Muster
330. re subject to the current search and catagorization criteria Test cases may be viewed on a printer friendly page as described in Section 5 2 6 Print Pages as well as categorized as described in Section 5 2 7 Categorization gt Warning Sign in the ID Column A test case which has execution set to manual and contains no steps is not exe cutable To indicate this a warning sign is displayed in the ID column Clicking on the delete icon removes the test case Warning Only test cases that are not referenced by results or test suites can be deleted 6 6 1 Bulk Actions TF EN enterprise edition dl Feature only available in Klaros Testmanagement Enterprise Edition Some bulk actions are available on the Test Cases page Bulk actions are described in Sec tion 5 2 10 Bulk Actions 92 Define The bulk actions available on this page are Edit Print Delete Duplicate Create new Revisions Create new Test Suite and Assign to category The bulk action buttons can be found above the table on the left 6 6 2 Creating Test Cases Clicking the New button creates a new test case Figure 6 21 An empty row is added at the beginning of the table The fields Name Traceability Priority State and Execution of the test case can be specified The test case ID is automatically assigned by Klaros Testman agement The test case is created in the currently selected project Clicking the edit
331. resolution of this issue The format and content of this value varies with the issue management system and its configuration Parameters return the resolution of this issue B 1 1 8 11 getState public abstract String getState Gets the state of this issue The format and content of this value varies with the issue man agement system and its configuration Parameters return the state string of this issue B 1 1 8 12 getSubject public abstract String getSubjectO Gets the subject of this issue Parameters return the subject string of this issue B 1 1 8 13 getTestCases public abstract Set lt KlarosTestCase gt getTestCases Get the related test cases Parameters return Set of test cases which have detected this issue B 1 1 9 IKlarosIteration An iteration in a project B 1 1 9 1 Synopsis public interface IKlarosIteration extends IKlarosNamedEntity Public Methods public abstract Set lt KlarosAttachment gt getAttachments public abstract Set lt KlarosIterationCategoryNode gt getCategories public abstract StateDef getCurrentStateQ public abstract String getDescription public abstract Date getDueDate public abstract Set lt KlarosTestEnvironment gt getEnvs public abstract Set lt KlarosJob gt getJobs 228 Model API Reference public abstract String getShortname public abstract Date getStartDateQ public abstract String getSuccessCriteria public abstract
332. rg hibernate dialect PostgreSQLDialect hibernate connection username root hibernate connection password root An exhaustive list of all parameters can be found in the Hibernate Core Manual Database Instance Creation Klaros Testmanagement will not automatically create either the database in stance klaros in the above example or the database user user root with pass word root in the above example in the database server Creating a database instance and adding a user is described in the corresponding database manual and will not be covered here The database user needs permissions to create drop and alter tables to properly bootstrap the Klaros Testmanagement data base instance 38 Installation Z Make sure to activate support for UTF 8 character sets Depending on your database product it may be needed to manually activate sup port for UTF 8 character sets which may be needed to support languages with uncommon character sets Especially MySQL is known for coming with a limited character support in its initial configuration The following example shows how to activate this by editing the mysal cnf configuration file character set server utf8 collation server utf8 general ci Example 3 2 Additional entries in mysql cnf to support UTF 8 character sets 3 10 Installing Klaros Testmanagement as a Service For day to day usage of Klaros Testmanagement it is necessary that the application is avail able after a reboot of
333. ripting Table B 1 KlarosQueryFactory 342 Appendix C Test Case Import File Specification The following table gives a short overview of the available elements name pnan O lt testsuite gt If this element is present a test suite with the name given here will be generated upon import lt traceability gt The traceability information for this test case ager gt The externally initiated trigger for this test case 343 Test Case Import File Specification name Reina SSS lt triggers gt The list of triggers for this object lt value gt The value of the custom attribute lt variety gt The result expectation of the test Whether a positive or negative re sult is expected Table C 1 Element summary 344 Test Case Import File Specification C 1 lt step gt A test case step This element may occur inside the following elements lt steps gt eeo ON E ON E CI Table C 2 lt step gt elements C 2 lt steps gt The list of contained test case steps This element may occur inside the following elements lt testcase gt s e IA Table C 3 lt steps gt elements C 3 lt attribute gt A custom attribute This element may occur inside the following elements lt attributes gt Table C 4 lt attribute gt elements C 4 lt attributes gt The list of custom attributes This
334. rn the default values B 2 4 1 5 getDescription public String getDescriptionQ Gets the description Parameters return the description B 2 4 1 6 getLabel public String getlLabelO Gets the label Parameters return the label B 2 4 1 7 getName public String getNameO Gets the name Parameters return the name B 2 4 1 8 getOptions public List lt String gt getOptions Gets the options 338 Model API Reference Parameters return the options B 2 4 1 9 getOptionsString public String getOptionsStringO Gets the options string Parameters return the options string B 2 4 1 10 getType public ScriptParameterType getTypeO Gets the type Parameters return the type B 2 4 1 11 getValue public String getValueO Gets the value Parameters return the value B 2 4 1 12 getValues public List lt String gt getValues Gets the value Parameters return the value B 2 4 1 13 isMandatory public boolean isMandatoryO Checks if is mandatory Parameters return true if is mandatory B 2 4 2 ParameterContext The context for script parameters B 2 4 2 1 Synopsis public class ParameterContext 339 Model API Reference Public Constructors public ParameterContext List lt ScriptParameter gt parameters Public Methods public Map lt String Parameter gt getParameters Methods inherited from java lang Object equals getClass hashCode not
335. ros Testmanagement supports revisioning of require ments test cases and test suites Different versions can be applied to individual systems under test and test environ ments with full traceability of their results Klaros Testmanagement allows to save binary content of any type text documents graphics screenshots etc to test cases and their results iterations requirements SYS tems under test test environments and test suites With Klaros Testmanagement reports and statistics for test results can easily be assembled All test related data is stored in a database and can be accessed at any time The report files can be exported into various file formats such as PDF HTML CSV and TXT Klaros Testmanagement supports the tester during execu tion of manual tests A web based client leads the tester through the test steps allows him to attach comments and attachments and automatically records the test process and results Manual execution can be paused whenever and be re sumed any later time Klaros Testmanagement supports a fine grained role based user management system connected with a rights and role system In this way the access and editing rights of single users can be restricted for critical data A Jenkins Hudson plug in enables transfer of results of au tomated tests on the continuous integrations server to Klaros Testmanagement Integration with Bugzilla JIRA Mantis Redmine and Trac enable direct documenta
336. rt summary of the issue The ease of reproduction of the issue The priority and type of the issue The version of the system that is affected The category of the issue The current status of the issue The current resolution of the issue The detailed description of the issue A text field for additional information about the issue 131 Execute Issue Management System IMOOOOS Mantis Server EO Summary Reproducibility always Severity feature lt Priority none Is Version 2 0 Category Left Category Status new Resolution open A Description http localhost8080 klaros web browse jsp typertestCaseResult amp Additional information ia MULTILIST 3 4 5 FLOAT ENUM Ais NUMERIC DATE LIST 1 EMAIL STRING CHECKBOX Mandatory fields must be filled Update Test Case State S State Skip Save Back Figure 8 19 Mantis Issue Page jm To change the state of the related test case just activate the Update Test Case State button and choose the new state from the drop down box For more detailed information about each field please consult the documentation of the respective issue management system The created issues can be inspected in the Issues by Test Case page of the Evaluate section see Section 9 7 1 Issues by Test Case for more details 8 7 Creating Review Jobs ection Feature only available in Klaros Testm
337. rter Parameters testrun the Test Run return the converter B 2 3 1 5 getDate Date public String getDate Date d Gets the date Parameters d the date return the date B 2 3 1 6 getTestCase KlarosTestRun public String getTestCase KlarosTestRun testrun Gets the test case Parameters testrun the Test Run return the Test Case Name B 2 3 2 JobReport The Class JobReport A Java snippet to create an Job Report Template B 2 3 2 1 Synopsis public class JobReport implements KlarosScript Public Constructors public JobReportO Public Methods public void execute KlarosContext context public String getColorcint index public final List lt gt getConverter Set lt gt testrun public String getDate Date date 332 Model API Reference Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait JobReport Job Report execute context KlarosContext void getColor index int String getDate date Date String getConverter testrun Set lt gt List lt gt B 2 3 2 2 getColor int public String getColorcint index Return the background color code for the given table row index This method implements a zebra color schema with alternating colors for odd and even rows Parameters index the row index return the HTML color code string B 2 3 2 3 getConverter Set lt gt public final List lt gt g
338. rties User Defined Copy Test Cases Access Results Changes Requirements Test Environments 10 y Systems under Test Object Type Name Default Action E z A S ll Requirement Text requirement number 0 Test Suites Test Case Boolean regression test O A ED ee Edit the elements of the enumeration S en ser S N HCS MES New Firefox S Opera Created by John Doe on 11 18 13 5 24 PM Last changed by John Doe on 11 19 13 3 43 PM Chrome Save Discard Back Entry Internet Explorer dp Confirm Cancel Figure 5 21 Editing an Enumeration Property Once user defined properties are configured they can be edited in the User Defined tab of the relevant object Figure 5 22 Note If no user defined properties are configured for the object type this tab will only contain a link to the project s user defined tab in order to create some EZ Define E Plan Execute Fi Evaluate X Configure Issue Management System Integration FA p 2 P00003 Issue Management System Integration a SS Back Iterations a r Properties User Defined 5 Copy Objects Access Results Changes Requirements Test Environments 15 Systems under Test Type Name Default Action E SO gel Y f A aS Test Cases Requirement Text Requirement Number 0 6 pot Case anlean i A Test Suites Test Case Boolean Regression Test E S Iteration Text Code S Iteration Text Field Sprint goals S System under Test Enumeration 2 Application Server Tomcat 8 0
339. rview Plan po Execute qa Evaluate y Configure WebApp 2 L LZ 5 TC00001 IDE check SE Projects Iterations Overview Properties User Defined Steps 2 Attachments Revisions Issues Jobs 2 Results 31 Changes Requirements Test Environments oe De Execution Manual Systems under Test Priority Low Latest Executor John Doe Test Cases Test Suites Execution Times of this Test Case Most unsuccessful Test Case Steps E 24 a 8 a S Maximum B 6 E Failure E Average 2 44 E Error amp Minimum Q 1 Z LL 0 1 2 o Step poe ar es Produkton EEE Wows st Staging Ya mees RSD nane baan UPN OA 0 1 0 2 0 2 SNAPSHOT 6 0 3 SNAPSHOT Latest Results ID 2 Name Start Executor Test Run Test Environment System under Test Duration Result Action TC00001 IDE check 11 20 13 8 24 06 PM John Doe TRU0000015 tomcatad hoc 0 2 SNAPSHOT 6 1ms Q TC00001 IDE check 11 20 13 8 24 14PM John Doe TRU0000016 tomcatad hoc 0 2 SNAPSHOT 6 1 ms O TC00001 IDE check 11 20 13 8 29 39 PM John Doe TRU0000027 tomcat ad hoc 0 2 SNAPSHOT 6 1ms A Q TC00001 IDE check 11 20 13 8 03 30 PM John Doe TRUO0000010 tomcat ad hoc 0 2 SNAPSHOT 6 1 ms O Q TC00001 IDE check 11 20 13 8 24 21 PM John Doe TRU0000017 tomcatad hoc 0 2 SNAPSHOT 6 1ms Q Show all Figure 5 27 The Test Case Overview Tab 67 Chapter 6 Define This section describes the Define section of Klaros Testmanagement In this section Projects Iterations Requirements
340. ryNode 318 KlarosTestSuiteCategoryTree 319 KlarosTestSuiteResult 320 KlarosUser 321 L Link Issue 117 Login 49 N Notification 171 Notification Scheme 170 P Parameter 336 ParameterContext 339 parameters 330 Parameterlype 340 Passed 116 118 Postcondition 95 97 116 118 Precondition 95 97 116 118 Print Pages 56 Projects 68 Create Project 69 R Reduirements 9 S Skip 116 118 Skip All 116 Systems under Test 87 T Test Test Case 114 Test Suite 120 Test Cases 91 Test Environments 83 Test Execution 117 Test Suites 99 TestRunReport 334 Index U user 330 W WRAPPER PREFIX 325 361
341. ryTree A generic category tree B 1 1 34 1 Synopsis public class KlarosCategoryTree lt I W extends KlarosCategoryTree lt I W P X Y gt P extends CategoryTree X extends KlarosCategoryNode lt I W X Y gt Y extends CategoryNode gt extends KlarosNamedEntity lt W P gt implements IKlarosCategoryTree lt I W P X Y gt Public Methods public String getDescription public KlarosCategoryNode lt I W X Y gt getRootNode public String getShortnameO Direct known subclasses de verit klaros core model KlarosIterationCategoryTree de verit klaros core model KlarosRequirementCategoryTree de verit klaros core model KlarosSUTImplementationCategorylree de verit klaros core model KlarosTestCaseCate goryTree de verit klaros core model KlarosTestEnvironmentCategoryTree de verit klaros core model KlarosTestSuiteCategoryTree 279 Model API Reference Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait X X extends KlarosCategoryNodes l W X Y gt Y Y extends CategoryNode KlarosCate
342. s Testmanagement installation and database are migrated to a different location this folder should be moved with them 3 8 Running Klaros Testmanadement To access Klaros Testmanagement open the following URL in a web browser http host port klaros web where host is the IP address or domain name of the appli cation server and port is the HTTP port defined in Section 3 3 6 Step 6 User Data The first time Klaros Testmanagement is executed it will create a klaros folder containing Klaros Testmanagement and database property files The klaros folder is created in the home directory of the current user For Microsoft Windows XP users it is located in C Docu ments and Settingslusername for Microsoft Windows Vista and Microsoft Windows 7 8 users it is in C Users username and for Linux users in home username by default 3 9 Changing the Default Database By default Klaros Testmanagement uses the Apache Derby Database which requires no fur ther installation or maintenance but is lacking performance in comparison to other imple mentations For production systems it is strongly recommended to use a full blown data base system such as the open source PostgreSQL or MariaDB MySQL database servers or the commercial Microsoft SQLServer or Oracle database products To switch to another database system Klaros Testmanagement must be stopped and the file hibernate properties located in lt user home gt klaros hib
343. s User Defined Attachments Results 11 Comments Work Log 4 Changes Jobs from Test Suites eee Type Test Execution Manual Test Suite TS00001 Sprint Null Status Reopened System under Test SUT00004 0 3 SNAPSHOT Priority a Major Test Environment ENV00008 Ubuntu 14 04 1 LTS Assignee Torsten Divers Estimated Time 00 30 00 Start Date 9 hours from now Due Date 2 days from now Latest Test Runs 4 1 15 3 36 PM 3 30 15 10 30 AM S 3 30 15 10 23 AM m Pesad Z L E Failure le ER 3 24 15 11 17 AM E Error Skipped S 1 8 18 14 2 33 PM La 0 1 2 3 Results 0 Latest Test Runs Start Executor Test Case Suite Test Environment 3 30 15 10 30 04 AM John Doe TS00001 Solaris 11 2011 11 3 30 15 10 23 39 AM John Doe TS00001 Solaris 11 2011 11 Show all Created 2 years ago by John Doe Figure 7 2 The Job Overview Tab Type Swap F O TKL Back Progress Success Total Time spent 00 00 52 Latest Executor John Doe Execution Time S Maximum E Average amp Minimum System under Test Action 0 2 SNAPSHOT 6 Q 0 2 SNAPSHOT 6 Q Last changed moments ago by John Doe Back The job type Test Execution Automated Test Execution Manual or Task if the job isn t related to a test case Status The status of the job s Priority The priority of the job s Assignee Who is assigned for this job Start Date The earliest point in time this job can be executed by a tester 106 Plan Due Date The p
344. s in the Groovy script add the Klaros model libraries to the build path of your Eclipse project Instead of manually entering the code for each text area the code can be imported from a file Specify the file to be use by clicking on the Browse Button and select the file from the file system Click OK in the file dialog and afterwards click Upload to import the selected file into the text area This page provides three actions to be executed To test the code click on the Preview button to generate areport The Save button stores the reportinto the Klaros repository in the file system The changes can be discarded by pressing the Back button lt Note The generated report is opened automatically in a new browser window If this does not work for you please check if you have a pop up blocker active To provide a certain degree of freedom to the report users and to make the reports more flexible it is possible to pass parameters to the Groovy script This mechanism can for ex ample be used to pass a time span to the Groovy script so that only data for this time span is retrieved from Klaros Testmanagement 188 Custom Reports To pass arguments to the report click the New Parameter button A new section as shown in Figure 11 4 Specifying Parameters is displayed which enables the addition of parameters Clicking the button allows a parameter to be added to the parameter list AE Execute Pl Evaluate E Configure Issu
345. s its guality standards it is needed to document which of the system requirements are covered by tests Coverage and how many of them have been executed with a passed result Compliance To enable this traceability it is needed to link requirements to one or more test cases and vice versa From this set of information Klaros Testmanagement is able to automatically determine cov erage and compliance information for the whole project or selected artifacts once the first test results are available 2 8 Jobs Planning the test process Many users may execute tests in Klaros Testmanagement simultaneously To orchestrate this process it is recommended to plan the testing activities of the users The planned exe cution of a test case or a test suite by a user is defined in the form of a Job which is also an artifact Jobs usually reference a test case or test suite The intended test environment and system under test may be defined beforehand by the creator of a job Jobs also contain a start date when the testing should begin a due date a deadline for the execution of the test and may be assigned a priority how urgent the test execution is Available priorities are Trivial Minor Major Critical and Blocker Jobs may also contain status information like Resolved Reopened Closed In Progress or New to document their progress After a job has been created it can be assigned to a user This user then can execute the job and set its
346. s page are correct The test process in divided in two phases In the first phase a bind to the server is attempted and a search for all matching users is conducted If it is successful a dialog is shown listing the matching users found in the LDAP directory In the second phase a username and a password may be entered to test the actual LDAP authentication The result of the authentication attempt is logged in the logpanel E Define 8 Plan TF Execute q Evaluate E Configure S pon P Error getting users CommunicationException localhost 389 ConnectException Connection refused connect x Overview S Integration Report Templates Users Issue Management E Mail Network LDAP Mobile Devices Server Address localhost User Context DN ou Person dc acme dc com System Server Port 389 User Object Classes person uidObject i Enable naive DN Matching Mode Integration Bind DN cn Manager dc acme dc com g Bind Credentials e User DN Prefix uid Backu 7 Follow Referrals User DN Suffix ou Person dc acme dc com Authentication required for LDAP User Search Attribute uic cn User Name Attribute uic User entries found y mail User Password Attribute us f TED Please enter a valid user name and password to validate the authentication at the LDAP server Set as default UserName admin lization Password eeeee oK Cancel Figure 10 29 The LDAP Authentication Popup 10 7
347. s section will be the tabular view Rows per table page With this option the number of rows per table page can be set Quote of the day The message to display on the login screen Use random quote of the day If true a line from the file uploaded below will be displayed as the quote of the day Upload quotes This allows the user to upload a quotes file to be used for the random quote of the day This should be a text file named quotes txt with one quote per line The details of the current quotes file are shown below including a download link for the file itself and a delete button which causes the default quotes file to be restored A Caution Please refer to Section 4 2 Custom Quotes for detailed information on the file format 173 Configure 10 5 4 Languages Klaros Testmanagement supports the addition of custom languages The available lan guages can be set in the Languages section of the system parameters section The language settings page is shown in Figure 10 20 The Languages Tab Plan YF Execute fa Evaluate E Configure Issue Management System Integration System Miscellaneous Interface Languages Enabled Languages Available Languages le Mobile Devices English en US Geman ee 00 S Integration Report Templates Users Backup J Refresh messages files Figure 10 20 The Languages Tab 10 5 4 1 Enabling and Disabling Languages Up to 5 languages
348. s the attachment to be removed from the Klaros Testmanage ment database The Save button must be pressed to persist this change 5 2 13 Revisions Requirements Test Cases and Test Suites are revisionable artifacts A new revision of an object should be created when a major edit is taking place An old revision of a test case can for example be executed when using a system under test where newly added test steps are not applicable Revisioning of objects can be managed fromthe Revisions tab This tab shows the revi sion history for the object allows the user to change the revision comment associated with each revision and also allows creation of new revisions The revision history table may also be used to select a revision to display and edit Plan kS Execute pa Evaluate y Configure S WebApp 1 1 T500001 Sprint Null aE lt 4 Projects Iterations Properties User Defined Attachments Revisions Results Changes Requirements Test Environments Selected Revision 1 1 Comment Revision 1 1 Systems under Test Revision Created Created By Changed Changed By Comment Test Cases 2 1 0 10 30 13 2 28 PM Devon Manager 11 19 135 01PM John Doe Created Test Suites 5 11 10 30 13 2 28 PM Devon Manager 11 19 135 02PM JohnDoe Revision 1 1 New Revision Back Figure 5 24 The Test Suite Revisions Tab 5 2 14 Related Test Runs and Results enterprise edition _d Feature only available in Klaros Test
349. scription of the iteration Success Criteria A description of the conditions which need to be met for this iteration to be complete Start Date The date on which this iteration starts Due Date The date on which this iteration is due to be finished 77 Define Plan e Execute pi Evaluate X Configure webapp A JJ ITRO0002 Sprint 01 a E Projects Back EE R Properties User Defined Attachments Test Environments Systems under Test Requirements Results Changes equirements Test Environments Name i Systems under Test Sprint 01 Description Minimal functionality Test Cases Test Suites Success Criteria Login works Wrong user pw combination rejected No official acceptance by management or users Start Date 11 11 2013 10 00 Due 25 11 2013 10 00 Created by Ted Steve Manager on 10 29 13 4 37 PM Last changed by John Doe on 11 20 13 7 17 PM Back Figure 6 12 The Iteration Details Screen 6 2 3 2 1 User Defined Properties User defined properties can be used to customize iterations within Klaros Testmanagement by adding custom fields This process is described in Section 5 2 11 User Defined Proper ties 6 2 3 2 2 Attachments Attachments may be added to iterations This process is described in Section 5 2 12 Attach ments 6 2 3 2 3 Test Environments Systems under Test and Requirements Tabs These tabs allow linking of other artifacts to the iteration Simply
350. se Results Screen Clicking the icon starts a retest of the corresponding test case and clicking the C1 opens the test case result page for the corresponding test case The icon opens a dialog which enables the user to create a test suite from the selected test cases The dialog to create the new test suite is shown in Figure 9 21 147 Evaluate Plan kS Execute pil Evaluate X Configure Webapp EE amp Test Cases Projects Mer Iterations _ GaA OR B Categories Filter Sort 10 v Requirements q Revision Traceability Priority Execution Steps Action Test Environments TC00003 8 1 0 Continuous Integration check Medium Approved y Manual 2 28B Systems under Test TC00002 8 10 Project setup check High Locked v Manual 1 BABS OD Tco0001 8 10 IDE check Low v Draft v Mana v 2 2208 Test Suites Revision Are you sure Priority State Execution Steps A The following test cases will be added to a test suite HT HH name TC00003 amp 1 0 Continuous Integration check TC00002 amp 1 0 Project setup check Create new Test Suite Add to an existing Test Suite Test Suite Name Create a new test suite from these 2 test cases Figure 9 21 The Test Suite from Test Case Results Pop up 9 5 1 Single Test Case Results This page shows individual executions of the selected test case The result of each execution is shown as well as the system under test and test environment
351. seCategoryNodes gt A KlarosTestCaseCategoryTree B 1 1 60 KlarosTestCaseResult This class provides access to the information stored for test case results B 1 1 60 1 Synopsis public final class KlarosTestCaseResult extends KlarosNamedEntity lt KlarosTestCaseResult TestCaseResult gt implements IKlarosTestCaseResult Comparable lt KlarosTestCaseResult gt Public Methods public int compareTo KlarosTestCaseResult o public boolean eguals Object o public Set lt KlarosAttachment gt getAttachments public String getDescription public long getExecutionTimeQ public List lt KlarosTestCaseStepResult gt getStepResultsO public String getSummaryO public KlarosTestCase getTestCase public KlarosTestRun getTestRun public Integer getTestSuitePosition public KlarosTestSuiteResult getTestSuiteResult public int hashCode public boolean isError public boolean isFailureQ 307 Model API Reference public boolean isPassed public boolean isPendingO public boolean isSkippedO Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getC
352. shed successfully in 0 4 seconds returning 3 hits in 2 results Figure 5 8 The Status Bar Search Report 5 2 3 2 Quick Select For known element ids like e g TCOOOO1 a quick navigation field is present in the Klaros Testmanagement Community Edition It currently supports the following element types Project Test Environment System under Test Test Case Test Suite Test Case Result Test Suite Result Test Run Issue Management System Please note that ids will usually be searched for in the current project only gt Abbrevation Support It is possible to use case independent abbreviated forms of IDs eg TC00001 TC1 or tc1 will all resolve to the same element 53 Functional Overview 5 2 4 The Log Panel Q The current selected project is Test Development P00016 x Q INFORMATION 10 32 04 The current selected project is Test Development P00016 Q INFORMATION 10 32 03 The Project P00016 has been successfully created Q INFORMATION 10 31 35 The current selected project is Test GPS Tracking P00005 Q INFORMATION 10 31 35 The current selected iteration is Sprint 1 ITRO0001 Q INFORMATION 10 31 33 The current selected project is WebApp P00012 Figure 5 9 The Log Panel The log panel shows status messages like warnings or information to the user Initially only the latest status message is displayed By clicking on the icon on the right side of the log panel all status messages since the
353. shows a list of all test cases in every revision and the number of issues linked to it Pressing the icon opens up a separate page see Section 9 7 2 2 Issues by Test Case Details where the individual linked issues are listed Pressing the New button opens up anew page in where an issue can be created in any of the configured issue management systems and then linked to a test case 9 7 2 Issue Details Creating a new Issue E Define Z Plan Execute id Evaluate MX Configure T weap L Issue Details eile Issue Management System IM00001 JIRA Server MES Report Templates Summary Test Run History Issue Type Bug bs Priority Blocker v A Components Left Component a Test Case Results iaht componen Test Suite Results issues Affected Versions 2 0 1 0 Fixed Versions 2 0 1 0 Due is Description Environment Test Case Y System under Test Y Test Environment v Mandatory fields must be filed Save Back Figure 9 32 The Create Issue Page Upon entering this page at first an issue management system has to be selected from the Issue Management System dropdown list 155 Evaluate 00000000 E Note If the list of issue management systems is empty then at least one issue man agement system has to be configured and also available in the selected project The configuration of an issue management system is described in Section 10 6 1 Issue Management and Section 6 1 6
354. st B 1 1 8 3 getCreationDate public abstract Date getCreationDateQ 226 Model API Reference Gets the creation date of this issue Parameters return the creation date of this issue B 1 1 8 4 getDescription public abstract String getDescription Get the description Parameters return The description of this issue B 1 1 8 5 getExternalld public abstract String getExternalld Gets the external id of this issue if available This id is generated by the external issue man agement system upon creation of the issue Parameters return the external id B 1 1 8 6 getLastSynched public abstract Date getLastSynched Gets the last synchronization date of this issue Parameters return the last synched date of this issue B 1 1 8 7 getOwner public abstract String getOwnerO Gets the name of the owner assignee of this issue Parameters return the owner name of this issue B 1 1 8 8 getPriority public abstract String getPriorityO Gets the priority of this issue The format and content of this value varies with the issue management system and its configuration Parameters return the priority of this issue B 1 1 8 9 getReporter public abstract String getReporterO Gets the name of the reporter of this issue 227 Model API Reference Parameters return the reporter name of this issue B 1 1 8 10 getResolution public abstract String getResolution Gets the
355. stEnvironment getEnvO KlarosIteration getlterationO KlarosJob get JobO int getNumberErrors int getNumberFailures int getNumberPassed int getNumberSkipped String getRelatedSummaryQ Set lt KlarosTestCaseResult gt getResultsO String getRunld KlarosSUTImplementation getSutO KlarosTestSuite getTestSuite Date getTimestamp Set lt KlarosJobTimeBlock gt getWork int hashCodeO boolean isPending Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getProperties isDefinedProperty Methods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 315 Model API Reference S Sextends LabeledObject KlarosLabeledObject lt 1 S gt TEST S Sextends NamedEntity KlarosNamedEntity lt KlarosTestRun TestRun gt KlarosTestRun getConfiguration KlarosConfiguration getNumberErrors int getNumberFailures int getNumberPassed int getNumberSkipped int getRunld String getTimestamp Date getResults Set lt KlarosTestCaseResult gt getSut KlarosSUTImplementation getEnv KlarosTestEnvironment getbb Klarosbb getTestSu
356. stem to perform a test correctly Not to be confused with Failure 209 F Failure Guest GUIdancer I Incident Incident Management Sys tem Issue Issue Management System Issue Tracking System Iteration Java Java Runtime Environment JavaScript Java Runtime Environment Glossary A failure is a discrepancy between a computed observed or mea sured value or condition and the true specified or theoretically correct value or condition Not to be confused with Error User role that can display artifacts and reports but may not change any data GUlIdancer is an Eclipse based tool for automated functional test ing through the Graphical User Interface GUI See Issue See Issue Management System The term issue is a unit of work to accomplish an improvement in a system An Issue could be a bug a requested feature task missing documentation and likewise An Issue Management System Issue Tracking System is a soft ware to manage Issues See Issue Management System An iteration is a complete development loop resulting in a release internal or external of an executable product a subset of the final product under development which grows from iteration to itera tion to become the final product ISTQB glossary Java is a programming language Most often Java is used as a ab breviation for Java Runtime Environment which needs to be in stalled in order to run Klaros Testmanagement
357. sults which can be imported into Klaros Test management See System under Test A System Account is a user that is not able to login at the login page and interactively control the application System Accounts may be used for automated tasks like importing test results A System under Test is used to represent a version of a software product that can be tested A Test Case is a set of input values execution preconditions ex pected results and execution post conditions developed for a par ticular objective or test condition such as determine whether an application or software system meets its specifications The final verdict on the execution of a test and its outcomes like pass fail or error The result of error is used for situations where it is not clear whether the problem is in the test object A test case step consists of execution preconditions expected re sults and execution post conditions for a single action during test execution Test Environments represent the extrinsic settings that may influ ence the test result Examples for components of a Test Environ ments are the Operating System or an application server e g Tom cat 7 on Ubuntu 12 10 212 Tester Test Execution Test Run Test Suite Trac URL W Web browser Windows Glossary User role that has access to display artifacts and reports and run jobs test cases and test suites The process of running a test by the component or
358. sword secret Example 12 10 XML Requirement Import via Command Line with authentication Note J All artifacts which are referenced during import like projects or test cases con tain five digits in their ID For example P00001 is a valid project ID while POT and P001 are not 12 5 Importing Test Results Klaros Testmanagement is able to import test results via a REST interface into the Klaros Testmanagement database 12 5 1 Prerequisites To import test results the following prereduisites have to be met 1 The project iteration test environment and system under test that should contain the imported test case or test suite results have to be created 2 If the Authentication required for import flag is set see Section 10 5 1 Miscellaneous Set tings username and password of a system user have to be provided see Section 10 3 3 User Details for more information on system users 12 5 2 Execution The URL of the import interface is located at http host port klaros web importer The content will be transferred via a HTTP PUT request using the above URL and various URL Query parameters The following parameters are supported config The ID of the project to import the results into e g P0001 iteration The ID of the iteration to relate the results to e g 100001 This parameter is optional env The ID of the test environment in which the tests have been run e g ENV00001 P
359. system under test producing actual result s The result of running a test case or test suite under the same system under test and test environment giving or more test case result s A test suite is a set of test cases and the test cases can be execut ed in groups The test suite will be used to verify and ensure that a product or system meets its design specifications and other re quirements Trac is an open source bug tracking and issue tracking system A Uniform Resource Locator URL specifies where an identified re source is available and the mechanism for retrieving it Examples for URLs are http www klaros testmanagement com or file C klaros txt A Web browser is a software application which enables a user to display and interact with text images and other information typi cally located on a Web page at a Web site on the World Wide Web or a local area network Windows is the name of several Operating Systems by Microsoft 213 Appendix A Role Permission Overview trator Crete raat Create edit and delete users with the role Tester b T T T r Bo Ek ri r Ja ma ba T Maa OF P TE P b Jarr TE Man F Edit system preferences Ta a Global managers are able to restore any project However they may only export projects which have no project specific roles defined or in which they have the role Manager Create edit and delete users with the role Adminis
360. t B 1 1 25 1 Synopsis public interface IKlarosTestCaseStepResult extends IKlarosNamedEntity Public Methods public abstract String getAction public abstract String getDescription public abstract long getExecutionTimeO public abstract String getExpectedResult public abstract String getPostcondition public abstract String getPrecondition public abstract String getSummaryQ public abstract KlarosTestCase getTestCase public abstract KlarosTestCaseResult getTestCaseResult 263 Model API Reference public abstract KlarosTestRun getTestRun public abstract boolean isError public abstract boolean isFailureO public abstract boolean isPassed public abstract boolean isSkippedQ B 1 1 25 2 getAction public abstract String getAction Get the action Parameters return The action of this test case step B 1 1 25 3 getDescription public abstract String getDescription 264 Model API Reference Get the test result description This is usually set for failed error status results Parameters return The test result description B 1 1 25 4 getExecutionTime public abstract long getExecutionTimeO Get the test execution time in ms Parameters return The test execution time B 1 1 25 5 getExpectedResult public abstract String getExpectedResultO Get the expected result Parameters return The expected result of this test case step B 1 1 25 6 getPostcondi
361. t It is possible to edit the script and template in the text area or upload them directly from an external file Clicking the Save button causes Klaros Testmanagement to attempt to save the report to the content repository Note The report is only saved if the script and template are valid and free of errors 161 Configure E Define Plan po Execute L Evaluate SE Configure fed Issue Management System Integration k L Report Template Details OME Revision 10 Report Templates Name Iteration PDF Overview Report pas Description Lists a defined Iteration in a Project Template Type PDF v Edit the Script Mobile Devices System Name Label Type Description Value Action Integration l l i iterationName Iteration ID Text v The ID of the Iteration to generate 1 Backup New Parameter The Class IterationsReport A Java snippet to create an Iteration Report Template public class IterationsReport implements KlarosScript Groow Script Override i public void execute final KlarosContext context final String iterationName String context getParameterValue iterationName String query select g from KlarosIteration g where g name query iterationName query if context getActiveProject null query and g configuration name v query context getActiveProject getName Upload Script Template Edit the Template Preview Save Discard Figure 10
362. t 8 0 Tomcat8 Properties General Log On Logging Java Startup Shutdown Java Virtual Machine C Program Files x66 av aure 5 0 40 bin client jym dll Java Classpath C Program Files x66 Apache Software Foundation Tomcat 8 01bintbool Java Options Djava io tmpdir C Program Files 386 4pache Software Foundatia Bjava util logging manager org apache juli ClassLoaderLogManage Djava util logging config File C Program Files x86 4pache Softwa nk MaxPermsize 120m Only required for Java 7 Runtime Environments Initial memory pool 256 ME Maximum memory pool ME Thread stack size KB Figure 3 15 Additional Tomcat memory settings 3 11 Monitoring Klaros Testmanagement Using the built in JMX Support in Tomcat it is possible to monitor the Klaros Testmanage ment installation using any JMX capable Monitoring tool like e g VisualVM Add the following lines to bin catalina sh Set JMX Connector RMI SERVER FQDN JMXREMOTE Dcom sun management jmxremote JMXREMOTE JMXREMOTE Dcom sun management jmxremote port PORT JMXREMOTE JMXREMOTE Dcom sun management jmxremote ssl false JMXREMOTE JMXREMOTE Dcom sun management jmxremote authenticate false JMXREMOTE JMXREMOTE Dcom sun management jmxremote ssl false 41 Installation JAVA OPTS JAVA OPTS JMXREMOTE Djava rmi server hostname RMI SERVER Where FQDN and PORT denote the fully qualified domai
363. t always uses the active iteration if available Alternatively the fixed iteration that this report will display if available The system under test to display The test environment to display Test Progress EF Test Progress for SUT KLAROS 1 0 and Test Environment 1 6 0 13 Tomcat 6 0 18 Sun Microsystems Inc Windows XP SP3 Executed 8 amp Not executed 32 Figure 9 9 The Test Progress Report 9 1 2 6 The Test Progress History Report enterprise 7 edition i Feature only available in Klaros Testmanagement Enterprise Edition The Test Progress History Report shows the rate of executed vs defined tests of a project for a given test environment system under test and time period The configurable properties of the report are 141 Evaluate The name of the report A boolean value indicating that this report always uses the active project Alternatively the fixed project that this report will display A boolean value indicating that this report always uses the active iteration if available Alternatively the fixed iteration that this report will display if available The system under test to display The test environment to display The time period of the report Test Progress History Ei a Test Progress History for SUT KLAROS 1 0 and Test Environment 1 6 0 13 Tomcat 6 0 18 Sun Microsystems Inc Windows XP SP3 40 35 ER 30 Moer Ve ee IN 25 Count 15 Mar 30 M
364. t contain sub jobs Clicking the icon opens a dialog in which a test case or a test suite can be selected Only one item can be selected at the same time Clicking the icon removes the element from the job This section also contains a Test Runs tab and a Results tab as described in Section 5 2 14 Related Test Runs and Results 7 1 5 2 1 User Defined Properties User defined properties can be used to customize jobs within Klaros Testmanagement by adding custom fields This process is described in Section 5 2 11 User Defined Properties 7 1 5 2 2 Attachments Attachments may be added to jobs this process is described in Section 5 2 12 Attach ments 7 1 5 2 3 Results The result tab is further divided into a Test Runs Test Case Results and a Test Suite Results tab showing the test results related to this job as described in Section 5 2 14 Related Test Runs and Results 7 1 5 2 4 Comments This tab allows a user to add comments by clicking onthe Add Comment button E Dene YG Execute pa Evaluate X Configure 2 Issue Management System Integration SA amp JOB00001 Test the file upload of the ticket system FreeBSD ET ER Maintain Jobs Save Discard Back Jobs from Test Cases Overview Properties User Defined Attachments Results Comments Work Log Changes Jobs from Test Suites Jobs by User Fiter Sot 15 fel Created By Add comment Changed Action No entries available Comm
365. t gt getResultsO public abstract String getRunld public abstract KlarosSUTImplementation getSutO public abstract KlarosTestSuite getTestSuite public abstract Date getTimestampO public abstract Set lt KlarosJobTimeBlock gt getWorkO public abstract boolean isPending B 1 1 28 2 getConfiguration public abstract KlarosConfiguration getConfiguration Get configuration 269 Model API Reference Parameters return The related configuration B 1 1 28 3 getEnv public abstract KlarosTestEnvironment getEnvO Get test environment Parameters return The test environment in which the test cases have been executed B 1 1 28 4 getIteration public abstract KlarosIteration getlteration Get the iteration in which the test run has been created if available Parameters return The iteration in which the test run has been created B 1 1 28 5 getJob public abstract KlarosJob getJob Get the job that initiated the test run if available Parameters return The job that initiated the test run B 1 1 28 6 getNumberErrors public abstract int getNumberErrorsO Get number of test cases with errors of this test run It is assumed that error results have a property type with the value E Parameters return The number of error test cases B 1 1 28 7 getNumberFailures public abstract int getNumberFailures Get number of failed test cases of this test run It is assumed that f
366. t only used to retrieve the data but it can also be used to prepare the data for the report The following listing shows a possible way to prepare the data for a pie chart For every possible result a List object is created then the de verit klaros core model KlarosTestCaseResult retrieved before are stored in one of the lists depending on the test result Next the lists are added to the context List lt KlarosTestCaseResult gt error new ArrayList lt KlarosTestCaseResult gt List lt KlarosTestCaseResult gt failure new ArrayList lt KlarosTestCaseResult gt List lt KlarosTestCaseResult gt success new ArrayList lt KlarosTestCaseResult gt Iterate over the results and retrieve the status Iterator lt KlarosTestCaseResult gt iter Iterator lt KlarosTestCaseResult gt tcr iterator while iter hasNext KlarosTestCaseResult result iter next if result isError error add result else if result isFailure failure add result else if result isPassed success add result i context add error error context add failure failure context add success success The de verit klaros core model KlarosTestCaseResult are split into three lists depending on the test case result These lists can then be accessed from the context by their corresponding key 11 3 3 2 Pie Chart Template Script The following snippet shows how to display the data that was prepared by the Groovy script before
367. t the requirements and the latest results of these executions Coverage The percentage of the test cases which cover the require ment which have been executed in this iteration Compliance For the test cases executed in the Coverage metric the per centage which were last executed with the result Passed 6 2 3 2 4 Results The result tab is further divided into a Test Runs Test Case Results and a Test Suite Results tab showing the test results related to this iteration as described in Section 5 2 14 Related Test Runs and Results 6 2 3 2 5 Bookmarking Iterations Iterations may be linked to from outside of Klaros Testmanagement using the link on the bookmark icon Right click the icon and choose Copy Link Location Firefox Chrome or the equivalent option 6 3 Requirements Ca edition y Feature only available in Klaros Testmanagement Enterprise Edition Requirements are conditions which must be met in order for the product to be considered ready to be shipped The Requirements section allows management of the requirements in the selected project Requirements may be linked to test cases This enables users to quickly check the status of a given requirement Requirements may be created removed updated and assigned to categories on this page Figure 6 13 The displayed requirements may be filtered and sorted as described in Sec tion 5 2 5 Filtering and Sorting 79 Define Plan TF Execute qa Evaluate
368. tCategoryTrees Set lt KlarosSUTImplementationCategoryTree gt B 1 1 36 KlarosEnumValue 281 Model API Reference A Custom property enumeration value B 1 1 36 1 Synopsis public final class KlarosEnumValue extends KlarosWrapper lt KlarosEnumValue EnumValue gt implements IKlarosEnumValue Public Methods public String getValueO Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait l KlarosEnum Value getValue String B 1 1 37 KlarosExternalImplementation This class encapsulates external implementation data of a test case B 1 1 37 1 Synopsis public final class KlarosExternalImplementation extends KlarosWrapper lt KlarosExternalImplementation ExternalImplementation gt implements IKlarosExternalimplementation Public Methods public KlarosTestCase getImplementationOf public String getReference Methods inherited from de verit klaros core model KlarosWrapper getWrapped 282 Model API Reference Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait KlarosExternallmplementation getImplementationOf KlarosTest Case getReference String B 1 1 38 KlarosIssue This class provides access to the information stored for detected issues B 1 1 38 1 Synopsis public final class
369. tMimeTypeQ public abstract String getNameO public abstract long getSizeQ public abstract String getUuid public abstract String getVersion B 1 1 1 2 getMimeType public abstract String getMimeTypeQ Gets the mime type of the attachment Parameters return the mime type B 1 1 1 3 getName public abstract String getName Gets the name of the attachment Parameters return the name 216 Model API Reference B 1 1 1 4 getSize public abstract long getSize Gets the size in bytes of this attachment Parameters return the size B 1 1 1 5 getUuid public abstract String getUuidO Get the unique id of this attachment This may be resolved by calling KlarosContext getAt tachmentURL to an URL pointing to the attachment data Parameters return The uuid of this attachment B 1 1 1 6 getVersion public abstract String getVersion Gets the version of this attachment Parameters return the version B 1 1 2 IKlarosCategoryNode A Klaros Category Node B 1 1 2 1 Synopsis public interface IKlarosCategoryNode lt I T W P gt Public Methods public abstract T getCategoryTree public abstract String getDescription public abstract W getParentO public abstract List lt I gt getReferences public abstract String getShortnameO public abstract List lt W gt getSubCategories 217 Model API Reference B 1 1 2 2 getCategoryTree public abstract T getCategoryTreeQ
370. tainer gt C 10 lt externalld gt The external id of this test case Reserved for future use This element may occur inside the following elements lt testcase gt C 11 lt externalRevision gt The external revision of this test case Reserved for future use This element may occur inside the following elements lt testcase gt C 12 lt trigger gt The externally initiated trigger for this test case Reserved for future use This element may occur inside the following elements lt triggers gt 347 Test Case Import File Specification C 13 lt areatopic gt The category of requirements that is covered by the test case FUNCTIONAL 100 tc functional NON FUNCTIONAL 200 tc non functional STRUCTURAL 300 tc structure REGRESSION 400 tc regression RE TEST This element may occur inside the following elements lt testcase gt C 14 lt depends gt The string describing the dependencies of this test case This element may occur inside the following elements lt testcase gt C 15 lt description gt The textual description of the test case This element may occur inside the following elements lt step gt lt testcase gt C 16 lt docbase gt A reference to the document this test case is based on which may e g contain the require ments this test case is related to This element may occur inside the following elements lt tes
371. tallation 25 Installation 3 3 8 Step 8 Perform External Processes The optional eighth step performs external processes such as setting the environment vari ables and starting the Tomcat service In case none of the flags Launch Application Server and Launch Browser are checked this panel will be skipped ser Y klaros Processing 4 4 fileserver tmp tempinstaller CMD EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet UNC Pfade werden nicht unterstOtzt fileserver tmp tempinstaller CMD EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet UNC Pfade werden nicht unterstOtzt Stattdessen wird das Windows Verzeichnis als aktuelles Verzeichnis gesetzt fileserver tmp tempinstaller CMD EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet UNC Pfade werden nicht unterstOtzt Stattdessen wird das Windows Verzeichnis als aktuelles Verzeichnis gesetzt Using CATALINA BASE C Users qidley Klaros Testmanagement Using CATALINA HOME Users qidley Klaros Testmanagement Using CATALINA TMPDIR Users gidley Klaros Testmanagement temp Using JRE_HOME Program Files Java jdk1 8 0 25 Using CLASSPATH Users qidley klaros resources C Users qidley Klaros Made with IzPack http izpack org Figure 3 9 Perform External Processes Screen The installation may be aborted by clicking the Quit button Clicking Next proceeds with t
372. tcase gt C 17 lt evaluation gt The evaluation method of this test case This element may occur inside the following elements lt testcase gt C 18 lt execution gt The execution type of this test case manual or automated This element may occur inside the following elements lt testcase gt C 19 lt expectedResult gt The expected result of this test This element may occur inside the following elements lt step gt lt testcase gt C 20 lt level gt The level of this test case This element may occur inside the following elements lt testcase gt 348 Test Case Import File Specification C 21 lt method gt The test design view on the system under test This element may occur inside the following elements lt testcase gt C 22 lt note gt A free text short note for this test case This element may occur inside the following elements lt testcase gt C 23 lt postcondition gt The postcondition for this test case This element may occur inside the following elements lt step gt lt testcase gt C 24 lt precondition gt The precondition for this test case This element may occur inside the following elements lt step gt lt testcase gt C 25 lt revision gt The revision of this test case This field is used only for exporting test cases imported test cases always have the fixed revision ID 1 0 This element may occur inside th
373. te E Configure Test GPS Trackng L Report Templates Overview Server Server Uptime 00 07 22 Users Processors 2 Threads TE Mobile Devices System Load n a Integration Name Windows 8 Language de Backup Version 6 2 Country DE Architecture x86 Time Zone Europe Berlin Version 1 7 0_45 Heap 53 Other 46 Vendor Oracle Corporation Used 265 MB Used 73 MB Home C Program Files x86 Uava jdk1 7 0_45 jre Maximum 494 MB R Maximum 160 MB Runtime Name Java TM SE Runtime Environment Runtime Version 1 7 0 45 b18 VM Name Java HotSpot TM Client VM VM Version 24 45 b08 Flush License R License Mobile Edition licensed to Fabian Klaffke verit Informationssysteme GmbH mobile Server ID GAYD AMBQ GAYD AMBQ GAYD AMDFGA edition j Support Expiration Date Dec 31 2015 Z 771 821 Days left Install License Figure 10 1 The Overview Page 10 2 Report Templates enterprise 7 edition j Feature only available in Klaros Testmanagement Enterprise Edition On the Report Templates pages it is possible to create edit delete and generate user defined reports Clicking the B icon starts the creation of the corresponding report in the PDF format Likewise the will start the creation of the report in Excel format Define Plan X Execute fm Evaluate gt e Issue Management System Integration tq L Report Templates soso Name Revision Description Changed
374. tegoryNode gt getCategories Gets the categories this test environment belongs to Each category node will belong to a different category tree Parameters return the category nodes B 1 1 26 4 getIterations public abstract Set lt KlarosIteration gt getIterations Get the iterations this test environment is assigned to Parameters return Set of iterations this test environment is assigned to B 1 1 26 5 getTestRuns public abstract Set lt KlarosTestRun gt getTestRuns Gets the test runs associated with this test environment Parameters return Collection of test runs executed in the environment B 1 1 27 IKlarosTestExecutable This class provides access to a test executable This may wrap a test case or a test suite B 1 1 27 1 Synopsis public interface IKlarosTestExecutable B 1 1 28 IKlarosTestRun 268 Model API Reference This interface provides access to data of a test run B 1 1 28 1 Synopsis public interface IKlarosTestRun Public Methods public abstract KlarosConfiguration getConfiguration public abstract KlarosTestEnvironment getEnvO public abstract KlarosIteration getIteration public abstract KlarosJob getJob public abstract int getNumberErrors public abstract int getNumberFailuresO public abstract int getNumberPassed public abstract int getNumberSkippedO public abstract String getRelatedSummaryQ public abstract Set lt KlarosTestCaseResul
375. tep Results esec eee eee 150 9 25 The Test Case results Print STEN HR 151 926 Tre LOCATION Ts 152 9 27 INe Test Suite Results STEEN Le oe Be EG De 152 9 28 The Test Sulte Results STEEN ANS 153 9 29 The Test Suite Results Screen Test Results sisie eee 153 9 30 The Test Suite Results Screen Print Test Results sesse see see se ee de ee de 154 9 31 The Issues Dy Test Case Screeh ss RE EE NE AE GE EG a Ee EG 155 9 32 Tie Create Issue Page Se OR ee Ge se eg 155 9 33 The Issues by Test Case Details Screen esec esec eee 157 xiii Klaros Testmanagement User Manual 9 34 Tlie Test Case Selection STEN ve 158 9 35 TRE Link ISSUES SEN Nene 158 9 36 Tne Test Case Results Screen Lasse 159 10 1 TNE verview Pad ees De Ge es Ee DE de EE Ge Ee ee RE ie ER Ge 160 10 2 User Defined Report Template Page css esec sese eee eee 160 10 3 Generate a parameterized Report iss esse es ee Ee Gra Haa dide a Ta 161 10 4 Report Details vred 162 10 35 The Maintain Users Pearse 163 10 6 The Save New User Dialog css ese RR diia 163 10 2 The Edit USE STEEN ee 165 VJ Pioecd Roles Tab as EE ii cs 165 10 9 Tie Poet Roles TaD ua 166 10 10 The Mobile Device Connection Log Tab esse sees cce eee eee 166 10 11 The MODIG Devices Pads alii rte occ 167 10 12 The Mobile Devices Details Page sessies se see Ne ee Ge Ee Ek AG ee be ee Se ee 168 10 13 The Mobile Device Results Tab esec sesse se se Se Ne AE Ge AG ek AG ee Ak Ee de 168
376. terationCategoryTree KlaroslterationCategoryNode lterationCategoryNode gt A KlaroslterationCategoryTree B 1 1 42 Klarosjob This class provides access to the information stored for jobs B 1 1 42 1 Synopsis public final class KlarosJob extends KlarosNamedEntity lt KlarosJob Job gt implements IKlarosJob Comparable lt KlarosJob gt Public Methods public int compareTo KlarosJob o public boolean eguals Object o 287 public public public public public public public public public public public public public public public public public public public public public public public Model API Reference Set lt KlarosAttachment gt getAttachmentsO KlarosConfiguration getConfiguration String getDescriptionO Date getDueDate KlarosTestEnvironment getEnvO String getEstimatedTime Long getEstimatedTimeInMilliseconds JobPriority getJobPriorityO JobStatus getJobStatus JobType getJobTypeQ KlarosJob getParentO Integer getProgress Date getStartDate List lt KlarosJob gt getSubJobs Integer getSuccessRate String getSummary KlarosSUTImplementation getSutO KlarosTestCase getTestCase Set lt KlarosTestRun gt getTestRuns KlarosTestSuite getTestSuiteQO List lt KlarosJobUpdateAction gt getUpdateAction List lt KlarosJobTimeBlock gt getWork int hashCodeO Methods inherited from de verit klaros core model KlarosNamedEntity getAssignee getPro
377. ternal id of this requirement the format of this string can be chosen deliberately This element is ignored for import operations and will only be used during synchronization Changing this id for subsequent synchronization attempts will result in the creation of ad ditional requirements Else the data in the requirement will be overwritten with the data provided This element may occur inside the following elements lt requirement gt D 8 lt externalRevision gt The external revision of this requirement the format of this string can be chosen deliber ately This element is ignored for import operations and will only be used during synchro nization Changing this revision for subsequent synchronization attempts may result in the creation of an additional revision of the requirement if the revision is yet unknown Else the data in the requirement will be overwritten with the data provided This element may occur inside the following elements lt requirement gt D 9 lt trigger gt The externally initiated trigger for this requirement Reserved for future use This element may occur inside the following elements lt triggers gt 353 Requirement Import File Specification D 10 lt description gt The description of this requirement This element may occur inside the following elements lt requirement gt D 11 lt priority gt The priority of this requirement This element may occur inside the following ele
378. ters return the job B 1 1 11 9 getTestRun public abstract KlarosTestRun getTestRun Gets the test run this job time block belongs to Parameters return the test run B 1 1 12 IKlarosjobUpdateAction This interface provides access to the job update action B 1 1 12 1 Synopsis public interface IKlarosJobUpdateAction Public Methods public abstract String getChanges public abstract String getDescription 235 Model API Reference B 1 1 12 2 getChanges public abstract String getChangesO Gets the changes Parameters return the changes B 1 1 12 3 getDescription public abstract String getDescriptionO Gets the description Parameters return the description B 1 1 13 IKlarosLabeledObject This interface provides access to the fields of a labeled object B 1 1 13 1 Synopsis public interface IKlarosLabeledObject Public Methods public abstract Iterable lt gt asIterableQ public abstract Date getCreated public abstract KlarosUser getCreator public abstract UUID getKey public abstract KlarosUser getLastEditorO public abstract Date getLastUpdated public abstract String getNameO public abstract boolean isEnabled 236 Model API Reference B 1 1 13 2 asIterable public abstract Iterable lt gt asIterableQ Return this object as an iterable containing just this object Parameters return the iterable container B 1 1 13 3 getKey
379. th this mobile device and also the time at which the synchronization took place Clicking the user name displays the user details page for this user Mobile devices may be viewed on a printer friendly page as described in Section 5 2 6 Print Pages 167 Configure 10 4 1 Mobile Device Details E Define 9 Plan X Execute fm Evaluate y 2 WebApp gt A E xT1032 68 2 Back Overview Report Templates Properties Results Connection Log Changes Users Device Name XT1032 Device Id 730248fe b3c3 4ae5 8278 593076e4fc18 System Mobile Phone Id 359307054927468 Integration Android Version 442 Hardware Serial qcom Backup Manufacturer motorola Failed Logins 0 Consecutive failed Logins 0 Last Access 6 16 2014 Last User tester Comment Activated Y Blocked O Created by Erika Mustermann on 6 16 14 10 58 AM Last changed by Erika Mustermann on 6 16 14 11 05 AM Figure 10 12 The Mobile Devices Details Page Clicking either the id of the mobile device or the details symbol on the rightmost column opens the mobile device details page This page contains all of the details of the mobile device like the installed Android version and the unique device id An administrator can check the Activated checkbox to activate or deactivate the device and the Blocked checkbox to block or unblock it The Results tab displays the results of all test runs that have been executed on this mobile device E E
380. the installation finishes in GUI mode including the optional creation of automatic installation scripts You can create such a script by installing Klaros Testmanagement on a server with a GUI and modifying the script to fit your needs Automatic installation scripts will work for unattended installations in console mode as well Generate an automatic installation script 31 Installation Enter Y for Yes N for No N Installation was successful application installed on opt klaros testmanagement L Writing the uninstaller data Console installation done After the installation has finished you can find the installation of Klaros Testmanagement in the folder opt klaros testmanagement See Section 3 10 Installing Klaros Testmanagement as a Service for details on how to configure Klaros Testmanagement to run as a service 3 5 Automated Installation Script If you ve previously installed Klaros Testmanagement and chose to save an automated in stallation script you can install Klaros Testmanagement again with the same parameters using one of the following commands This example assumes the automated installation script was saved as auto install xml Linux java jar Klaros Setup jar console auto install xml Windows Klaros Setup exe auto install xml In case you cannot run the Klaros Testmanagement installer on a system with graphical user interface you can build an automated installation script and run an unattended
381. the machine it is installed on Depending on the operating system different measures have to be taken to achieve this 3 10 1 Installing Klaros Testmanagement as a Linux service To start Klaros Testmanagement automatically the startup script shown below should be saved to the etc init d directory as klaros and selected for the appropriate run level Please refer to the documentation of your linux distribution for details The values of the KLAROS USER and KLAROS PATH fields must first be replaced with the intended user id and installation path It is important that the script is executable This can be ensured with the command chmod a x klaros bin bash This will be ignored by systems that don t use chkconfig chkconfig 345 98 2 description klaros inside Tomcat a servlet container KLAROS_USER klarosdemo KLAROS_PATH opt klaros testmanagement bin su KLAROS_USER c KLAROS_PATH bin catalina sh gt var tmp klaros log 2 gt amp 1 3 10 2 Installing Klaros Testmanagement as a Windows service Under the Windows operating system family the supplied service bat script can be used to install the Tomcat application server as a Windows service Please refer to the official Apache Tomcat 8 Windows service HOW TO for further details 39 Installation Change the Service User Account Per default the created Windows service will use the LocalSystem account to run the Klaros Testmanagement a
382. the map The position of the marker on the map corresponds to the coordinates that have been tracked when the user entered the test case step result on his mobile device Clicking on one of the markers opens up a popup with details about the test case step result Only available in Klaros Testmanagement Mobile Edition like the verdict or the description the user has entered 151 Evaluate Plan po Execute pm Evaluate X Configure Test GPS Tracking SE A N Test Case Result TCR0000002 TC00003 Testing the GPS Device A E Dashboard Report Templates o Properties Location Changes Test Run History iQ C o Mes o Test Case Results p 1 ed mx Step 5 Test Suite Results f Darmstadt 9 Result Failure p Issues N x Date 10 22 13 6 43 42 PM din E GA Summary Testfailed R K Description The GPS system displayed the wrong dA E AE coordinates j Coordinates 49 6981323 8 05182 RHINELAND PALATINATE RHEINLAND PFALZ v at re y e Obermoschel j o A i L ar Oberstein Meisenheim Gian Osthofe m KE L lt po ig o o 7 ML L f j y x F hheimbolanden gy 9 ON nr 4 Lauterecken l L 425 yp 70 L EA E Y RAR Birstadt N Heppenheim O _Rockenhausen WE OR s 4 F Baumholder z 5 e TT Ai E Vo os N Lampertheil Koss JE C jo Hemsbach Mida Lad C N j o J T N oSrUnstadt je a Wei i X f Tank
383. the selected test case The result of the test cases run is shown using the following icons amp the test finished successfully 3 a failure of the system under test has been detected an error occured during the test execution e the test result could not be determined In addition the ID of each test case result is colored green for passed orange for failed red for error or gray for skipped 148 Evaluate If the icon appears in the ID column this means that the corresponding test case result has been manually changed by a user Clicking the icon starts a retest of the test case To get a better overview of the test case results the sorting and filtering functionality of the Filter Sort panel can be used as described in Section 5 2 5 Filtering and Sorting 9 5 1 1 Navigating back to the Overview Page Clicking the Back button brings the user back to the test case results screen Figure 9 20 where they may choose another test case Clicking on the Gi icon opens up the test case result details screen for the corresponding test case result Figure 9 23 9 5 1 2 The Test Case Results Details Screen O A Define Plan LS Execute EI Evaluate Configure Issue Management System Integration k amp Test Case Result TCR0000009 TC00001 Testing the file upload of the ticket system iD E Dashboard Report Templates Properties Changes Test Run History R Summary The Issue cannot be cr
384. thods inherited from de verit klaros core model KlarosLabeledObject asIterable getCreated getCreator getKey getLastEditor getLastUpdated getName isEnabled Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait 317 Model API Reference S Sextends LabeledObject TE S Sextends Revision KlarosRevision lt KlarosTestSuite Testoulte gt k mm mm m EE EE mm EE EE MEE EE MEE EE m m EE EE MEE EE m m EE MEE EE EE m m m EE EE m m m ma KlarosTestSuite getConfiguration KlarosConfiguration getResults List lt KlarosTestSuiteResult gt getShortname String getSut KlarosSUTImplementation getTestCases List lt KlarosTestCase gt getTestSuiteResultCount Integer getTrunkRoot KlarosTestSuite getRoot KlarosTestSuite getSuccessor KlarosTestSuite getPredecessor KlarosTestSuite getBranches Set lt KlarosRevision lt KlarosTestSuite TestSuite gt gt getBranchRoot KlarosTestSuite getCategories Set lt KlarosTestSuiteCategoryNode gt getAttachments Set lt KlarosAttachment gt S a S B 1 1 70 KlarosTestSuiteCategoryNode A category node for test suites B 1 1 70 1 Synopsis public final class KlarosTestSuiteCategoryNode extends KlarosCategoryNode lt KlarosTestSuite KlarosTestSuiteCategoryTree KlarosTestS
385. tinue X to exit Additional information can be found at http www klaros testmanagement com verit Informationssysteme GmbH 67657 Kaiserslautern Europaallee 10 Germany Web http www verit de E Mail support verit de Phone 49 631 520 840 00 Fax 49 631 520 840 Q1 Press 1 to continue 2 to quit 3 to redisplay 1 3 4 3 Step 3 Licensing Agreements lU The License Panel Section 3 3 3 Step 3 Licensing Agreements can be paged with a rep etition of Enter Commit with 1 Enter Limited Use Software License Agreement PLEASE READ THIS AGREEMENT CAREFULLY BEFORE ATTEMPTING TO USE THE SOFTWARE OF verit Informationssysteme GmbH AND RELATED DOCUMENTATION COLLECTIVELY THE SOFTWARE AND BEFORE INSTALLING OR USING THE SOFTWARE BY INSTALLING OR USING THE SOFTWARE YOU ARE CONSENTING TO BE BOUND BY THIS AGREEMENT limitations may not apply to you You may also have other rights 29 Installation that vary from state to state Press 1 to accept 2 to reject 3 to redisplay 1 3 4 4 Step 4 Target Path The Target Path Panel Section 3 3 4 Step 4 Target Path looks like this with the console installer Select target path opt klaros testmanagement You can press Enter to accept the proposed path or type another The path will be created if it did not already exist If the directory already exists a warning is displayed and you can cancel the installation or continue 3 4 5 Step 5 Se
386. tion Created by John Doe on 1 8 14 10 59 AM Properties User Defined Steps Created by John Doe on 1 8 14 10 59 48 AM Functional Overview 1 0 TC00007 Test the new ordering process aE Revisions Results Changes Changes THhe ordering process has been revised and needs to be testsed thoroughly Acceptance Test You are logged in at one of the terminals Changes THe ordering proces has been revised and needs to be tests thoroughly Changes Re Testing of the new ordering process Changes Re Testing of the new ordering process Changes Testing the new ordering process Changes List changed Changes High Changes Manual Last changed by John Doe on 1 8 14 11 07 AM Back Figure 5 26 The Test Case Changes Tab Changes to an object are grouped by edit i e if a user changes two fields and then presses save the changes to these to fields will be grouped in the Changes tab 5 2 16 Overview Tabs enterprise 7 edition i Feature only available in Klaros Testmanagement Enterprise Edition For every type of artifact in Klaros Testmanagement there is a dedicated overview tab which shows the most important data for this artifact like the last editor or the the status at a glance In addition to raw data many overview pages are enriched with various useful sta tistics like for example the success history for test suites which helps visualizing the test progress 66 Functional Ove
387. tion public abstract String getPostconditionO Get the postcondition Parameters return The postcondition of this test case step B 1 1 25 7 getPrecondition public abstract String getPrecondition Get the precondition Parameters return The precondition of this test case step B 1 1 25 8 getSummary public abstract String getSummary Get the test result summary This is usually set for failed error status results Parameters return The test result summary B 1 1 25 9 getTestCase public abstract KlarosTestCase getTestCase 265 Model API Reference Get test case Parameters return The test case that has been executed to get this result B 1 1 25 10 getTestCaseResult public abstract KlarosTestCaseResult getTestCaseResult Get test case result Parameters return The test case result that has been executed to get this re sult B 1 1 25 11 getTestRun public abstract KlarosTestRun getTestRun Get test run Parameters return The test run that created this result B 1 1 25 12 isError public abstract boolean isError Check if this is an error result It is assumed that error results have a property type with the value E or error Parameters return true if this results represents an error B 1 1 25 13 isFailure public abstract boolean isFailureO Check if this is a failure result It is assumed that failure results have a property type with the v
388. tion of issues found while execut ing a test Import Interfaces for Test Cas es Import Interface for Test Au tomation Backup and Restore Key Features Test case definitions can be imported in well defined XML and Excel formats Test results from test automation software e g JUnit can be easily imported and added to the manual test results Supported test automation software includes AUnit Boost Test Check CppTest CopUnit ctest CUnit Free Pascal Unit Jubula GUIDancer JUnit MbUnit MSTest NUnit PHPUnit QF Test QTestLib Ranorex Selenium TestComplete TestNG TUSAR UnitTest Valgrind and xUnit net Complete test projects can be backed up and restored The restore interface can also be used to import foreign data from XML files 1 2 Klaros Testmanagement Enterprise Edition Features enterprise edition pr Additional features of Klaros Testmanagement Enterprise Edition Project based role manage ment Agile Test Management Scrum Requirement Management Test Coverage Assigning and Management of Jobs Evaluation of the User Work load Measure Success Rate and Progress Categorization Change history User Defined Custom Fields A user can be assigned to a different role in each project allowing to individually limit rights and access to informa tion Iterative development processes are supported by using test cycles to coincide with development cycles sprints Col
389. tmanagement Select Installation Packages Step 5 of 10 Select the packs you want to install Note Grayed packs are required El Tomcat 8 Application Server 1J Klaros Testmanagement 4 3 2 SNAPSHOT PDF Documentation Description The Tomcat 8 0 23 Web Application Server Total space required 188 87 MB Available space 34 45 GB Figure 3 5 Select Installation Packages Screen 23 Installation The installation may be aborted by clicking the Quit button Clicking Previous goes back to the Target Path dialog clicking Next proceeds with the installation 3 3 6 Step 6 User Data In the sixth step the Tomcat server settings can be changed F 1 IzPack Installation von User Data dl S klaros Tomcat Server Settings server Port HTTP Part 18080 AJP 1 3 Port 18009 session Timeout 60 The minimum and maximum amount of memory available to the Tomcat process Minimum MB 256 Maximum MB 768 The username and the password of the administrator account for managing the Tomcat server Username admin Password Retype Password Launch Application Server Launch Browser Made with lzPack http lizpack org Figure 3 6 User Data Screen It is possible to set the ports used by Tomcat Server Port HTTP Port and AJP 1 3 Port the minimum and maximum amount of memory available to the Tomcat process as well as the user name and password of the Tomcat application server administrator I
390. to upload your data from the command line or other applications The following example shows how to import an XML file containing test cases into the project named P00001 using the curl command line application Curl should be available in every decent Linux distribution and as part of the Cygwin http www cygwin com distribution or as a command line tool from http curl haxx se download html for the Microsoft Windows operating system family 199 Import Export curl v T TestCases xml lt klaros app url gt seam resource rest import testcase xml config P00001 Example 12 3 XML Test Case Import via Command Line If the Klaros Testmanagement installation requires authentication for importing test cases username and password arguments have to be appended to the curl call curl v T TestCases xml lt klaros app url gt seam resource rest import testcase xml config P00001 amp username user amp password secret Example 12 4 XML Test Case Import via Command Line with authentication 00000000 Note Eal All artifacts which are referenced during import like projects or test cases con tain five digits in their id For example P00001 is a valid Project id while P01 and P001 are not 12 3 Importing Requirements from Excel Klaros Testmanagement allows importing of requirements from Excel sheets structured in a predefined format which will be further detailed in Section 12 3 1 Import Format In addition to th
391. trator or Manager Not changed by project role Table A 1 Role Permission Overview Table Klaros Testmanagement Community Edition Adminis trator Manager Tester Configure dashboard Execute jobs Export Excel tables Generate custom reports Generic full text search Create and assign jobs Create Custom Reports Define custom fields E gt QU A no N O ct M U N Cr A O am 3 N D gt lt D N CT O Configure LDAP authentication Not changed by project role Table A 2 Role Permission Overview Table Klaros Testmanagement Enterprise Edition Manager Tester wd p M i a Adminis trator Actions Roles Execute jobs in the App View jobs in the App q ExecutejobsintheApp 100 2 pU K 214 Role Permission Overview Actions Roles Adminis Manager Tester trator Enable Disable mobile devices for the N Klaros Testmanagement instance a o View mobile devices for the Klaros Testman m m agement instance s a aNot changed by project role Table A 3 Role Permission Overview Table Klaros Testmanagement Mobile Edition 215 Appendix B Model API Reference B 1 API Reference B 1 1 de verit klaros core model B 1 1 1 IKlarosAttachment This interface provides access to a binary attachment B 1 1 1 1 Synopsis public interface IKlarosAttachment Public Methods public abstract String ge
392. ts hl SSUES Administration Project Project Playground Projects J yg Project Categories Me Users Groups amp Roles Mees The playground project for Klaros regression testing User Browser Keyt PLAYGROUVND Group Browser URL No OF Project Role Browser Project Team Project Lead Jenkins Build System Default Assignee Project Lead Attachments Project Roles View members Issue Type Scheme Default Issue Type Scheme Select Edit Manage Notification Scheme None i Select Global Settings Bamboo Servers CVS Modules Permission Scheme Default Permission Scheme Select Edit System Dashboard Issue Security Scheme Mone Select Events Field Configuration Scheme system Default Field Configuration Issue Type Screen Scheme Default Issue Type Screen Scheme Select Edit Figure 10 23 The JIRA Project ID Mantis Project ID The Mantis Project ID consists of the Project Name field value as shown below Logged in as admin Mantis Administrator administrator 2011 05 27 10 20 CEST Main My View View Issues Report Issue Change Log Roadmap Summary Docs L Manage Users Manage Projects Manage Custom Fields Man Playground development Y Edit Project Project Name Status Figure 10 24 The Mantis Project ID Redmine Project ID The Redmine Project ID consists of the Identifier field value as shown below 177 Configure Home My page Projects Administration
393. ts associated with this test suite Parameters return the attachments B 1 1 29 3 getCategories public abstract Set lt KlarosTestSuiteCategoryNode gt getCategories Gets the categories this object belongs to Each category node will belong to a different category tree 273 Model API Reference Parameters return the category nodes B 1 1 29 4 getConfiguration public abstract KlarosConfiguration getConfiguration Get configuration Parameters return The related configuration B 1 1 29 5 getResults public abstract List lt KlarosTestSuiteResult gt getResults Get test suite results Parameters return Set of results of executions of this test suite B 1 1 29 6 getShortname public abstract String getShortname Get the short name of the test suite Parameters return String of the description of the test suite B 1 1 29 7 getSut public abstract KlarosSUTImplementation getSut Get the description of the test suite Parameters return String of the description of the test suite B 1 1 29 8 getTestCases public abstract List lt KlarosTestCase gt getTestCases Get the executables of this test suite Parameters return Set of test cases of this test suite B 1 1 29 9 getTestSuiteResultCount public abstract Integer getlestSuiteResultCountO Return the number of test suite results in this test suite 274 Model API Reference Parameters return The number of test suit
394. tter performance After running the initial installation process the database can be changed see Section 3 9 Changing the Default Database This chapter provides all information necessary to install Klaros Testmanagement 3 1 License Model 3 1 1 License Model Users Depending on the version of Klaros Testmanagement in use a different user license model is applied Since the Klaros Testmanagement Community Edition has a smaller number of features in comparison to the other editions it supports an unlimited amount of users that can work in parallel The Klaros Testmanagement Enterprise Edition follows another license model Each Klaros Testmanagement Enterprise Edition license is bound to a set number of licensed users This number dictates how many users can be active at any single point in time If a user is to be created which would excess the number of licensed users this user immediately gets deactivated thereafter The user can later be re activated if another active user gets deactivated first 3 1 2 License Model Mobile Devices The Klaros Testmanagement Mobile Edition license is tied to a set number of mobile devices If a mobile device connects to Klaros Testmanagement for the first time and if there are no free mobile device slots available then the mobile device gets deactivated It can later be activated again if an administrator deactivates another mobile device first r Important If a user or mobile d
395. ttp devverit de 3200 D a New Figure 10 21 The Issue Management Tab The issue management systems sections shows all of the configured systems in a single table The properties of each entry can be changed directly in the table The properties of the issue management system are ID The internal id of the issue management system This property is assigned automatically and cannot be altered by the user Info If the deletion of an issue management system is prohibited since there are test case results assigned to issues in the issue management system the info column shows a amp icon To enable background synchronisation of issues it is required that creden tials are configured for the issue management system via the icon If credentials are not yet available a icon is shown System The system column indicates which issue management system is used Cur rently Klaros Testmanagement supports JIRA Trac Mantis Redmine and Bugzilla 175 Configure Project If the issue management system organizes Issues in projects it is possible to specify the project id where the new Issues should be created in the sys tem JIRA Redmine Mantis and Bugzilla manages their issues in different projects For Trac the URL is used to specify different projects Description In the Description field a description of the issue management system can be entered URL In the URL field the link to the issue management system is specified To
396. uite result if it did not yet exist Only Administrators can create Users If checked only administrators can create users If unchecked managers can also create Users s Testers may only execute tests via a related job If checked users in the role of Tester may only execute tests by executing a Job s Testers may only resume jobs assigned to them If checked users in the role of Tester may only resume executions of Jobs which are as signed to them 10 5 2 Notification Settings Notifications will be sent by the system via email for various events like creating a user ac count or assigning a job This section allows to configure the conditions under which these notification emails will be sent Sets of notifications can be defined in a notification scheme and reused for various projects If a notification scheme is declared as the default notification scheme it will automatically be assigned to every existing project unless a different scheme is defined for this project Figure 10 16 shows the notification scheme definition tab A Email Configuration required For notifications to work properly it is required to both configure the email serv er settings as described in Section 10 6 2 E Mail and make sure that all user accounts contain a valid email address 170 Configure System Overview Miscellaneous Notifications Interface Languages Report Templates WA gt Notification schemes ID
397. uiteCategoryNode TestSuiteCategoryNode gt Public Constructors public KlarosTestSuiteCategoryNode TestSuiteCategoryNode wrapped Public Methods public List lt KlarosTestSuite gt getReferences 318 Model API Reference Methods inherited from de verit klaros core model KlarosCategoryNode getCatego ryTree getDescription getParent getShortname getSubCategories Methods inherited from de verit klaros core model KlarosWrapper getWrapped Methods inherited from java lang Object equals getClass hashCode notify notifyAll toString wait l m T W W extends KlarosCategoryNode lt l T W P gt I P Pextends CategoryNode L KlarosCategoryNode lt KlarosTestSuite KlarosTestSuiteCategoryTree KlarosTestSuiteCategoryNode TestSuiteCategoryNode gt P A KlarosTestSuiteCategoryNode KlarosTestSuiteCategoryNode wrapped TestSuiteCategoryNode getReferences List lt KlarosTestSuite gt B 1 1 70 2 KlarosTestSuiteCategoryNode TestSuiteCategoryNode public KlarosTestSuiteCategoryNode TestSuiteCategoryNode wrapped Instantiates a new klaros test suite category node Parameters wrapped the wrapped class B 1 1 71 KlarosTestSuiteCategoryTree A category node for test suites B 1 1 71 1 Synopsis public final class KlarosTestSuiteCategoryTree extends KlarosCategoryTree lt KlarosTestSuite KlarosTestSuiteCategoryTree TestSuiteCategoryTree KlarosTestSuiteCategoryNode TestSuiteCat
398. unReport execute context KlarosContext void add Result verdict String testResult KlarosTestCaseResult resultMap Map lt String List lt KlarosTestCaseResult gt gt void getColor index int String getDate d Date String getDateOnly d long String getConverter testrun Set lt gt List lt gt getTestCaseStepResult result KlarosTestCaseStep Result String getTestCaseResult result KlarosTestCaseResult String getTestCaseStepError result KlarosTestCaseStepResult int getTestCaseError result KlarosTestCaseResult int getSortTestRuns testRuns List lt gt context KlarosContext List lt gt i B 2 3 3 2 addResult String KlarosTestCaseResult Map lt String List lt KlarosTestCaseResult gt gt public void addResult String verdict 334 Model API Reference KlarosTestCaseResult testResult Map lt String List lt KlarosTestCaseResult gt gt resultMap Adds the result to the results map Parameters verdict the verdict of the result testResult the test result resultMap the result map B 2 3 3 3 getColor int public final String getColordint index Gets the color Parameters index the index return the color B 2 3 3 4 getConverter Set lt gt public final List lt gt getConverter Set lt gt testrun Gets the converter Parameters testrun the Test Run return the converter B 2 3 3 5 getDate Date public final String getDate Date d
399. ust be accessible from Seam This can either be achieved by storing the image in a jar file and storing this file in the klaros resources folder of the user running Klaros Testmanagement or by providing the image on a web server from where it can be included by using HTML code in the report template When storing the image in a jar file it can be easily accessed by the following code snippet lt p image value images image png gt The value attribute defines the image filename and the folder of the image location When providing an image via a web server it can be accessed by the following code snippet lt p html gt lt img src http www verit de images logo klaros 169 png gt lt p html gt In this case the src attribute defines the URL of the image location 11 3 5 Creating a SeamExcel Report Template The code snippets presented in this section show how to build a report template for Klaros Testmanagement For detailed information please refer to SeamExcel man ual More information on the Klaros Testmanagement object model can be found in de verit klaros core model The following snippet shows how to build the frame for the report template Inside this frame all other report details can be described and grouped in chapters and sections lt e workbook xmlns e http jboss org schema seam excel xmlns f http java sun com jsf core xmlns ui http java sun com jsf facelets gt 194 Custom Reports
400. vironment these results should be assigned to The format of the result file is typically detect automatically 0 Execute fF Evaluate X Configure IT TEE N O Import Test Results My Jobs T Afile must be uploaded to continue Run Test Suite Upload Results Continue Test Run Import Test Results Test Environment System under Test lt Produktion 0 2 Staging 0 3 SNAP SHOT Test 0 3 Developer local IDE integriert 0 1 0 1 SNAPSHOT Figure 8 13 Import Results Page Clicking the Next button opens the Assign Test Results to Test Cases page The test case to assign each test result to can be selected using the corresponding drop down box Each result must be assigned to a different test case If no test case is selected here a new test case is automatically created upon import When the option Create additional test suite re sult is selected test suite results are automatically created for the corresponding test suite information contained in the result file This information may vary with the import format Additionally a corresponding test suite is created for the test suite result if it did not yet exist 126 Execute AN 55 Execute ET O Ewo S Z Import Test Results My Jobs External Test Case Name Associated Test Case Run Test Case de verit klaros service issuemanagementtest bugzilla TestBugzilla4xx testGetPriorities Run Test Suite de veritklaros service issuemanagementtest bugzilla TestBug
401. w Link Refresh Created 2 years ago by Devon Manager Last changed 4 months ago by John Doe Back Figure 6 20 The Test Case Issues Screen This tab lists all issues that have been linked to this system under test Pressing the New button opens the Issue Details page Section 9 7 2 Issue Details Creating a new Issue where new issues can be created and linked to this system under test By pressing the Link button it is possible to link existing issues to this system under test Section 9 7 3 Link Issues 6 5 3 5 Results The result tab is further divided into a Test Runs Test Case Results and a Test Suite Results tab showing the test results related to this system under test as described in Section 5 2 14 Related Test Runs and Results 6 5 3 6 Bookmarking Systems under Test edition y Feature only available in Klaros Testmanagement Enterprise Edition Systems under test may be linked to from outside of Klaros Testmanagement using the link on the bookmark icon Right click the icon and choose Copy Link Location Fire fox Chrome or the equivalent option 6 6 Test Cases A test case is a set of input values execution preconditions expected results and execution postconditions developed for a particular objective or test condition in order to determine whether or not an application or software system meets its specifications 91 Define Test cases may be created removed duplicated updat
402. which are listed there Revision only used in export Priority LOW MEDIUM HIGH Table 12 4 General Property Coordinates 12 3 1 2 Custom Properties Requirements may contain an arbitrary number of custom attributes These are listed as name value pairs starting from cell G1 downwards The name in the name column must exactly match the name of general property for a value to be parsed correctly The parsing stops once an empty name cell has been found The value field for enumeration properties must exactly match the name of the enumeration property value definition to be parsed er Table 12 5 User Defined Property Coordinates 12 3 2 Prerequisites To import Excel based requirements the following prerequisites have to be met 1 The file that is going to be imported has to be in xIs format 2 The project that should contain the imported requirements has to be already created 3 If the Authentication required for import flag is set see Section 10 5 1 Miscellaneous Set tings username and password of a system user have to be provided see Section 10 3 3 User Details for more information on system users 4 If custom properties are to be used they have to be defined for the project prior to starting the import process Please note that custom properties are only supported in the Klaros Testmanagement Enterprise Edition 201 Import Export 12 3 3 Execution To import Excel based requireme
403. xt Parameters name the name value the value B 2 2 1 3 executeParameterizedQuery String public abstract List lt gt executeParameterizedQuery String query Execute the given query with the Parameters from the ParameterContext Parameters query The HQL query to execute return A KlarosList of the selected objects B 2 2 1 4 executeQuery String public abstract List lt gt executeQuery String query Execute the given query Parameters query The HQL query to execute 327 Model API Reference return A KlarosList of the selected objects B 2 2 1 5 getActivelteration public abstract KlarosIteration getActivelteration Gets the active iteration Parameters return the active iteration B 2 2 1 6 getActiveProject public abstract KlarosConfiguration getActiveProject Gets the active project Parameters return the active project B 2 2 1 7 getAttachmentUrl String public abstract String getAttachmentUrl String attachmentId Return the attachment url for the given attachment id Parameters attachmentId the attachment id return the attachment url B 2 2 1 8 getAttachmentUrl UUID public abstract String getAttachmentUrlcUUID attachmentId Return the attachment url for the given attachment id Parameters attachmentId the attachment id return the attachment url B 2 2 1 9 getBrowsePageUrl KlarosLabeledObject lt gt public abstract String getBrowsePageUrl KlarosLabeledObject
404. xtends LabeledObject KlarosLabeledObject lt T S gt PE AAA S Sextends Named Entity KlarosNamedEntity lt T S gt E EG i S Sextends Revision KlarosRevision lt KlarosTestCase TestCase gt KlarosTestCase getConfiguration KlarosConfiguration getStateName sut KlarosSUTImplementation String getimplementation KlarosExternallmplementation getDetectedIssues List lt Klaroslssue gt getCovers Set lt KlarosRequirement gt getResults Set lt KlarosTestCaseResult gt getTestCaseSteps List lt KlarosTestCaseStep gt getStates Map lt KlarosSUTImplementation KlarosTestCaseState gt compareTo o KlarosTestCase int equals o Object boolean hashCode int getShortname String getDescription String getPrecondition String getPostcondition String getArea TestAreatopic getExecution TestExecutionMethod getNote String getDesignTechnique TestDesignTechnique getLevel TestLevel getPriority TestPriority getState String getTeam String getVariety TestVariety getDependency String getDocbase String getEvaluation String getTraceability String getTrunkRoot KlarosTestCase getRoot KlarosTestCase getSuccessor KlarosTestCase getPredecessor KlarosTestCase getBranches Set lt KlarosRevision lt KlarosTestCase TestCase gt gt getBranchRoot KlarosTestCase getExpectedResult String getCategories Set lt KlarosTest Case
405. y Configure Swmp a Requirements Projects em 28 BE B Categories Fiter Sort 10 v Iterations ID Revision Hame Priority Action Test Environments RO0011 1 0 Integration Test Project Low N 2 8GS Systems under Test R00010 g 1 0 Continuous Integration Hih S GE Test Cases C Roo009 g 10 Project Setup Hih v 2208 Test Suites RO0008 g 10 Development environment High N 2208 R00007 1 0 User management user reactivation Low v 2208 R00006 1 0 User management user deactivation Low v 2208 R00005 1 0 User management deletion Low vd 2208 R00004 1 0 User management deletion Medium v 2 8 GEB R00003 1 0 Change password Medium v 2 8 GB R00002 1 0 Reject invalid login High vd 22808 ID Revision Name Priority Action 11 Elements found Page 1 of 2 1 2 gt bi 10 w Figure 6 13 The Requirements Screen The Requirements page shows all of the requirements defined for the current project Click ing on the table fields allows direct editing of the attributes The leftmost column allows requirements to be selected for bulk actions The uppermost checkbox is a global select button which selects or deselects all elements shown in the table Please note that the displayed elements are subject to the current search and catagorization criteria Requirements may be viewed on a printer friendly page as described in Section 5
406. y_min value 256 gt lt entry key tomcat_memory_max value 512 gt lt entry key tomcat_admin_name value tcadmin gt lt entry key tomcat admin password value IfYouDontChangeThisDontBlameMe gt lt entry key start server flag value false gt 32 Installation lt entry key launch browser flag value false gt lt userInput gt lt com izforge izpack panels userinput UserInputPanel gt lt com izforge izpack panels install InstallPanel id install gt lt com izforge izpack panels process ProcessPanel id process gt lt com izforge izpack panels shortcut ShortcutPanel id shortcuts gt lt createShortcuts gt false lt createShortcuts gt lt com izforge izpack panels shortcut ShortcutPanel gt lt com izforge izpack panels finish FinishPanel id finish gt lt AutomatedInstallation gt Example 3 1 sample auto install xml 3 6 Update Process If Klaros Testmanagement is already installed it is possible to update it to a newer version The installer will update all files automatically Further information of the installation process can be found in Section 3 3 Installation Process The Klaros Testmanagement home folder remains untouched so all settings database connections and the content repository will be unaffected by the update process r Important Klaros Testmanagement must be stopped before starting the update Otherwise the installation process cannot fi
407. ystem that is affected The version of the system that is affected The milestone of the system that is affected A detailed description of the issue Keywords for the issue Issue Management System Summary Issue Type Priority Components Version Milestone Description Keywords text textarea checkbox radio Mandatory fields must be filled Update Test Case State State Figure 8 16 Trac Issue Page IM00003 Trac Server S defect lt blocker Is component Is http localhost S080 klaros webi browse jsp7type testCaseResult amp uuid df7e1a01 2849 47ca a1da c7f 8048cea7 one e so E Save Back The following fields are available for the Redmine issue management system Summary Issue Type Importance Assignee Version Category Description Estimated time hours A short summary of the issue The type of the issue e g a defect or enhancement The priority of the issue The assignee of the issue The version of the system that is affected The category of the system that is affected A detailed description of the Issue The estimated time in hours for completing the issue 129 Figure 8 17 Redmine Issue Page Issue Management System Summary Issue Type Priority Assignee Version Category Description Estimated time hours INT FLOAT TEXT DATE LIST STRING BOOL Mandatory fields must be fill
408. zilla4xx testGetissue Continue Test Run Import Test Results de verit klaros semvice issuemanagementtest buazilla TestBugzilla4xx testGetStatuses de verit klaros service issuemanagement test bugzilla TestBugzilla4xx testUpdatelssue de verit klaros service issuemanagementtest bugzilla TestBugzilla4xx testCreatelssue de verit klaros service issuemanagement test bugzilla TestBugzilla4xx testGetOperatingSystems de verit klaros service issuemanagementtest bugzilla TestBuagzilla4xx testGetPlatforms de verit klaros service issuemanagement test bugzilla TestBugzilla4xx testGetVersions de verit klaros service issuemanagementtest bugzilla TestBugzilla4xtestGetSeverities de verit klaros service issuemanagementtest bugzilla TestBugzilla4xx testGetComponents 1 2 Cancel Figure 8 14 The Import Test Results Page Pressing the Import button will import all results into Klaros Testmanagement 8 6 Creating Issues After the execution of a test case or test suite has been finished an issue in an issue man agement system can be created In order to do this at least one issue management sys tem has to be configured and also available in the selected project The configuration of an issue management system is described in Section 10 6 1 Issue Management and Sec tion 6 1 6 1 Editing the Issue Management Systems in a Project contains instructions on how to add a

Klaros-Testmanagement

Contents

Download Pdf Manuals

Related Search

Related Contents