-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LPS-122810 Set voted style with a unique style #615
Conversation
…atibilityConverterImpl, to avoid converting it every time we save the web content.
…erted to the correct format
…lateNode._getLatestArticleData()
…tibility-expected-results.xml since if we format this file we can not use Assert.assertEquals(expectedDocument.formattedString(), document.formattedString()); to compare it
…est and replace it with testGetLinkToLayoutValue in JournalContentCompatibilityConverterTest
The <clay:management-toolbar-v2 /> tag has been replaced with the <clay:management-toolbar /> tag (which uses clay v3). Creating, merging and deleting tags should work as expected. **Test plan**: - Navigate to **Categorization**>**Tags** - Assert that you can create a tag - Assert that you can delete the tag you created previously - Assert that you can merge two or more tags correctly.
…roductMenuApp from quarantine.
…kins-results-parser
… already deployed the jar as module. This may cause a "uses" constraint violation which is discovered when upgrade Log4J.
…y for web content and now in web content we are using the new data engine
The <clay:management-toolbar-v2 /> tag has been replaced with the <clay:management-toolbar /> tag (which uses clay v3). **Test plan**: - Navigate to **Content & Data** > **Documents and Media** - Uploading new files should work as expected - Editing tags should work as expected - Deleting items should work as expected - Moving items to a new folder should work as expected - Creating Document Types should work as expected - Creating Metadata Sets should work as expected
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
✔️ ci:test:sf - 1 out of 1 jobs passed in 36 secondsClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-122810 1 Successful Jobs:For more details click here. |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#99252 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#7610 |
Jenkins Build:test-portal-source-format#4740 |
No description provided.