code-charity/youtube

Automation of Testing, Github & Stores

Opened this issue · 8 comments

Deleted user commented

Edit by @ImprovedTube (Repurposing this thread)

To-Do:

EvgenKo423 commented

Were you using Beta a lot too by chance?

No, I'm using release, but with new UI it's much less polished, unfortunately (even though this UI exists for 3-4 years now; it was just me using the old one till the very end).

I was actually thinking a few times how your workflow could be made better, but unfortunately there's a huge gap for me now between thinking and actually working on it (I think of many things from time to time, but unfortunately there's no mental programming technique yet 🤭, we would be much more productive).

Here are a few things:

  1. dev, beta and master branches:

    • Every 2 weeks dev is merged into beta -> automatic beta release to store (GH Actions, no idea if it's possible);
    • Every 2 weeks beta is merged into master -> automatic stable release to store;
    • Bug fix commits to beta and master only.

  2. Automated tests of all functionality (GH Actions, no idea if it's possible; though Selenium exists):

    • Basic checks: default settings + each option turned on at a time. Executed on every push;
    • Complete checks: every possible combination of settings tested (will probably eat a lot of Action time). Executed before every merge to beta / master;
    • Performance checks: one setting at a time, test on all page types (home, channel, video...). CPU usage (or maybe something more appropriate) is measured for 3-5 seconds after page is ready. Executed before every merge to beta / master.

    Actual YT pages are crawled before the test. All tests are done on local copies.

ImprovedTube commented

old GUI? i liked the darkRed-white-contrast & pixel density(need not be bigger than browser icons)
less polished, why? 'New' one still got list-view option. Newer displays have smaller pixels and more contrast.
Some new users might expect/prefer calm experience & low mouse control/touchpad?

Testing consistency & CPU with Selenium
👍

Github actions

https://dev.to/michaelcurrin/beginner-s-guide-to-github-actions-49aa#:~:text=What%20is%20GitHub%20Actions

Just a question of time and number of GitHub action / pull requests (not many yet)

(+ AI for the project to program itself)

The bug caused few uninstalls/reinstalls:
maybe 100 or 0.03% 🤔 hard to guess - the few guys giving 1 Star, might harm more on a longer term)

Yet on the same day we should have focused even more on the 2800 new installations / over 0.5%

EvgenKo423 commented

old GUI, why?

I mean YouTube UI. =)) Your extension worked much better with old YouTube UI (and the UI worked better itself).

It could be used for direct contributions as well (and you could make PRs from dev to beta to run tests), it would make finding bugs much easier.

ImprovedTube commented

ohh of course 😀 @EvgenKo423

automatic beta release to store (GH Actions, no idea if it's possible);

Github Actions to publish 🌞 with: Chrome Web Store & FireFox & Edge

--

Plan:
master = we read the PR's per contributor + devs/testers (few) automatically run this in browsers
+daily autotesting = beta (not a repo)
+longer-autotest + some days = stable (not a repo)

+automatic release notes?🤔

exception: urgent changes after youtube changes

Goal:

4.9 stars & keeping people up-to-date. Get feedback for new features soon enough for every contributor.
& beta: ~4.5 stars (many people didnt notice what version they get (testing) - including a large organisation with 1000s of users )

dev ... direct contributions

= world editing. easier collaboration, only if there are ever two people updating the same feature on the same day

User198263321 commented

I hope that this has an optional setting to toggle the old style.

Moninha123 commented

Problema corrigido com sucesso, ficou muito bom

mrangjunboon2019 commented

i sad!:(

  • ❤️1