2 commits
| Author | SHA1 | Date | |
|---|---|---|---|
78f57c7547
|
|||
|
f4d40efc05
|
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
78f57c7547
|
jw.pkg.lib.Result: Add unit test
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 4m28s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m10s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 3m43s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m58s
CI / Packaging test (push) Successful in 0s
Add a unit test for the Result class covering: - stdout/stderr property access with various status values - None output handling and exception behavior - Encoding and strip_output property setters - cmd and wd setters - summary, summarize, and __repr__ behavior - matches_error pattern matching Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
|
f4d40efc05
|
test: Move unit tests below jw/pkg
Move the unit test hierarchy to below test/unit/python/jw/pkg. Nesting the subdirectories so deeply might be overly careful, but it may as well be not - maybe in the future installable test packages are going to be generated and need simple ways to install without stepping onto each other's toes. If not, it's easier to cut two directory components out than having to reorganize possibly incoherent paths grown over multiple packages. Signed-off-by: Jan Lindemann <jan@janware.com> |