Long running jBehave test

One of the Foldering jBehave tests runs between 17 and 20 minutes every time it is run though it doesn’t seem to call any endpoint.

I'm a newbie to jBehave, can anyone suggest me what this test is trying to achieve and how to bring down the run time for this test?
Thanks!

Feature: Validate the encryption at rest of the display_name and normalized_name in the category table.

// ------------------------------

Scenario: I want to create a folder and verify the folder name encryption

Given the product is Forms Assembly

Given I have a folder named 'My Folder' whose category ID is assigned to ${myFolderCategoryID}

Then the folder name value for folder 'My Folder' has been encrypted

Find more posts tagged with

jbehave

refinitiv-internal

Accepted answers

All comments

Dave Bender

Which test is it?

Vishnu Gandhi

DiaplayNameEncryption.feature/java

Chris Nelson

I'm not seeing the same results. It looks like this test was temporarily disabled, if I re-enable it and run, it fails after 75 seconds. Does your DisplayNameEncryption.java have this method override in it?

@Override
public void runScenario() throws Throwable
{
// Temporarily disabled
}

Vishnu Gandhi

Yes, it contains the override, but I still see the test being running. Below is a trace I took from slowest.html which is generated as part of developer build. So it may be that the test is not properly disabled...

Class Name Time

DisplayNameEncryption testScenario 1288.545

ApplicationContextLoader loadApplicationContext 240.722

BaseControllerTests findRoControllersNotUsingUserToken 72.767

BaseControllerTests findRoControllersWithNoEventMapping 45.279

GetFrequentlyUsedItems testScenario 28.661

GetAncestorsWithtagsShared testScenario 18.538

EXPLORE OUR SITES