r0s

13 ms·

91.
by r0s 6y ago
Why should states have more power?
92.
by r0s 6y ago
I can heartily recommend skipping books from the "school of life" and any of their publications. I was gifted one on relationships, which is a topic I read often. I can say it was unfocused, terrible advice that seems like the aut
93.
by r0s 6y ago
I'm primarily focused on automated testing. Which is great but all revolves around test data "fixtures", standardized test data that is integrated with the system under test to be sure all the tests are using correct data. M
94.
by r0s 6y ago
Good stuff. I especially appreciate the entreaty to limit assertions and corner cases to one test concern. The only thing I didn't like was the Given When Then recommendation. BDD style story language is really meant for key specific
95.
by r0s 6y ago
I appreciate the conversation! That's interesting about RSpec, I'll read more about it, thanks.
96.
by r0s 6y ago
> it's hard to properly define when the system under test behaves unexpectedly... I feel your pain. I think at that point it's good to look deeper and ask if exceptions are being properly thrown, as I try to call for in the fi
97.
by r0s 6y ago
> You could design assertions in a very sophisticated way to minimize that problem, and optimize amount of information... but that's complex and brittle and time consuming. My point here is this optimization is really pretty simple.
98.
by r0s 6y ago
Short answer: Not all failed test coverage is invalid. Granted, unit tests benefit less from soft assertions, but I'll take a shot at an example anyway: Consider a complex object returned from a unit test result (this would be a single
99.
by r0s 6y ago
Interesting, it sounds like you would benefit from breaking each test out into one that focuses on a single target state. Another layer would be conditional test execution hierarchy where one early failure would skip a set of tests that dep
100.
by r0s 6y ago
> If the test is in a invalid state then you can't trust soft asserts that pass. Agreed, which is why I suggest designing each test for a single target state. That target may then legitimately benefit from multiple assertions, and y
101.
by r0s 6y ago
If one assertion fails early in a test, you lose any subsequent coverage from further assertions. Maybe you can build your tests such that there's only one assert for each, and if that meets your needs, fine. If not, or if you're
102.
by r0s 6y ago
Yes! I'm stoking the flames for these ideas because they were quite beneficial in my experience. In particular, the code reuse aspect, which I haven't seen any advocacy for previously.
103.
by r0s 6y ago
Thanks, I'll check it out.
104.
by r0s 6y ago
If you architect each test to have a single assertion, yes, I agree it's essentially the same effect.
105.
by r0s 6y ago
Hey Hacker News, I'm Ross Radford from Austin Texas. I've been a Senior Engineer in Test for long enough to care about this subject, and I think we'd all be better off using soft assertions, and less assertion in tests genera
106.
Making the case for fewer assertions in tests(assertless.org)
16 points by r0s 6y ago|32 comments
107.
by r0s 6y ago
Hey Hacker News, I'm Ross Radford from Austin Texas. I've been a Senior Engineer in Test for long enough to care about this subject, and I think we'd all be better off using soft assertions, and less assertion in tests genera
108.
Making the case for fewer assertions in tests(assertless.org)
2 points by r0s 6y ago|1 comments
109.
by r0s 6y ago
This feels like a Wired article from 2003.
110.
by r0s 6y ago
Supply has never been the problem with feeding the world. More supply solves nothing.
111.
by r0s 6y ago
Talk to your potential customers. Maybe you have doubts that are very real reasons you shouldn't start.
112.
by r0s 6y ago
On the contrary, there's not a lot of money to be made, and people constantly question it. Would-be spoilers get educated about their own unrealized bias, racism continues to be a huge problem in this country, activists are vindicated
113.
by r0s 6y ago
> Suppose you're right. Easy to verify, why suppose anything? > censorship? On a privately owned site? Try again.
114.
by r0s 7y ago
Try gitlab.
115.
by r0s 10y ago
Such as parenthood?
116.
by r0s 11y ago
For me the hardest part of management is letting go of control, especially when the habit of asking the lead for advice is necessarily ingrained in junior developers. What works for me is getting in tune to my annoyance and identifying oppo
117.
by r0s 11y ago
Like a transporter on Star Trek, I'm afraid there would be no upload without a copy. Could we really then delete the original?
118.
by r0s 11y ago
Cognitive science and human computer interface research. 1) Every problem you're working on will be improved by better learning systems. 2) The direct challenger to AI's potential is human augmentation. There's an evolving
119.
by r0s 11y ago
The smugness thing really hits home. Sometimes clueless, overconfident or downright negligent people are so embedded in a culture that an outside expert opinion is exactly what's needed. Thanks for the reply.
120.
by r0s 11y ago
I think the arguments against penetration testing are interesting. As a software test engineer, we do external audits like this, but I wonder: Documented or "known" vulnerabilities are not worth testing until there are systems

More ›