Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Test that specifying encryption explicitly works | Tom Ryder | 2017-10-20 | 1 | -0/+1 |
| | |||||
* | Add test of custom name in constructor | Tom Ryder | 2017-10-20 | 1 | -0/+1 |
| | |||||
* | Add test that signing requires key and passphrase | Tom Ryder | 2017-10-18 | 1 | -0/+1 |
| | |||||
* | Add encrypt-sign build test | Tom Ryder | 2017-10-18 | 1 | -0/+1 |
| | |||||
* | Add more tests, bump versionv0.06 | Tom Ryder | 2017-10-18 | 1 | -1/+1 |
| | | | | | | | This is still really only testing that the object constructed in the right way and is providing the expected interface and internals as functions. It needs to actually run as much as possible. I still have to figure out how to mock that up cleanly. | ||||
* | Add a test of `mailto` constructor requirement | Tom Ryder | 2017-10-18 | 1 | -0/+1 |
| | |||||
* | One basic test to start: can we instantiate? | Tom Ryder | 2017-10-14 | 1 | -0/+1 |
| | |||||
* | Add dedicated LICENSE file | Tom Ryder | 2017-10-14 | 1 | -0/+1 |
| | |||||
* | Rename/separate out into app and module | Tom Ryder | 2017-10-05 | 1 | -6/+6 |
| | | | | | | | | | | | This still needs a lot more work before release. In particular, I have to figure out what I'm going to do about the `passphrase` option. It's probably better to both not require it, in which case no signing is done (only encryption), and to instead allow a path to a file to be specified. The other big puzzle would be how on earth to write automated tests for it... I may end up imitating however Mail::GnuPG is testing itself. | ||||
* | Add Module::Starter boilerplate for perlmodding | Tom Ryder | 2017-10-05 | 1 | -0/+9 |