llaske / sugarizer-server

Sugarizer Server allow deployment of Sugarizer on a local server, for example on a school server.
Apache License 2.0
43 stars 94 forks source link

Selenium testing #391

Open parteekcoder opened 1 year ago

parteekcoder commented 1 year ago

@llaske @NikhilM98

398

First step towards selenium testing for sugarizer-server

image

I would like your suggestions and work upon, now it is just a initial step I will refactor the code to the best possible approch

parteekcoder commented 1 year ago

also there are some eslint errors I will remove them

parteekcoder commented 1 year ago

hi @llaske @NikhilM98 please guide me, I will make code more optimized but I want to know if it is to be done in the way I implemented

currently I implemented 2 tests, whose outputs are coming correct as expected image

parteekcoder commented 1 year ago

I know first I need to add a fakeuser to test login page , but now I just want to show what I have implemented

I will first add a fakeuser and update this PR

parteekcoder commented 1 year ago

image

NikhilM98 commented 1 year ago

Good job! This PR looks good as the first step towards selenium testing. I'll update you about the scope of the Selenium testing soon.

parteekcoder commented 1 year ago

Good job! This PR looks good as the first step towards selenium testing. I'll update you about the scope of the Selenium testing soon.

@NikhilM98 thanks for the review, should write some more test

parteekcoder commented 1 year ago

Good job! This PR looks good as the first step towards selenium testing. I'll update you about the scope of the Selenium testing soon.

Hey @NikhilM98 you are telling about some selenium testing scope , what is that

NikhilM98 commented 1 year ago

The idea is to have functional testing to complement unit testing. The selenium tests should test the the features of each view.

For example (for Users view): testing "if the users are correctly listed in the users view", "does searching, sorting, and filtering on the users view works as expected", "does the users form successfully creates a new user", "are the details of the created user correct in the edit user view", etc.

parteekcoder commented 1 year ago

The idea is to have functional testing to complement unit testing. The selenium tests should test the the features of each view.

For example (for Users view): testing "if the users are correctly listed in the users view", "does searching, sorting, and filtering on the users view works as expected", "does the users form successfully creates a new user", "are the details of the created user correct in the edit user view", etc.

yeah sure @NikhilM98 I will work upon this

llaske commented 1 year ago

I've fixed a specific issue on Linux and published a branch here https://github.com/llaske/sugarizer-server/tree/feature/selenium

parteekcoder commented 1 year ago

I've fixed a specific issue on Linux and published a branch here https://github.com/llaske/sugarizer-server/tree/feature/selenium

Thanks @llaske , please may I know the issue on Linux. So that in Future I also consider that while making PR

parteekcoder commented 1 year ago

@llaske I checked that branch and understood the issue. Thanks for fixing this.