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

Fix issues related to integration tests due to the registry changes #3394

Open
RusJaI opened this issue Nov 27, 2024 · 3 comments
Open

Fix issues related to integration tests due to the registry changes #3394

RusJaI opened this issue Nov 27, 2024 · 3 comments

Comments

@RusJaI
Copy link

RusJaI commented Nov 27, 2024

Description

This is a subtask of Adding visibility restrictions in the developer portal based on the Organizations

Related Issues

#3061, #2925

@RusJaI
Copy link
Author

RusJaI commented Dec 1, 2024

Update [2024-11-29]

The test cases related to content search and store visibility are failing.

Since the default setup's existing behavior should not be modified, any relevant changes should be implemented in the code, not in the tests. These functional modifications are being tracked separately.

Therefore, the plan is to revisit and validate the tests once issue #3406 is resolved.

@RusJaI
Copy link
Author

RusJaI commented Dec 7, 2024

Update [2024-12-06]

Same set of integration tests are failing even after implementing the unified search.
Hence double checked the following tests flows manually :

  1. ContentSearchTestCase.testDocumentContentSearch()
  • create a tenant and create & publish an API logging in as the tenant admin (no visibility restrictions). Add a documentation with github4156 in the content. Go to devportal and do a content search in the tenant's devportal providing the value github4156 (not logged in). No documents getting listed. But can see the document and the content when click on the API and go to the documents section.

    tested this in a pack without config and APIM 4.4.0 live pack as well. There also the same issue appears.

  1. APIVisibilityByRoleTestCase.testVisibilityForAdminUserWithAdminAndSubscriberRoleInSameDomainInStore()
  1. APIVisibilityByRoleTestCase.testVisibilityForCreatorInStore()
  • Manually tested the following criteria which is given in the description. it worked as expected :
    Although API visibility on the devportal is restricted (eg, to the 'admin' role), if a user has the
     * 'internal/publisher' role, the API should still be visible to them.
     * This ensures that publishers can view all APIs of the organization on the devportal 
    
    Hence need to check this further

@RusJaI
Copy link
Author

RusJaI commented Dec 15, 2024

Update [2024-12-12]

Added the fixes for the identified bugs, in separate commits in the PR : wso2/carbon-apimgt#12717
The previously mentioned secondary user store related issues require further investigation and resolution.
Keeping this task on-hold since i have been allocated to work on a higher-priority task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant