1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
**bash unit testing enterprise edition framework for professionals **
If you like bash_unit and want to contribute, you can do so in one of the
following ways (order might matter).
# Spread the word
Talking about bash_unit is a very welcomed contribution.
Share your success with bash_unit on your blog, twitter, stackoverflow...
Nice words to share your experience with bash_unit is always appreciated.
If you want to say something nice about bash_unit but can not think of a
place for that right now, just add a comment to
[issue #37](https://github.com/pgrange/bash_unit/issues/37).
Starring the project is also appreciated.
# Suggest improvements
When you see something that is not working with bash_unit, or if you feel
something is missing, open an
[issue](https://github.com/pgrange/bash_unit/issues).
Opening issues helps improving bash_unit.
# Contribute code
If you use a tool like bash_unit, odds are high that you already heard
about software development. Just code the improvement you have in mind
and create a pull-request.
You can contribute with new features you think are missing but you can
also find inspiration with the
[open issues](https://github.com/pgrange/bash_unit/issues) of bash_unit.
See [how to contribute code](CONTRIBUTING_CODE.md).
# Donate
bash_unit is free software I develop during my (not so) free time. If you feel
bash_unit is helpful enough to you that you want to compensate for some of
the time spent developing or promoting it, you can contribute with your money
on liberapay:
[](https://liberapay.com/bash_unit/donate)
|
