←back to thread

"Widevine Dump":Leaked Code Downloads HD Video from Disney+, Amazon, and Netflix

(torrentfreak.com)
449 points bertman | 5 comments | 27 Dec 21 12:55 UTC | HN request time: 0s | source
Show context
bertman ◴[27 Dec 21 13:05 UTC] No.29702169[source]▶
The repos: https://github.com/widevinedump?tab=repositories
replies(1): >>29702805 #
sovietmudkipz ◴[27 Dec 21 14:39 UTC] No.29702805[source]▶
I don’t know why but for some reason I was hopeful to see unit tests in any of the repos. Searching “test” for that user doesn’t reveal any tests. :(

Even the digital property liberators/internet pirates don’t test their software. I feel like I’m on an island with a small population of test enthusiasts.

replies(4): >>29703006 #>>29703066 #>>29703153 #>>29703226 #
1. boppo1 ◴[27 Dec 21 15:27 UTC] No.29703226[source]▶
What's the best place to get started with testing? As a newbie brogrammer it's intimidating enough writing software that works, let alone suites to comprehensively test it. Is there a testing 'bible'?
replies(4): >>29703264 #>>29703627 #>>29704108 #>>29708559 #
2. corndoge ◴[27 Dec 21 15:31 UTC] No.29703264[source]▶
You'll fare much better in today's software industry climate if you don't use the word brogrammer
3. hatware ◴[27 Dec 21 16:09 UTC] No.29703627[source]▶
Build systems that break, the tests come naturally after that.
4. Godel_unicode ◴[27 Dec 21 16:53 UTC] No.29704108[source]▶
There are many deeply held beliefs that people have about testing, so I recommend reading many different takes on how to structure your testing approach. For the pragmatic python programmer, Brian's book is quite good as a starting place:

https://pragprog.com/titles/bopytest/python-testing-with-pyt...

5. codedokode ◴[28 Dec 21 00:09 UTC] No.29708559[source]▶
I cannot recommend a book or an article, but just wanted to give an idea: automated testing is when you make a script do what a human tester would do. So maybe you should read about testing software in general. How test planning is done, how do you choose test cases.

You start with listing requirements (what a program/a class/a function is expected to do or not to do) and then write tests that verify that it is indeed so.

The easiest thing is writing unit tests. Pick a function, define requiremens and write a test for every requirement. If your code is not very modular and it is difficult to isolate a class or a function in order to test it, then maybe you should refactor the code first.