Earlier quoted context omitted.
> What's the gap between a Co-pilot written test and a human-written test? IMHO the gap is that human-written test understands the (unwritten) specification (which might be as simple as "program doesn't crash"), and tests the program against it. I am of the (pretty radical, it seems) opinion that the (especially unit) tests that just take the code as the specification, instead of having specification coming from else…
Do you know of any good resources to read about testing? How did you learn what you know?
Increasing QA maturity level:
– B.Beizer – „Black-box testing“ ($), „SW testing techniques“ ($)
– ISTQB Foundation level
– RTCA DO-178C ($) / EUROCAE ED-12C ($), DO-248C
– Joint Software Systems Safety Engineering Handbook
Test analysis specification-based techniques (EP, BVA, EP DI, STT, TCl):
– ISTQB „Advanced Test Analyst“, „Advanced Technical Test Analyst“ courses and Syllabi
– BS 7925-2 „Standard for SW Component testing”, ISO/IEC/IEEE 29119-4:2015 „Test techniques” ($)
– IEEE 829:2008 „Standard for SW testing documentation” ($)
Test analysis failure/risk-based techniques (FMEA, FTA, RCA):
– C.Wilhelmsen, L.T.Ostrom – „Risk Assessment: Tools, Techniques, and Their Applications” ($)
– C.S.Carlson – „Effective FMEAs” ($)
– MIL-STD-1629A „Procedures for performing FMEA”
– NUREG-0492 „Fault Tree Handbook”
– NASA Fault Tree Handbook with Aerospace Applications
– DOE-HDBK-1208-2012 Volume 1 „Accident and Operational Safety Analysis Techniques”
– TOR-2014-02202 „RCA Best Practices Guide” ($)