Add more test cases.

[RobertWesner]

This is specific to the testing scripts, not test.user.js. (See Script.purs)

I tested most of the cases I could think of:

• Navigation from YouTube home screen
• Clean reloads
• Navigation between channels
• Incorrect Channel ID For Mythbusters #9

This is probably close to 100% coverage, but more cases, different channels, are always a nice addition.

[AdminAdi]

Hey i want to work on the issue #46

[RobertWesner]

Hey i want to work on the issue #46

Thank you for your interest in helping out.

Are you familiar with Purescript and Puppeteer (via Toppokki)?
The tests for this project are written in Purescript and utilize the Toppokki bindings to navigate Puppeteer.

It should be fairly easy to extend, so if you haven't worked with them before, it can be a nice way to get some experience with those tools. Although the functional programming syntax can be a bit confusing if coming from an imperative/OOP background.

The bindings are close to how Puppeteer is navigated with JS. Most things can be taken from the Puppeteer documentation and applied to Toppokki.

@AdminAdi if you are still interested, let me know.

[AdminAdi]

Yess I am interested I want to work

[RobertWesner]

Awesome, I'll assign you the issue.

There are instructions on how to set up and run the tests in the readme. You can find the tests in the testing directory.

Using Docker/Podman is the most straightforward approach, but I'd recommend working with them directly on your host machine so you can inspect the Chromium instance visually.

To get the Chromium to display, you will need to adjust the setup slightly:

- browser <- T.launch { args: [ "--no-sandbox", "--disable-setuid-sandbox"] }
+ browser <- T.launch { args: [ "--no-sandbox", "--disable-setuid-sandbox"], headless: false }

Feel free to add a command line option like --show/--display/etc. if that is something you are also interested in, it would make working with the tests more comfortable to future developers.

If you have any questions, let me know!

[RobertWesner]

Also an important note, you should work from the development branch.

[AdminAdi]

okk sir

[RobertWesner]

Sorry for any confusion I caused with the good first issue label, I originally meant it as a "good first issue to explore the project" as it is mostly a surface-level addition and does not change the userscript itself.

After looking into how GitHub uses that label, it’s usually meant for much simpler tasks than this. This issue assumes a fair bit of prior knowledge with functional programming and the PureScript + Puppeteer setup, so I’m going to remove good first issue and keep only help wanted.

If you still want to contribute, you are very welcome to - just keep in mind it's a task that can take a bit of time, even if you are familiar with the surrounding language and libraries.