Closed
Conversation
WalkthroughThis PR updates test descriptions across 40+ test YAML files to use explicit, verification-focused language. A configuration file receives formatting and a commented option. One test adds validation fields. No functional test logic changes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 16
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (5)
api-test/src/main/resources/mimoto/CreateVID/CreateVid.yml (1)
21-38:⚠️ Potential issue | 🟡 MinorTest input contradicts description and test name.
Test case
Mimoto_Generate_Temporary_VID_Valid_Smoke_sidand its description reference creating a "temporary VID," but the input specifies"vidType": "Perpetual". This should likely be"Temporary".📝 Proposed fix
input: '{ - "vidType": "Perpetual", + "vidType": "Temporary", "UIN": "$ID:AddIdentity_withValidParameters_smoke_Pos_UIN$",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@api-test/src/main/resources/mimoto/CreateVID/CreateVid.yml` around lines 21 - 38, The test Mimoto_Generate_Temporary_VID_Valid_Smoke_sid declares it validates creation of a temporary VID but the request input sets "vidType": "Perpetual"; update the input JSON for this test (the input field under the test name Mimoto_Generate_Temporary_VID_Valid_Smoke_sid / inputTemplate mimoto/CreateVID/createVid) to set "vidType": "Temporary" so the test name, description and payload are consistent.api-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/DownloadIssuerCredential/DownloadIssuerCredential.yml (1)
325-346:⚠️ Potential issue | 🟡 MinorTest input doesn't match description.
The description states "Verify that downloading credentials with a space in the code..." but the input has
"code": ""(empty string), not a space. This appears to be a copy-paste error from theEmptyCodetest case above.📝 Proposed fix
input: '{ "grantType": "authorization_code", - "code": "", + "code": " ", "redirectUri": "$INJIREDIRECTURI$",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@api-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/DownloadIssuerCredential/DownloadIssuerCredential.yml` around lines 325 - 346, The test case Mimoto_DownloadIssuerCredentialWithGoogleLogin_IssuerMosip_SpaceInCode_Neg has a mismatch between its description and input: the "code" field is an empty string instead of a space; update the input JSON for this test (the "code" property in the DownloadIssuerCredential input) to contain a single space character (" ") so it aligns with the test description and intent.api-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/DownloadIssuerCredential/DownloadIssuerCredential.yml (1)
76-98:⚠️ Potential issue | 🟡 MinorTypo in description: "local" should be "locale".
📝 Proposed fix
- description: Verifying that downloading a Sunbird Verifiable Credential (VC) with a valid authorization code after Google login fails when the local contains a space + description: Verifying that downloading a Sunbird Verifiable Credential (VC) with a valid authorization code after Google login fails when the locale contains a space🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@api-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/DownloadIssuerCredential/DownloadIssuerCredential.yml` around lines 76 - 98, Update the description text for the test case Mimoto_DownloadStayProtectedIssuerCredentialWithGoogleLogin_SunBirdC_SpaceInLocale_Neg by correcting the typo: change "local contains a space" to "locale contains a space" (i.e., edit the description property value where the test key Mimoto_DownloadStayProtectedIssuerCredentialWithGoogleLogin_SunBirdC_SpaceInLocale_Neg is defined).api-test/src/main/resources/mimoto/LoginFlow/Wallet/CreateWallet/CreateWallet.yml (2)
195-212:⚠️ Potential issue | 🟡 MinorDescription contradicts the test name and expected output.
The test case
Mimoto_CreateWallet_WalletNameWithSpaces_valid(suffix_valid) expects a successful wallet creation (walletName: "Automation Wallet"in output), but the description states "Verify that wallet creation fails when the wallet name contains spaces."Either the description should reflect successful creation, or the test name/output are incorrect.
📝 Suggested fix if creation with spaces is valid
- description: Verify that wallet creation fails when the wallet name contains spaces + description: Verify that wallet creation succeeds when the wallet name contains spaces🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@api-test/src/main/resources/mimoto/LoginFlow/Wallet/CreateWallet/CreateWallet.yml` around lines 195 - 212, The test case Mimoto_CreateWallet_WalletNameWithSpaces_valid currently has conflicting expectations: the description says creation should fail but the test name and output expect success ("walletName": "Automation Wallet"). Fix by making them consistent — either (A) update the description to state that wallet creation with spaces is allowed/succeeds, or (B) if creation should fail, rename the test to reflect a failure case (e.g., Mimoto_CreateWallet_WalletNameWithSpaces_invalid), change the output to the expected failure payload, and adjust the input/expected response accordingly; locate and update the fields named Mimoto_CreateWallet_WalletNameWithSpaces_valid, description, input (walletName), and output in the YAML to apply the chosen fix.
156-174:⚠️ Potential issue | 🟡 MinorDescription contradicts expected response code.
Test case
Mimoto_CreateWallet_MissingWalletName_ValidhasresponseCode: "200"(success) in output, but the description states "...fails as expected." The test name suffix_Validand HTTP 200 both suggest success, not failure.📝 Suggested fix
- description: Verify that creating a new wallet with a missing wallet name fails as expected + description: Verify that creating a new wallet with a missing wallet name succeeds as expected🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@api-test/src/main/resources/mimoto/LoginFlow/Wallet/CreateWallet/CreateWallet.yml` around lines 156 - 174, The test case Mimoto_CreateWallet_MissingWalletName_Valid (uniqueIdentifier TC_Mimoto_CreateWallet_09) is inconsistent: the description says creation "fails as expected" but output.responseCode is "200" and the test name ends with "_Valid"; either change the expected output.responseCode to the appropriate failure code (e.g., "400" or the API's validation code) to reflect a failing case when "walletName" is removed, or rename the test (and description) to indicate a success case and restore a valid input; update the output.responseCode or test name/description accordingly so they match the intended behavior.
🧹 Nitpick comments (2)
api-test/src/main/resources/mimoto/SunBirdR/SearchPolicySunBirdR/SearchPolicySunBirdR.yml (1)
4-4: Consider matching punctuation style with sibling test descriptions.Line 4 is missing a trailing period, while the related updated descriptions include one. Keeping this consistent helps metadata readability.
✍️ Suggested small consistency edit
- description: Verify that the system successfully searches and retrieves the Sunbird policy when all valid parameters are provided + description: Verify that the system successfully searches and retrieves the Sunbird policy when all valid parameters are provided.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@api-test/src/main/resources/mimoto/SunBirdR/SearchPolicySunBirdR/SearchPolicySunBirdR.yml` at line 4, Update the description string in SearchPolicySunBirdR.yml for the SearchPolicySunBirdR test to include a trailing period so it matches sibling test descriptions; locate the "description" key (the line that reads "Verify that the system successfully searches and retrieves the Sunbird policy when all valid parameters are provided") and append a period at the end.api-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/OAuthDetailsRequestSunBirdC/OAuthDetailsRequestSunBirdC.yml (1)
4-4: Optional: align wording style with the rest of the suite.Consider using “Verify that ...” phrasing for consistency with other updated specs.
✏️ Suggested wording
- description: Verifying authorization details via Google login to ensure Sunbird Verifiable Credentials (VCs) can be downloaded successfully + description: Verify that authorization details via Google login allow successful download of Sunbird Verifiable Credentials (VCs) - description: Verifying authorization details via Google login to ensure multiple Sunbird Verifiable Credentials (VCs) can be downloaded successfully + description: Verify that authorization details via Google login allow successful download of multiple Sunbird Verifiable Credentials (VCs)Also applies to: 32-32
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@api-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/OAuthDetailsRequestSunBirdC/OAuthDetailsRequestSunBirdC.yml` at line 4, Update the YAML description values to match the suite's phrasing style by changing the current sentence to start with "Verify that ..."; specifically replace the description field value "Verifying authorization details via Google login to ensure Sunbird Verifiable Credentials (VCs) can be downloaded successfully" with a phrasing like "Verify that authorization details via Google login allow Sunbird Verifiable Credentials (VCs) to be downloaded successfully" and make the same wording adjustment for the other occurrence referenced (the description at the other location).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@api-test/src/main/resources/mimoto/AidGetIndividualId/AidGetIndividualId.yml`:
- Line 120: Update the YAML description field for the AidGetIndividualId test
case to fix typos and match the project's description pattern: change "Verify
the system Generating individualID with invalid lengh of AID" to a clear
sentence such as "Validate that the system rejects generating an individualID
when the AID length is invalid" (lowercase "generating", correct "length"
spelling, and use "Validate that the system..."); also append the expected
negative behavior (e.g., "and returns an appropriate error response") so the
description clearly states the expected failure outcome; target the description
key in AidGetIndividualId/AidGetIndividualId.yml.
In `@api-test/src/main/resources/mimoto/AuthenticateUser/AuthenticateUser.yml`:
- Line 4: The description overstates the test scope; update the description in
AuthenticateUser.yml (the description field) to state that the test verifies
successful user authentication within the credential-download flow rather than
asserting that credentials are downloaded—e.g., replace the current text with a
concise phrase like "Verify user is successfully authenticated for the
credential-download flow when all valid parameters are provided."
In `@api-test/src/main/resources/mimoto/AuthLock/createAuthLock.yml`:
- Line 130: Update the description field in createAuthLock.yml to accurately
describe the negative test case: replace the current “invalid OTP” wording with
a phrase reflecting that the test uses an invalidVID with a valid OTP (e.g.,
“Verify system does not lock an authentication when an invalid VID is provided
with a valid OTP”); locate the description property in the createAuthLock.yml
test case that references invalidVID and edit it to match the actual condition.
In `@api-test/src/main/resources/mimoto/AuthUnLock/createAuthUnLock.yml`:
- Line 64: Update the YAML test description text to accurately reflect the
assertion target: replace "displays the appropriate error message" with wording
that references the asserted errorCode (e.g., "returns the expected errorCode")
so the description matches the test's verification of errorCode rather than
message text; locate the description line inside createAuthUnLock.yml (the
description field that currently reads "Validate that the system does not unlock
the UIN when an invalid OTP is provided and displays the appropriate error
message") and edit it to mention errorCode or response error code validation
instead.
In `@api-test/src/main/resources/mimoto/BindingOtp/BindingOtp.yml`:
- Line 84: Update the test description in BindingOtp.yml to accurately reflect
that the test sends an empty string for individualId rather than omitting the
field; specifically change the line currently reading "Validate that the system
does not generate an OTP when the individualID is missing" to indicate "empty"
(e.g., "when individualId is empty") so the description matches the test input
for individualId in the BindingOtp YAML.
- Line 280: The description in BindingOtp.yml currently says "OTP channel is
empty" but the test payload sets the channel to the literal "null" string;
update the description field to accurately state it's the null/"null"
OTP-channel scenario (or alternatively change the test payload to an empty
string) so the description and the test input match; edit the description
property in the BindingOtp.yml test case that references the OTP channel to
reflect "null" rather than "empty".
In
`@api-test/src/main/resources/mimoto/DownloadIssuerCredential/DownloadIssuerCredential.yml`:
- Line 100: Update the description string for the DownloadIssuerCredential YAML
entry that currently reads "Validate that the system does not download the
credential when an reused authorization code is provided" by replacing "an
reused authorization code" with the grammatically correct "a reused
authorization code" (i.e., modify the description field text to use "a" instead
of "an").
In
`@api-test/src/main/resources/mimoto/GetIssuerConfiguration/GetIssuerConfiguration.yml`:
- Line 4: Update the description fields in GetIssuerConfiguration.yml that
incorrectly refer to the "verifiers list" so they reference "issuer
configuration" instead; locate the description entries in the
GetIssuerConfiguration/GetIssuerConfiguration.yml (the YAML key named
description) and replace the domain term "verifiers list" with "issuer
configuration" for all affected cases (including the second occurrence noted in
the file) so test reports accurately reflect these issuer configuration tests.
In
`@api-test/src/main/resources/mimoto/LoginFlow/Authorization/GoogleLoginToken/GoogleLoginToken.yml`:
- Line 65: Update the YAML description for the negative test case
Mimoto_GoogleLoginToken_EmptyToken_Neg: change the wording that currently says
the ID token is “expired” to indicate the token is “empty” (or “missing”) so the
description accurately reflects that the test sends an empty cookie ("cookie":
"") and verifies failure to create a session token.
In
`@api-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/OAuthDetailsRequest/OAuthDetailsRequest.yml`:
- Line 32: The YAML's description field ("description") claims this is a
negative test for invalid/missing parameters while the request payload in
OAuthDetailsRequest.yml is valid; update either the description to state it's a
positive/valid payload test or modify the request payload to include the
intended invalid/missing fields (e.g., remove or blank required fields like
client_id or client_secret) so the description and payload in
OAuthDetailsRequest.yml match; ensure the "description" string and the request
body keys are consistent after the change.
In
`@api-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/ViewCredential/ViewCredential.yml`:
- Around line 287-290: The uniqueIdentifier "TC_Mimoto_ViewCredential_14" is
duplicated for the Mimoto_ViewCredential_Invalid_AcceptHeader_Neg test; update
the uniqueIdentifier value in the ViewCredential YAML entry
(Mimoto_ViewCredential_Invalid_AcceptHeader_Neg) to a new, globally unique token
(e.g., TC_Mimoto_ViewCredential_15 or another unused ID) so it no longer
collides with the earlier test's uniqueIdentifier and preserves traceability in
reports.
- Line 4: The description field in ViewCredential.yml under the ViewCredential
test is incomplete; update the description: finish the sentence to clearly state
the expected result (e.g., that the API returns the credential details and a 200
OK when a valid credential ID is supplied for the wallet), so replace the
current truncated text in the description node with a full sentence describing
the input, action, and expected outcome.
In
`@api-test/src/main/resources/mimoto/LoginFlow/Users/GetUserProfileAfterLogout/GetUserProfileAfterLogout.yml`:
- Line 4: Update the description field for the GetUserProfileAfterLogout test to
reflect post-logout unauthorized access (expected 401) instead of "logged-in
session"; in the GetUserProfileAfterLogout.yml change the description text to
clearly state this validates that accessing the user profile after logout
returns 401 Unauthorized (e.g., "Verify accessing the user profile after logout
is rejected with 401 Unauthorized"), so the description matches the test intent
and expected_status.
In
`@api-test/src/main/resources/mimoto/LoginFlow/Wallet/DeleteWallet/DeleteWallet.yml`:
- Line 108: Update the description value in DeleteWallet.yml for the
expired-session test case so it reflects an expired login session rather than
"without a login session"; replace the current description field text ("Verify
that deleting a wallet without a login session fails as expected") with
something like "Verify that deleting a wallet with an expired login session
fails as expected" to match the expired-session scenario and avoid duplicating
the previous test case description.
In
`@api-test/src/main/resources/mimoto/SunBirdC/OAuthDetailsRequestSunBirdC/OAuthDetailsRequestSunBirdC.yml`:
- Line 4: The description field in OAuthDetailsRequestSunBirdC.yml contains a
typo ("provideds"); update the description value in the
OAuthDetailsRequestSunBirdC.yml file (the description key for
OAuthDetailsRequestSunBirdC) to read "...when all valid parameters are provided"
replacing "provideds" with "provided" to correct the grammar.
In `@api-test/src/main/resources/mimoto/WalletBinding/WalletBinding.yml`:
- Line 1727: Update the description string in WalletBinding.yml for the test
whose current description reads "Verify that generating an OTP to bind a VID VC
fails when an invalid individualId is provided" to correctly describe the actual
test condition (missing requestTime); locate the test block by the existing
description field and change it to something like "Verify that generating an OTP
to bind a VID VC fails when requestTime is missing/omitted" so the wording
matches the scenario being tested.
---
Outside diff comments:
In `@api-test/src/main/resources/mimoto/CreateVID/CreateVid.yml`:
- Around line 21-38: The test Mimoto_Generate_Temporary_VID_Valid_Smoke_sid
declares it validates creation of a temporary VID but the request input sets
"vidType": "Perpetual"; update the input JSON for this test (the input field
under the test name Mimoto_Generate_Temporary_VID_Valid_Smoke_sid /
inputTemplate mimoto/CreateVID/createVid) to set "vidType": "Temporary" so the
test name, description and payload are consistent.
In
`@api-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/DownloadIssuerCredential/DownloadIssuerCredential.yml`:
- Around line 325-346: The test case
Mimoto_DownloadIssuerCredentialWithGoogleLogin_IssuerMosip_SpaceInCode_Neg has a
mismatch between its description and input: the "code" field is an empty string
instead of a space; update the input JSON for this test (the "code" property in
the DownloadIssuerCredential input) to contain a single space character (" ") so
it aligns with the test description and intent.
In
`@api-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/DownloadIssuerCredential/DownloadIssuerCredential.yml`:
- Around line 76-98: Update the description text for the test case
Mimoto_DownloadStayProtectedIssuerCredentialWithGoogleLogin_SunBirdC_SpaceInLocale_Neg
by correcting the typo: change "local contains a space" to "locale contains a
space" (i.e., edit the description property value where the test key
Mimoto_DownloadStayProtectedIssuerCredentialWithGoogleLogin_SunBirdC_SpaceInLocale_Neg
is defined).
In
`@api-test/src/main/resources/mimoto/LoginFlow/Wallet/CreateWallet/CreateWallet.yml`:
- Around line 195-212: The test case
Mimoto_CreateWallet_WalletNameWithSpaces_valid currently has conflicting
expectations: the description says creation should fail but the test name and
output expect success ("walletName": "Automation Wallet"). Fix by making them
consistent — either (A) update the description to state that wallet creation
with spaces is allowed/succeeds, or (B) if creation should fail, rename the test
to reflect a failure case (e.g.,
Mimoto_CreateWallet_WalletNameWithSpaces_invalid), change the output to the
expected failure payload, and adjust the input/expected response accordingly;
locate and update the fields named
Mimoto_CreateWallet_WalletNameWithSpaces_valid, description, input (walletName),
and output in the YAML to apply the chosen fix.
- Around line 156-174: The test case Mimoto_CreateWallet_MissingWalletName_Valid
(uniqueIdentifier TC_Mimoto_CreateWallet_09) is inconsistent: the description
says creation "fails as expected" but output.responseCode is "200" and the test
name ends with "_Valid"; either change the expected output.responseCode to the
appropriate failure code (e.g., "400" or the API's validation code) to reflect a
failing case when "walletName" is removed, or rename the test (and description)
to indicate a success case and restore a valid input; update the
output.responseCode or test name/description accordingly so they match the
intended behavior.
---
Nitpick comments:
In
`@api-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/OAuthDetailsRequestSunBirdC/OAuthDetailsRequestSunBirdC.yml`:
- Line 4: Update the YAML description values to match the suite's phrasing style
by changing the current sentence to start with "Verify that ..."; specifically
replace the description field value "Verifying authorization details via Google
login to ensure Sunbird Verifiable Credentials (VCs) can be downloaded
successfully" with a phrasing like "Verify that authorization details via Google
login allow Sunbird Verifiable Credentials (VCs) to be downloaded successfully"
and make the same wording adjustment for the other occurrence referenced (the
description at the other location).
In
`@api-test/src/main/resources/mimoto/SunBirdR/SearchPolicySunBirdR/SearchPolicySunBirdR.yml`:
- Line 4: Update the description string in SearchPolicySunBirdR.yml for the
SearchPolicySunBirdR test to include a trailing period so it matches sibling
test descriptions; locate the "description" key (the line that reads "Verify
that the system successfully searches and retrieves the Sunbird policy when all
valid parameters are provided") and append a period at the end.
ℹ️ Review info
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (52)
api-test/src/main/resources/config/mimoto.propertiesapi-test/src/main/resources/mimoto/AddIdentity/AddIdentity.ymlapi-test/src/main/resources/mimoto/AidGetIndividualId/AidGetIndividualId.ymlapi-test/src/main/resources/mimoto/AuthLock/createAuthLock.ymlapi-test/src/main/resources/mimoto/AuthUnLock/createAuthUnLock.ymlapi-test/src/main/resources/mimoto/AuthenticateUser/AuthenticateUser.ymlapi-test/src/main/resources/mimoto/AuthorizationCode/AuthorizationCode.ymlapi-test/src/main/resources/mimoto/BindingOtp/BindingOtp.ymlapi-test/src/main/resources/mimoto/CreateVID/CreateVid.ymlapi-test/src/main/resources/mimoto/DownloadIssuerCredential/DownloadIssuerCredential.ymlapi-test/src/main/resources/mimoto/GenerateVID/createGenerateVID.ymlapi-test/src/main/resources/mimoto/GetAllIssuers/GetAllIssuers.ymlapi-test/src/main/resources/mimoto/GetIssuerConfiguration/GetIssuerConfiguration.ymlapi-test/src/main/resources/mimoto/GetIssuerWellKnown/GetIssuerWellKnown.ymlapi-test/src/main/resources/mimoto/GetVerifierList/GetVerifierList.ymlapi-test/src/main/resources/mimoto/LoginFlow/Authorization/GoogleLoginToken/GoogleLoginToken.ymlapi-test/src/main/resources/mimoto/LoginFlow/Authorization/Logout/Logout.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/AuthenticateUser/AuthenticateUser.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/AuthorizationCode/AuthorizationCode.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/DownloadIssuerCredential/DeleteCredentials/DeleteCredentials.hbsapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/DownloadIssuerCredential/DeleteCredentials/DeleteCredentials.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/DownloadIssuerCredential/DeleteCredentials/DeleteCredentialsResult.hbsapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/DownloadIssuerCredential/DownloadIssuerCredential.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/FetchAllCredentials/FetchAllCredentials.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/OAuthDetailsRequest/OAuthDetailsRequest.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/ViewCredential/ViewCredential.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/ViewCredential/ViewCredentialAfterLogout.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/AuthenticateUserSunBirdC/AuthenticateUserSunBirdC.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/AuthorizationCodeSunBirdC/AuthorizationCodeSunBirdC.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/DownloadIssuerCredential/DownloadIssuerCredential.ymlapi-test/src/main/resources/mimoto/LoginFlow/DownloadStayProtectedIssuerCredentialWithGoogleLogin/OAuthDetailsRequestSunBirdC/OAuthDetailsRequestSunBirdC.ymlapi-test/src/main/resources/mimoto/LoginFlow/Users/GetUserProfile/GetUserProfile.ymlapi-test/src/main/resources/mimoto/LoginFlow/Users/GetUserProfileAfterLogout/GetUserProfileAfterLogout.ymlapi-test/src/main/resources/mimoto/LoginFlow/Wallet/CreateWallet/CreateWallet.ymlapi-test/src/main/resources/mimoto/LoginFlow/Wallet/DeleteWallet/DeleteWallet.ymlapi-test/src/main/resources/mimoto/LoginFlow/Wallet/GetWallets/GetWallets.ymlapi-test/src/main/resources/mimoto/LoginFlow/Wallet/UnlockWallet/UnlockWallet.ymlapi-test/src/main/resources/mimoto/LoginFlow/Wallet/UnlockWalletAfterDelete/UnlockWalletAfterDelete.ymlapi-test/src/main/resources/mimoto/LoginFlow/Wallet/UnlockWalletForTemporarilyLock/UnlockWalletForTemporarilyLock.ymlapi-test/src/main/resources/mimoto/OAuthDetailsRequest/OAuthDetailsRequest.ymlapi-test/src/main/resources/mimoto/SendOTP/SendOTP.ymlapi-test/src/main/resources/mimoto/SendOTPUIN/createSendOTP.ymlapi-test/src/main/resources/mimoto/SendOtpForVid/createSendOTP.ymlapi-test/src/main/resources/mimoto/SunBirdC/AuthenticateUserSunBirdC/AuthenticateUserSunBirdC.ymlapi-test/src/main/resources/mimoto/SunBirdC/AuthorizationCodeSunBirdC/AuthorizationCodeSunBirdC.ymlapi-test/src/main/resources/mimoto/SunBirdC/OAuthDetailsRequestSunBirdC/OAuthDetailsRequestSunBirdC.ymlapi-test/src/main/resources/mimoto/SunBirdR/CreatePolicySunBirdR/CreatePolicySunBirdR.ymlapi-test/src/main/resources/mimoto/SunBirdR/DeletePolicySunBirdR/DeletePolicySunBirdR.ymlapi-test/src/main/resources/mimoto/SunBirdR/GetPolicySunBirdR/GetPolicySunBirdR.ymlapi-test/src/main/resources/mimoto/SunBirdR/SearchPolicySunBirdR/SearchPolicySunBirdR.ymlapi-test/src/main/resources/mimoto/ValidateOTP/ValidateOTP.ymlapi-test/src/main/resources/mimoto/WalletBinding/WalletBinding.yml
api-test/src/main/resources/mimoto/AidGetIndividualId/AidGetIndividualId.yml
Show resolved
Hide resolved
api-test/src/main/resources/mimoto/AuthenticateUser/AuthenticateUser.yml
Show resolved
Hide resolved
...n/resources/mimoto/LoginFlow/DownloadMosipIssuerCredential/ViewCredential/ViewCredential.yml
Show resolved
Hide resolved
...ain/resources/mimoto/LoginFlow/Users/GetUserProfileAfterLogout/GetUserProfileAfterLogout.yml
Outdated
Show resolved
Hide resolved
api-test/src/main/resources/mimoto/LoginFlow/Wallet/DeleteWallet/DeleteWallet.yml
Outdated
Show resolved
Hide resolved
...c/main/resources/mimoto/SunBirdC/OAuthDetailsRequestSunBirdC/OAuthDetailsRequestSunBirdC.yml
Outdated
Show resolved
Hide resolved
api-test/src/main/resources/mimoto/WalletBinding/WalletBinding.yml
Outdated
Show resolved
Hide resolved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mimoto:Update the test case descriptions to improve clarity
Summary by CodeRabbit
Note: This PR contains internal test maintenance updates with no user-facing changes.