What is Continuous Testing?

[@1love1heart1light]

Eric's video's are the best. He's a great teacher. The other teachers I have to watch a few times or research knowledge gaps they left out.

[@ericminick1700]

You're too kind. Thank you!

[@mocaloca]

Would love to go even deeper in this topic. Any recommendations?

[@tib7209]

what if i have a large application without any tests and i want to write tests for it? is the traditional approach more appropriate?

[@EricMinick]

You want to work towards the mix suggested in the video. Starting with some automated functional and API tests makes sense since a small number of tests can provide you insight into whether the key use cases seem to still work. That's super valuable. However, you want the developers to start writing unit tests around whatever code they are touching. If some code is never touched, it may never get a unit test, but you'll start getting tests where the changes are and that's where they're most valuable.

[@marishte]

every time somebody mentions test pyramid, a kitten dies

[@ericminick1700]

Can I clap and bring them back like you can with faeries? More seriously, what's your objection to the pyramid framing?

[@shirkhanaslanzade982]

thank you very much

[@IBMTechnology]

You're welcome, Shirkhan, thanks for watching! 🙂

[@Zivenshy]

Where is he writing on?

[@porkbun5080]

If you're using a VR headset, he's writing on your eyes so it slowly seeps into your head so you can remember

[@EricMinick]

It's a sheet of semi-thick, clear glass. By lining the edges with LEDs, you get a bit of a glowing effect when you write on it with dry-erase markers.

[@Chris-jm2gx]

He's obviously writing on air, he's a wizard.

[@Deters0n]

wait, is he writing backward?

[@shreejashetty4570]

Deters0n 😂

[@WeWalkAI]

They flip the screen horizontally I think. He is, most probably, right handed :)

[@sheksbear]

The video is flipped

[@kingofcampbell6413]

maybe we should have more layers of tests in the pyramid test structures.

[@ericminick1700]

Performance, useability, penetration, etc, etc, etc. They're all real. The principles are the same though. The more you can do against stable surfaces like APIs the better. The more you can do quickly, the better. The expensive testing needs to be done judiciously. You can apply this directly to security land as well. Static code scans are relatively cheap, active scans less so, manual white-hat penetration tests are very expensive. You want all of it, but optimize for cheap and fast.