Skip to content
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

MARP-790 Fix failed tests of alfresco connector item #48

Conversation

ntqdinh-axonivy
Copy link
Contributor

No description provided.

@github-actions github-actions bot added the bug Something isn't working label Nov 11, 2024
@ntqdinh-axonivy
Copy link
Contributor Author

ntqdinh-axonivy commented Nov 11, 2024

Hi @ivy-rew

We found that the web-tester somehow made the test result of Alfresco connector fail.
From my understanding, the Web-tester focuses on testing the UI function when we interact with a component.
When I checked the testing code, only 1 test case of callable sub-process is tested and I think web-tester does not need to be set up for it. TBH, I'm not sure whether there is any behind the story that we want to include in the POM file.

Could we remove it from the test project or need to provide some additional setup to make the status green?

Copy link
Member

@ivy-rew ivy-rew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you are right @ntqdinh-axonivy , seems to be a forgotten dependency from the past. Therefore, it's good to omit it.
Thanks for the chore 🥇

@ntqdinh-axonivy ntqdinh-axonivy marked this pull request as ready for review November 11, 2024 10:19
@ntqdinh-axonivy ntqdinh-axonivy merged commit 78d8e7d into master Nov 11, 2024
4 checks passed
@ntqdinh-axonivy ntqdinh-axonivy deleted the bugfix/MARP-790-Fix-failed-tests-of-alfresco-connector-item branch November 11, 2024 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants