It's all about the answers!

Ask a question

How to customize the status of Test Artifacts?


Xiaoguang Ning (51277) | asked May 29 '12, 1:56 p.m.
Hello,

Currently the test plan, test case, test suite, and test script have the predefined/fixed status shown below:

Draft
Under Review
Approved
Retired

The test execution also have predefined status but we can select which ones to use for text execution status.

Would anyone know how we can add or remove a status for the above testing artifacts at project level? I could not find the information in information center and thus am posting here to see if anyone has some tips or suggestions :)

Thanks in advance
Frank

9 answers



permanent link
Jun Wang (6077) | answered May 29 '12, 10:02 p.m.
Hi, Frank,

There will be a new feature to support customized workflow for those testing artifacts in the coming 4.0 release. If you have gotten the 4.0 Beta, you can see the ability on Test Artifacts -> Workflows of the project area management page.

Hello,

Currently the test plan, test case, test suite, and test script have the predefined/fixed status shown below:

Draft
Under Review
Approved
Retired

The test execution also have predefined status but we can select which ones to use for text execution status.

Would anyone know how we can add or remove a status for the above testing artifacts at project level? I could not find the information in information center and thus am posting here to see if anyone has some tips or suggestions :)

Thanks in advance
Frank

permanent link
Jun Wang (6077) | answered May 29 '12, 10:32 p.m.
If you want it before 4.0, please refer to https://jazz.net/forums/viewtopic.php?t=23795.

permanent link
Chandrahasa Reddy D (5715360) | answered May 30 '12, 1:13 a.m.
We can Customise the test artifacts workflows. Login as admin, Open Project Area--> Click on Test Artifacts-->WorkFlows.. here you can define your own workflows.. hope it helps


permanent link
Xiaoguang Ning (51277) | answered May 30 '12, 9:25 a.m.
Hello,

The "repotools-jts.bat -createTables" was done without error.

However, the following command failed. I verified the users and passwords used in the file by connecting to the JTS and DW databases, which had no issue. The dbadm authority was granted to the jtsDBuser (for JTS database) and to the dwDBUser (for the DW database).

Any tip of help is appreciated

Thanks

Frank

Here are the details (sorry for the long post):


E:\IBM\JazzTeamServer\server>repotools-jts.bat -createWarehouse

Repo Tools
Provisioning using "E:\IBM\JazzTeamServer\server\conf\jts\provision_profiles".
Jazz Foundation - Core Libraries, Version 4.0 RC5 (RJF-I20120518-1323)

CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".

CRJAZ1779I This server is configured as a JTS.
CRJAZ1365I The server is attempting to connect to the following database: "//CLM4poc.rmtools.ssh:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: DB2/NT64
Db Product Version: SQL09075
Db URL: jdbc:db2://CLM4poc.rmtools.ssh:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture
Jdbc Driver Version: 3.57.82
CRJAZ1781W The Public URI Root has not been set. Use the server setup wizard to enter the public URI. This property is required to enforce consistent URL mana
gement in the application. The public URI represents the URL that all clients must use to access the application.
CRJAZ1318I A database connection error occurred.
CRJAZ0265I The virtual storage or database resource is not available.
SQL: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY
(TESTPLAN_CLASS_ID)
Parameter 0: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
SQL Exception #1
SQL Message: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82
SQL State: 57011
Error Code: -964

CRJAZ1728E An unexpected error has been detected. See the log file "E:\IBM\JazzTeamServer\server\repotools-jts_createWarehouse.log" for more details.


-------------------------
The contents of the log file:

2012-05-30 09:11:23,890 Repo Tools
2012-05-30 09:11:23,890 java.version=1.6.0
2012-05-30 09:11:23,890 java.runtime.version=pwa6460sr10fp1-20120321_01 (SR10 FP1)
2012-05-30 09:11:23,906 Provisioning using "E:\IBM\JazzTeamServer\server\conf\jts\provision_profiles".
2012-05-30 09:11:23,937 repotools-jts -createWarehouse
2012-05-30 09:11:23,937 Jazz Foundation - Core Libraries, Version 4.0 RC5 (RJF-I20120518-1323)

2012-05-30 09:11:27,213 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
2012-05-30 09:11:27,400 CRJAZ1779I This server is configured as a JTS.
2012-05-30 09:11:29,709 CRJAZ1365I The server is attempting to connect to the following database: "//CLM4poc.rmtools.ssh:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;"
2012-05-30 09:11:32,580 CRJAZ1364I The connection to the following database was successful:
Db Product Name: DB2/NT64
Db Product Version: SQL09075
Db URL: jdbc:db2://CLM4poc.rmtools.ssh:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture
Jdbc Driver Version: 3.57.82
2012-05-30 09:11:34,420 CRJAZ1781W The Public URI Root has not been set. Use the server setup wizard to enter the public URI. This property is required to enforce consistent URL management in the application. The public URI represents the URL that all clients must use to access the application.
2012-05-30 09:12:12,157 CRJAZ1318I A database connection error occurred.
CRJAZ0265I The virtual storage or database resource is not available.
SQL: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
Parameter 0: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
SQL Exception #1
SQL Message: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82
SQL State: 57011
Error Code: -964

com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82
at com.ibm.db2.jcc.am.bd.a(bd.java:679)
at com.ibm.db2.jcc.am.bd.a(bd.java:60)
at com.ibm.db2.jcc.am.bd.a(bd.java:127)
at com.ibm.db2.jcc.am.km.c(km.java:2506)
at com.ibm.db2.jcc.am.km.d(km.java:2483)
at com.ibm.db2.jcc.am.km.b(km.java:1903)
at com.ibm.db2.jcc.t4.db.h(db.java:220)
at com.ibm.db2.jcc.t4.db.b(db.java:46)
at com.ibm.db2.jcc.t4.t.b(t.java:38)
at com.ibm.db2.jcc.t4.sb.g(sb.java:114)
at com.ibm.db2.jcc.am.km.db(km.java:1898)
at com.ibm.db2.jcc.am.km.a(km.java:2899)
at com.ibm.db2.jcc.am.km.e(km.java:985)
at com.ibm.db2.jcc.am.km.execute(km.java:969)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.StatementStatWrapper.execute(StatementStatWrapper.java:178)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.execute(StatementErrLogWrapper.java:169)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.StatementLeakWrapper.execute(StatementLeakWrapper.java:70)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeStatement(AbstractDataWarehouseDbProvider.java:108)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:227)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:113)
at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseDbProvider.createDataWarehouseCoreTables(DB2DataWarehouseDbProvider.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy440.createDataWarehouseCoreTables(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:141)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$5.run(RemoteDatabaseService.java:254)
at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:244)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy415.createRemoteSchemas(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.CreateDataWarehouseCommand.execute(CreateDataWarehouseCommand.java:18)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:66)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:768)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:843)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
2012-05-30 09:12:18,459 ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
com.ibm.team.repository.common.TeamRepositoryException: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:247)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:113)
at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseDbProvider.createDataWarehouseCoreTables(DB2DataWarehouseDbProvider.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy440.createDataWarehouseCoreTables(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:141)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$5.run(RemoteDatabaseService.java:254)
at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:244)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy415.createRemoteSchemas(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.CreateDataWarehouseCommand.execute(CreateDataWarehouseCommand.java:18)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:66)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:768)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:843)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: com.ibm.team.repository.service.internal.UncheckedRepositoryException: com.ibm.team.repository.common.RetryableDatabaseException: CRJAZ1318I A database connection error occurred.
CRJAZ0265I The virtual storage or database resource is not available.
SQL: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
Parameter 0: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
SQL Exception #1
SQL Message: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82
SQL State: 57011
Error Code: -964

at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.AbstractErrLogWrapper.logAndReturnException(AbstractErrLogWrapper.java:99)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.logAndReturnException(StatementErrLogWrapper.java:66)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.execute(StatementErrLogWrapper.java:171)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.StatementLeakWrapper.execute(StatementLeakWrapper.java:70)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeStatement(AbstractDataWarehouseDbProvider.java:108)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:227)
... 40 more
Caused by: com.ibm.team.repository.common.RetryableDatabaseException: CRJAZ1318I A database connection error occurred.
CRJAZ0265I The virtual storage or database resource is not available.
SQL: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
Parameter 0: ALTER TABLE TESTPLAN_CLASSIFICATION ADD CONSTRAINT TPLCLASS_PK PRIMARY KEY (TESTPLAN_CLASS_ID)
SQL Exception #1
SQL Message: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82
SQL State: 57011
Error Code: -964

at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.AbstractErrLogWrapper.logAndReturnException(AbstractErrLogWrapper.java:98)
... 45 more
Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82
at com.ibm.db2.jcc.am.bd.a(bd.java:679)
at com.ibm.db2.jcc.am.bd.a(bd.java:60)
at com.ibm.db2.jcc.am.bd.a(bd.java:127)
at com.ibm.db2.jcc.am.km.c(km.java:2506)
at com.ibm.db2.jcc.am.km.d(km.java:2483)
at com.ibm.db2.jcc.am.km.b(km.java:1903)
at com.ibm.db2.jcc.t4.db.h(db.java:220)
at com.ibm.db2.jcc.t4.db.b(db.java:46)
at com.ibm.db2.jcc.t4.t.b(t.java:38)
at com.ibm.db2.jcc.t4.sb.g(sb.java:114)
at com.ibm.db2.jcc.am.km.db(km.java:1898)
at com.ibm.db2.jcc.am.km.a(km.java:2899)
at com.ibm.db2.jcc.am.km.e(km.java:985)
at com.ibm.db2.jcc.am.km.execute(km.java:969)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.StatementStatWrapper.execute(StatementStatWrapper.java:178)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.execute(StatementErrLogWrapper.java:169)
... 43 more
2012-05-30 09:12:18,475 CRJAZ1728E An unexpected error has been detected. See the log file "E:\IBM\JazzTeamServer\server\repotools-jts_createWarehouse.log" for more details.

-----------------
The content of the team.properties file:

com.ibm.team.repository.ws.allow.identity.assertion=false
com.ibm.team.repository.changeEvent.expirationDefault=1209600
com.ibm.team.datawarehouse.db.jdbc.password=
com.ibm.team.fulltext.indexLocation=E\:/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex
com.ibm.team.repository.db.jdbc.location=//CLM4poc.rmtools.ssh\:50000/JTS\:user\=jtsDBuser;password\={password};
com.ibm.team.repository.db.repoLockId=_ktCucapUEeGnAYLBRjKMTA
com.ibm.team.repository.web.suppressedPages={"com.ibm.team.repository.web.admin"\: }
com.ibm.team.repository.db.jdbc.password=
com.ibm.team.repository.web.helpuri=/clmhelp/index.jsp
com.ibm.team.datawarehouse.db.jdbc.location=//CLM4POC.rmtools.ssh\:50000/DW\:user\=dwDBuser;password\={password};
com.ibm.team.datawarehouse.db.base.folder=E\:\\DB2\\NODE0000\\JAZZDW
com.ibm.team.jfs.index.root.directory=E\:/IBM/JazzTeamServer/server/conf/jts/indices
com.ibm.team.repository.db.vendor=DB2
com.ibm.team.datawarehouse.report.user=RPTUSER
com.ibm.team.repository.changeEvent.expirationByCategory=SystemLog\:259200
com.ibm.team.datawarehouse.db.vendor=DB2

permanent link
Xiaoguang Ning (51277) | answered May 30 '12, 9:27 a.m.
We can Customise the test artifacts workflows. Login as admin, Open Project Area--> Click on Test Artifacts-->WorkFlows.. here you can define your own workflows.. hope it helps



Thanks to you and Jun for the reply. I will try what you suggested first:-)

permanent link
Xiaoguang Ning (51277) | answered May 30 '12, 9:37 a.m.
We can Customise the test artifacts workflows. Login as admin, Open Project Area--> Click on Test Artifacts-->WorkFlows.. here you can define your own workflows.. hope it helps



Hi there,

Would you be more specific about the URL and link menu to follow?

Did you mean logging in <>/qm/admin or <>/qm/web?

After login, what is the detailed "click" path to follow?

Thanks

permanent link
Jun Wang (6077) | answered May 30 '12, 10:08 a.m.
If you are using 4.0, please go to the link https://<server>:<port>/qm/admin#action=com.ibm.team.process.manageProjectAreas, then click into the project area, you will see Test Artifacts->Workflows on the left bar.

We can Customise the test artifacts workflows. Login as admin, Open Project Area--> Click on Test Artifacts-->WorkFlows.. here you can define your own workflows.. hope it helps



Hi there,

Would you be more specific about the URL and link menu to follow?

Did you mean logging in <>/qm/admin or <>/qm/web?

After login, what is the detailed "click" path to follow?

Thanks

permanent link
Xiaoguang Ning (51277) | answered May 30 '12, 11:31 a.m.
If you are using 4.0, please go to the link https://<server>:<port>/qm/admin#action=com.ibm.team.process.manageProjectAreas, then click into the project area, you will see Test Artifacts->Workflows on the left bar.

We can Customise the test artifacts workflows. Login as admin, Open Project Area--> Click on Test Artifacts-->WorkFlows.. here you can define your own workflows.. hope it helps



Hi there,

Would you be more specific about the URL and link menu to follow?

Did you mean logging in <>/qm/admin or <>/qm/web?

After login, what is the detailed "click" path to follow?

Thanks


Thanks. I am using V3. Yeah, Jun mentioned that the feature is available in V4. Thanks for the links in V4.

permanent link
Xiaoguang Ning (51277) | answered Jun 05 '12, 9:48 a.m.
Just played with CLM 4 RC5 for the customization feature of test artifacts. It looks great compared to CLM V3.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.