U.S. Torpedo Troubles During World War II (1998)

Post by [deleted] » Fri, Jan 17, 2020, 3:59 PM UTC

quotemstr wrote: post #43

mmhsieh wrote: post #11

Earlier quoted context omitted.

The logic behind test bans (in conjunction with numerical caps on warheads) is to create uncertainty in the reliability of one's own arsenal to discourage either side from contemplating a first-strike.

I'm not sure about that. What if you're convinced that your brilliant scientists have created working warheads while you think the enemy's dolts haven't been able to keep their arsenal working? What if your enemy thinks the same thing in reverse? I think there's always a temptation to overestimate one's own capability and underestimate the sophistication of others.

[deleted]

Post by penagwin » Fri, Jan 17, 2020, 4:22 PM UTC

cryptonector wrote: post #85

penagwin wrote: post #16

Earlier quoted context omitted.

Depends on the type of test. What you guys are talking about are unit tests, and are designed to test individual methods/functions. You write a separate test for each one. There's other types of testing, integration tests sound like what you are both complaining about. Integration tests test the interaction between components of a system, and are thus far more complex and likely to break as you're developing (which i…

But you also have to test the whole system.

For sure. There's dozens of types of tests (although many don't apply to certain use cases). In a healthy system you should be using a lot of them. And they don't stop at deployment, you need to be tracking exceptions (after all, production is the final, and best test environment).

This article has some nice diagrams of the different kinds of tests https://medium.com/@copyconstruct/testing-in-production-the-...

Re: U.S. Torpedo Troubles During World War II (1998)

Re: U.S. Torpedo Troubles During World War II (1998)