nader's post | Pingpad

je
Jean Ayala@jeanayala·Sep 02
the right answer is [object Object]
3
ce
Cesare@cesare·Aug 31
IMO it's not about the tests as an outcome it's about the process to get to a solution.

I use tests a discovery tool. I often don't know how the solution will look like but I most certainly always know how to start to write a test for it. It's dictated by my requirements/objectives.

My tests evolve as I discover the solution. A running tests suite is a side effect of this process.

On the other hand, if I don't have clear objectives/requirement and the goal is just gather knowledge, I don't bother with tests unless they happen to be the most convenient workbench compared to a simple script or a throwaway app.
2
ma
Mao@llmamao88·Aug 31
1
yi
yingshuolale@yingshuolale·Aug 31
gm
0
bo
boyikaoshengtian@boyikaoshengtian·Aug 31
gm
0
li
liang@qiaoliang·Aug 31
use co-pilot to generate tests
1
yo
Yoginth@yoginth·Aug 31
SoFi needs more test cases, IMO, I'm writing tests for @lenster.lens almost every day and making sure nothing should break 🤞
77
si
Sidetalker@sidetalker·Aug 31
If you can write a useful test, you should (regardless of industry). If you’re writing a test to check a box for your manager or inflate a coverage perecentage somewhere, your probably shouldn’t bother. Unfortunately, the latter seems much more common.
3
ki
Kipto | Orb@kipto·Aug 31
Writing meaningful tests is so hard.
4
pr
Princess Je$$yFries@jessyjeanne·Aug 30
Nyes
5
ja
Jake Damon@jakedamon·Aug 30
!🧢
1
ja
Jamie Alethieum@jamiealethieum·Aug 30
Seriously though, write tests! Ha!
1
ja
Jamie Alethieum@jamiealethieum·Aug 30
Haha! Sometimes you just have to accept that you will lose some money discovering bugs! You can’t test what you don’t know needs testing right!
1

About Pingpadbeta