|
Software is pure abstraction ether. Frivolous, fleeting, and exponential spirit makes the programming inherently and largely E R R O R - p r o n e .
|  |
When breaking changes are as close as fingers to the keyboard, commits can be rolled back, and there's always a gap until delivery to production (for last-minute fixes or bug introduction) software is Q A - f a t e d .
|
QA couldn't exist without errors - the catch-all term which inmates deserved their own corner.
---
config:
look: handDrawn
theme: neutral
---
graph TB
c1-->QA2
subgraph "<h3><a href="https://github.com/Kyriosity/read-write/tree/main/README%2B/software/tests">Programmatic Tests</a></h3>"
c1("<b>Proof</br>coverage</b>")
TDD("<b>Test driven</b>")-->TDDev("Development")
TDD-->TDDes("Design")
c1 o--o TDDev
end
subgraph "<h3>Quality Assurance</h3>"
a1(<b>Code</b>)-->a2(<a href="https://github.com/Kyriosity/read-write/blob/main/README%2B/software/QA/README+/code-quality.md">Quality</a>)
a1-->a3("Review")
T1("<b>Testing</b>")-->QA1("Manual")
T1("<b>Testing</b>")-->QA2(Automated)
end
There were and will be remarkable works done from scratch without allotted proof and validation measures (let alone code reviews and test automation) but robust from the first release. This may (and may not) happen in localized high-pro teams of responsible individuals but is an exclusion to underline the must-have of QA.
Coding cleanly and qualitatively must be the primary goal, but teams will be uneven, distributed / fluctuating, and stressed. Add human nature to sweep problems under the carpet—it is quite big and thick in the software.
Experience in
- domain/subjects,
- tools (as a platform and programming language),
- fails and retreats (also of others).
When security risks are a concern other approaches for hacking vulnerability come into play (and devs aren't writing code in a criminal-minded mode). Protrude this statement to all other cases where IT pundits don't have all the expertise to test the domain.
 |
These are continuous measures within teams:
|
Customer feedback is the top mark (not only on the positive scale) and not every user is eager to share it.
Tests and Testing are a CENTERPIECE of QA and w i d e umbrella terms for the check of code and its products (including documentation). Bug searching and quality proofing tests are optional but highly recommended and a natural share of software creation.
Opening this page was your manual test.
Unlike the olden days with blind commits of punchcards and tapes most development allows one to evaluate its product (in whole or by feature) with every step and at time: just build and run.
Responsible developers are the primary, most prepared, most effective, and critical testers.
Executable code routines - are the biggest cornerstone of modern QA. Automation of their run - fundament of continuous quality and safety.
___________
🔚 ... continued in ... Errors . . . Code quality . . . Tests for QA ... Pitfalls . . . TDD