ABOUT SOFTWARE TESTING
Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.[1] Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include the process of executing a program or application with the intent of finding software bugs (errors or other defects), and verifying that the software product is fit for use.
TYPICAL COMMANDLINE RELATED EXPOSURE
[bash]
$sudo ./cyclictest –smp -p95 -f -b 200
# /dev/cpu_dma_latency set to 0us
INFO: debugfs mountpoint: /sys/kernel/debug/tracing/
could not set ftrace_enabled to 1
Requested tracer ” not available
could not set tracing_max_latency to 0
policy: fifo: loadavg: 0.16 0.24 0.17 1/364 16976
T: 0 (16976) P:95 I:1000 C: 2902 Min: 7 Act: 15 Avg: 20 Max: 169
# Thread Ids: 16976
# Break thread: 16976
# Break value: 246
could not set ftrace_enabled to 0
[/bash]
[bash]
$sudo ./cyclictest –smp -p95 -f -b 100
# /dev/cpu_dma_latency set to 0us
INFO: debugfs mountpoint: /sys/kernel/debug/tracing/
could not set ftrace_enabled to 1
Requested tracer ” not available
could not set tracing_max_latency to 0
policy: fifo: loadavg: 0.27 0.15 0.14 2/361 16999
T: 0 ( 0) P:95 I:1000 C: 0 Min:1000000 Act: 0 Avg: 0 Max: 0
# Thread Ids: 16999
# Break thread: 16999
# Break value: 161
could not set ftrace_enabled to 0
[/bash]
[bash]
$sudo ./cyclictest –smp -p95 -f -b 1000
# /dev/cpu_dma_latency set to 0us
INFO: debugfs mountpoint: /sys/kernel/debug/tracing/
could not set ftrace_enabled to 1
Requested tracer ” not available
could not set tracing_max_latency to 0
policy: fifo: loadavg: 0.17 0.14 0.14 3/361 17002
T: 0 (17002) P:95 I:1000 C: 35587 Min: 7 Act: 32 Avg: 20 Max: 264
^C# Thread Ids: 17002
could not set ftrace_enabled to 0
$
[/bash]
LINKS
https://events.static.linuxfound.org/sites/events/files/slides/cyclictest.pdf
https://en.wikipedia.org/wiki/Software_testing