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

1. Strings #8 #104

Merged
merged 4 commits into from
Feb 15, 2023
Merged

1. Strings #8 #104

merged 4 commits into from
Feb 15, 2023

Conversation

RobertMili
Copy link
Contributor

  1. Change the name of class and test class
  2. More test were written
  3. This was made with a verified account

@RobertMili RobertMili linked an issue Feb 14, 2023 that may be closed by this pull request
Copy link
Contributor

@safstromo safstromo left a comment

Choose a reason for hiding this comment

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

You need to rename your classes, they cant be named "Redis".

I think the best solution would be to:
Merge your code with Origin main you can put your code in the HazeDatabase class methods instead.
Put your code inside the locks so that only one client can write to the database at time.

2. More test were written
3. Merge Redis Server to class HazeDatabase
safstromo
safstromo previously approved these changes Feb 14, 2023
Copy link
Contributor

@BobHogvall BobHogvall left a comment

Choose a reason for hiding this comment

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

Great work Robert! Just a small note:

Perhaps not the most important but if we want to follow the standard for test writing we should remove "public" from the tests: "JUnit5 test classes and methods should have default package visibility"

example:
@test
void testSetWithValidKeyValuePair() {}

We should be able to see this in sonarCloud as well! If you have sonarLint on your local computer it should be visible there as well.

Regards!

@RobertMili
Copy link
Contributor Author

Great work Robert! Just a small note:

Perhaps not the most important but if we want to follow the standard for test writing we should remove "public" from the tests: "JUnit5 test classes and methods should have default package visibility"

example: @test void testSetWithValidKeyValuePair() {}

We should be able to see this in sonarCloud as well! If you have sonarLint on your local computer it should be visible there as well.

Regards!

Thank you for reviewing my code

Copy link
Contributor

@BobHogvall BobHogvall left a comment

Choose a reason for hiding this comment

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

Maybe there was a misunderstanding, my bad, but I meant the tests in the test classes. All of them could be written with the default package visibility, which means you remove "public" from all the tests in the test class. This should also make sonarCloud happy and hopefully remove the red cross.

@sonarcloud
Copy link

sonarcloud bot commented Feb 14, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

Copy link
Contributor

@BobHogvall BobHogvall left a comment

Choose a reason for hiding this comment

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

Perfect!

@RobertMili RobertMili changed the title 1. Change the name of class and test class 1. Strings #8 Feb 15, 2023
@kappsegla kappsegla added this pull request to the merge queue Feb 15, 2023
Merged via the queue into main with commit 18b083f Feb 15, 2023
@kappsegla kappsegla added the enhancement New feature or request label Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Strings
6 participants