Testing Async Systems
|Testing Async Systems|
| Convenor: Phil Shotton
Tasos, Stylianos Ntilis, Giannis Skitsas
An open discussion about system testing, what we test, how we test and why we test, and the challenges of testing large distributed systems.
What is Testing / Why do it?
0/ Functional requirements
1/ Failure Prevention
2/ Regression Testing and to help refactoring
3/ Better Code by Design
4/ Cost - changing code whilst writing is easy and cheap. Cost to fix
How do we test?
Unit Tests - Component Class level -------> Compnent Integration ------> Staging -------> Functional / Integration ------------------------------->Testing During Production
Most ppl don't do enough tests and Code fails
Requirements - when the requirements aren't specified properly, it impacts the functional tests
It all comes down to resources available
We also have the non-functional requirements such as performance.
In Software dev, you have too many interconnects, you can't like engineering test the whole end to end.We have to break up and test the bits individually.
Should we test each part individually? at the API/interconnect level?
How do you design a good test?
Cost is the excuse why it isn't done It would be good to track why the manager who said we don't need tests, because we don't have time, capture that as a functional requirement