Hello, developer team,

We have been developping our product with jazz client library. We
created the unit test for our product, so in some test cases, we need
to create some work items to test server for the test data in test
set-up method on JUnit.

We wrote code which creating a project area, creating some work items
in setUp method. deleting project area in tearDown method.

Of course, we schedule CI in three times in a day(naturally-using
RTC). But the elapsed time for running all tests increased steadily
by execution. The test server been connected by test case, is
restarted everyday.

We collected the follwoing elapse in a week, and analized that.

the elapse of a certain test method.

times ratio
--------- --------
first 1
second 1.5
third 2.5 - 6


Will you please tell me what we should do

Best regards,

- Takeshi

Thank you for replying.

lavinmwrote:
Can you tell us a little more about what your tests are doing? When
you
run your tests is the DB back at the same empty state?


We start a new server for each integration. And then we create new
data for test in Junit setUp method, and delete them in JUnit
tearDown method to ensure consistent data. The integration runs over
100 test cases.


For example(JUnit3.x)


protected void setUp() throws Exception {
createProjectArea(testProjectAreaName);
createWorkItem(testProjectAreaName, "Task 1 for
test");
super.setUp();
}

protected void tearDown() throws Exception {
deleteProjectArea(testProjectAreaName);
super.tearDown();
}



The code of creation of project area,

	private String createNewProjectAreaFromCopy(String
baseProjectName, String projectName)
			throws TeamRepositoryException, TeamOperationCanceledException
{
		IProjectArea projectArea = getProjectArea(baseProjectName);

		IProjectArea area = processItemService.createProjectArea();
		area.setName(projectName);
		area.setProcessDefinition(projectArea.getProcessDefinition());
		area.setProcessContentURL(projectArea.getProcessContentURL());
		area.setProcessName(projectArea.getProcessName());
		area.setProcessSummary(projectArea.getProcessSummary());

		processItemService.save(area, null);
		processItemService.initialize(area, null);
		return projectName;
	}

The code of creating work item,

IProjectArea projectArea = (IProjectArea)
RepositoryServiceUtil.getProcessArea(projectAreaName,
getTeamRepository());
ITeamAreaHandle teamHandle =
getTeamAreaHandle(projectArea);
IIterationHandle itrHandle =
RepositoryServiceUtil.getIterationHandle(getTeamRepository(),
projectArea, "M1");

Identifier<IState> state =
Identifier.create(IState.class, stateId);
IWorkItemType useType = getWorkItemType(typeName,
projectArea);
ICategoryHandle categoryHandle =
getCategoryHandle(teamHandle);

Identifier<IPriority> priorityIdentifier = null;
if (priorityString != null) {
priorityIdentifier =
Identifier.create(IPriority.class, priorityString);
}

	//Extending WorkItemOperation
WorkItemOperation op = new WorkItemCreatorImpl(
summaryName,
itrHandle,
categoryHandle,
state,
priorityIdentifier );
IContributorManager manager =
getTeamRepository().contributorManager();
if (owner != null) {
IContributor contributor =
manager.fetchContributorByUserId(owner, null);
assert contributor != null;
((WorkItemCreatorImpl)op).owner =
contributor;
}

return op.run(useType, null);

The problem is similar to
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=27855.
But the defect had already fixed.

lavinmwrote:
In our build system, we typically start a new server for each
testsuite
(to ensure consistent data). Do you have any server side extensions

that might be left running after each test pass?

We have no server side extensions. We have been developing with only a
client library.

The point of our question is that we'd like to remove the risk which
our product using client library will have gotten slow while our
product and RTC server is running. So we'd like to know what the
cause of problem.

best regards,
-Takeshi

Additionally a simple test would be to start metronome by Windows -> Preferences -> Team -> Jazz Source Control from the Rational Team Concert client (GUI). Check metronome. It will display round trip response times of different commands. Connect to the repository while you are experiencing the slowness. For how to read the metronome stats pls read https://jazz.net/blog/index.php/2008/02/01/the-jazz-metronome-tool-keeps-us-honest/