Checklist to test the Uli Browser extension

Table of Contents

1. Test Case: Check DOM features
   • Slur Replacement
   • Slur Metadata
2. Test Case: Check Working of the Personal Slur list
3. Test Case: Try contributing from the context menu without login
4. Test Case: Login
5. Test Case: Test Crowdsourcing
6. Test Case: Test Syncing Data Functionality
   • Sub Test Case: Verify that newly vetted slurs are synced

Note:

• The following tests are to be performed on the ULI browser extension after loading it in Chrome and Firefox browsers.
• The prerequisite for the following testing is that the uli-community server is up and running.
• The following tests are for the development bundle of the extension. To test out the production bundle, load it in the browsers and repeat the same steps.
• While testing in the production bundle, if any slur is crowdsourced, delete it after checking that the contribution functionality works.
• For the production bundle, while testing the 7th step, just check the logs after clicking on the "Download slurs" button. Further checking for syncing (by adding and deleting entries in the database) testing would not be possible.

1. Test Case: Check DOM features

Check the "Enable Slur Replacement" and "Enable Slur Metadata" features.

Steps:

Slur Replacement

1. Search for the word "crazy" on Google.
2. Open the extension popup, then select the "Enable Slur Replacement" option and then click on "Save".

Expected Outcome: All the instances of the word "crazy" should be redacted with a black mark as shown in the below image.

Slur Metadata

1. Search for the word "crazy" on Google.
2. Open the extension popup, then select the "Enable Slur Metadata" option and then click on "Save".

Expected Outcome: All the instances of the word "crazy" should be highlighted and hovering on each of them should render a box near the word to show its metadata as shown in the below image.

• Test the above features for some (or all) of the links below. Apart from these URLs, testing on different websites can also be done.

1) https://www.reddit.com/r/EnglishLearning/comments/179zoxf/strongest_curses_swear_words_and_phrases/


2) https://www.reddit.com/r/TwoXIndia/comments/12eq26b/girls_what_are_really_bad_slurs_names_that_your/


3) https://www.reddit.com/r/india/comments/5lim6o/dear_india_whats_your_favorite_insultabuse_phrase/


4) https://www.reddit.com/r/india/comments/iis87h/what_are_some_indian_swear_words/


5) https://www.instagram.com/p/CPaEJHHt6XA/


6) https://x.com/KapilMishra_IND/status/1514915548001636353 AND https://www.theguardian.com/world/2015/may/26/french-journalist-poses-muslim-convert-isis-anna-erelle


7) https://en.wikipedia.org/wiki/Hindustani_profanity AND https://www.reddit.com/r/DHHMemes/comments/1e7oc6q/madarchod/


8) https://www.instagram.com/sammyjames7/reel/CloP2PCJt3X/

2. Test Case: Check Working of the Personal Slur list

Steps:

1. To open the personal slur list, open the extension popup and on the "Preferences" tab, click on the "Add to your personal block list" button.
2. Try adding some words to the personal slur list, for example, try adding the words dumb, idiot, bitter, and more. Save the list and enable the slur-replacement feature as shown in the previous steps. Test for the added words to see if the slur-replacement feature is working or not.
3. Close the extension and open it again. Go to the personalized slur list to see if the previously added words still exist or not. If everything works as expected, the previously added words should persist.

3. Test Case: Try contributing from the context menu without login

This step requires that the user is not logged in.

Steps:

1. Select a word on the webpage, and right-click on it to open the context menu. On context-menu select the "Add slur to Uli" option.
2. If everything works properly, an alert should appear with the following message: "Please login to Uli Browser Extension to contribute"
3. Next, in the extension popup, go to the "My Contributions" section. There, a button with the text Login to Contribute should appear instead of anything else.

4. Test Case: Login

This step requires an account in the uli-community (here, it means in the local setup). If an account hasn't been created, a new account can be created at http://localhost:4000/users/register.

Steps:

1. In the extension, go to the "Account" section and login with the uli-community credentials.
2. Next, go to the "My Contributions" section again. Now, adding a new slur would be allowed and the past contributions (if any) would also be visible.
3. Try adding a new slur from the context menu once again. Select a word and right-click on it, then select "Add Slur to Uli". Now, the contribution should be done successfully. An alert message would also be shown confirming the contribution. Check this contribution in the "My Contributions" section.

5. Test Case: Test Crowdsourcing

Steps:

• In "My Contributions", try to add new contributions, for example, try adding the words with metadata: "idiot", "dumb", "bitter", etc. Then, edit previous contributions and check if everything is updating correctly or not.

6. Test Case: Test Syncing Data Functionality

Steps:

1. Click on the "Download New Crowdsourced Slurs" button in the "Preferences" section. On successful syncing, a "Synced!" notification should appear at the top-right corner of the popup.
2. In case there is an error, a notification indicating the same would appear at the top-right corner of the popup.

Sub Test Case: Verify that newly vetted slurs are synced

This test case is there to check if the newly vetted slurs that are approved through uli-community, are getting synced in the extension as well or not. This test case requires the tester to be logged in as Admin in the uli-community.

Steps:

1. Crowdsource a new slur as described in the previous steps.

2. Open the uli-community's crowdsourced slurs page at http://localhost:4000//crowdsource-contributions.

3. On the crowdsourced slurs page, locate the newly contributed slur.

4. On the last column of the table, there would be a button "Add" in it. Click on this button.

5. A modal should open. The top-most dropdown allows you to toggle between "adding the slur" and "adding new slur metadata".

6. First, with the "Approve Slur Only" selected, click on the "Add Only Slur" button to vett only the slur.

7. Second, after selecting the "Approve Slr Metadata" option, fill in all the required details and then click on the "Save Slur Metadata" button to add a new vetted slur metadata entry.

   

8. To check whether multiple entries are syncing properly, try vetting multiple entries in the uli-community at once as mentioned in the above steps.

9. Search for one of the words that were recently vetted on Google.

10. Open the popup and enable the slur replacement and slur metadata features to confirm that they are not working for this word before syncing.

11. Open the popup, on the "Preferences" tab, and click on the "Download New Crowdsourced Slurs" button only ONCE.

12. Refresh the page or enable the features to check if they are working on the word now. If the syncing was successful, the features should work on the word.

13. Test it for the rest of the newly vetted slurs and slur metadata.