Skip to content

chore: Update to junit5 and doc upgrades #856

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Conversation

manisha1997
Copy link
Contributor

Fixes

Upgrade to junit5

Checklist

  • I acknowledge that all my contributions will be made under the project's license
  • I have made a material change to the repo (functionality, testing, spelling, grammar)
  • I have read the Contribution Guidelines and my PR follows them
  • I have titled the PR appropriately
  • I have updated my branch with the main branch
  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary documentation about the functionality in the appropriate .md file
  • I have added inline documentation to the code I modified

If you have questions, please file a support ticket, or create a GitHub Issue in this repository.

@@ -30,18 +30,18 @@ public void singleArgConstructorShouldPreserveMessage() {
@Test
public void twoArgConstructorShouldPreserveMessageAndCause() {
ApiException error = new ApiException(anyMessage, anyCause);
assertEquals("Message", anyMessage, error.getMessage());
assertSame("Cause", anyCause, error.getCause());
assertEquals(anyMessage, error.getMessage());
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we removing the strings in these assert functions while they are unchanged over here?

@@ -30,29 +33,29 @@ public void setUp() {

@Test
public void testValidate() {
Assert.assertTrue("Request does not match provided signature", validator.validate(url, params, signature));
assertTrue(validator.validate(url, params, signature));
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to remove these strings too?

Copy link
Contributor

Choose a reason for hiding this comment

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

If yes, what are we checking that the validate() will return? Just any non-false response?

.elevenlabsTextNormalization("elevenlabs_text_normalization")
.interruptSensitivity("interrupt_sensitivity")
.debug("debug")
.welcomeGreetingInterruptible("true")
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are the changes made here to just check a true response and not exact string matching?

.elevenlabsTextNormalization("elevenlabs_text_normalization")
.interruptSensitivity("interrupt_sensitivity")
.debug("debug")
.welcomeGreetingInterruptible("true")
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above

@tiwarishubham635
Copy link
Contributor

Cluster tests are failing, can you recheck?

Copy link

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

Successfully merging this pull request may close these issues.

2 participants