summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAge
* Implement DayLongEventModel and integrate it to the calendarRémi Nicole2018-05-15
| | | | | | | | | | | | | | Summary: Fixes T8697 Reviewers: cmollekopf Reviewed By: cmollekopf Tags: #kube Maniphest Tasks: T8697 Differential Revision: https://phabricator.kde.org/D12875
* Add calendar support in the Test StoreRémi Nicole2018-04-17
| | | | | | | | | | | | | | Summary: Fixes T8483 Reviewers: cmollekopf Reviewed By: cmollekopf Tags: #kube Maniphest Tasks: T8483 Differential Revision: https://phabricator.kde.org/D12087
* Avoid actually sending out mails.Christian Mollekopf2018-03-23
|
* Automatic key import / export + Expected monadRémi Nicole2018-03-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: There are many things going on here (perhaps a bit much for a single patch): - When an attachment is of mime type "application/pgp-keys", a button is added to import the key to GPG - When sending a mail and crypto is enabled (encryption, signing or both), the public key of the first private key found is sent as an un-encrypted attachment (T6994) - The `mailcrypto.{h,cpp}` was, for the most part, rewritten - Introduction of the expected monad, inspired by what was proposed for C++ [here](https://isocpp.org/files/papers/n4015.pdf), but not at all a strict implementation of this specification. We may want to add some more features of this standard later. The rationale for some of the choices: - I found mailcrypto a bit hard to edit to add new features, and a great part was commented code to prepare for the support the SMIME crypto format, which would (in my current knowledge) not be used for sending emails. - One thing I found that may be missing in the code base was a standardized way of handling errors in C++ code. Since exceptions are disabled I think that the functional way is the way to go. After some research I found the Expected monad / tagged union / sum type, which seemed to suit the problem particularly well. In the long run, I hope we would move the entire code base to use `Expected` to indicate if a function might fail. Of course every choice made here is to be considered as a proposition for doing things / RFC, critics wholeheartedly accepted. Reviewers: cmollekopf Tags: #kube Maniphest Tasks: T6994, T8147, T6995 Differential Revision: https://phabricator.kde.org/D11158
* Improvements of the log viewRémi Nicole2018-02-26
| | | | | | | | | | | | | Summary: - Add a test view for the log view - Allow passing the `entities` part of Sink messages - That allowed getting information about which mail could not be sent in sink transmission errors Reviewers: cmollekopf Reviewed By: cmollekopf Differential Revision: https://phabricator.kde.org/D10861
* Demonstrate reflow problemsChristian Mollekopf2018-02-23
| | | | | | | | | ...and cleanup the sizes of the text/html part a bit. Html content with a <pre> tag, such as inserted by an apple mail reply, is not reflowed in the TextEdit (it is in the WebEngineView). And that causes the text edit to run off the side of the conversation view.
* Use the new changes regarding aggregated properties.Christian Mollekopf2018-02-22
| | | | This fixes marking partially unread threads as read.
* Ensure that we can load replies.Christian Mollekopf2018-01-31
| | | | The webengine based code we use to create replies needs a QApplication.
* Tested account setupChristian Mollekopf2018-01-24
|
* More conversationview testingChristian Mollekopf2018-01-11
|
* Test some basic properties of outgoing mailsChristian Mollekopf2018-01-11
|
* Create thread for conversationviewChristian Mollekopf2018-01-11
|
* InboxCrusher testsetupChristian Mollekopf2018-01-10
|
* Inherit folder id (we can't hardcode it)Christian Mollekopf2018-01-10
|
* Run views with a test dataset using TestStore.Christian Mollekopf2018-01-10
| | | | | This allows us to start the view using qmlscene with a testdata set that is created in a test datastore (isolated from the regular data).
* Composertest with TestStoreChristian Mollekopf2018-01-08
|
* Dynamically setup initial test stateChristian Mollekopf2018-01-08
|
* Composer testChristian Mollekopf2018-01-08
|
* Basic test harness for viewsChristian Mollekopf2017-12-19
|
* Use a separate sink test environmentChristian Mollekopf2017-12-19
| | | | Otherwise the systems sink config and data is used.
* Moved tests to the relevant componentChristian Mollekopf2017-12-19
|
* Do what the QUICK_TEST_MAIN macro doesChristian Mollekopf2017-12-02
|
* Merge logentries by subtype if availableChristian Mollekopf2017-10-26
|
* Prepare logview for error merging.Christian Mollekopf2017-10-25
|
* Test that we start into the account wizardChristian Mollekopf2017-10-06
|
* The grand cmake cleanupChristian Mollekopf2017-08-23
| | | | | | We had a ton of duplication in our cmake code because we had no common toplevel settings. This is now cleaned up so we can sanely change settings and so we know what we have set.
* Use imported targets instead of qt5_use_modulesHeiko Becker2017-07-29
| | | | | | | | | | | | | | | | | | From Qt's documentation: "This macro is obsolete. Use target_link_libraries with IMPORTED targets instead." It's only recommended with cmake >=2.8.9 & < 2.8.12. Kube already requires cmake 3.0. One advantage of using the imported targets is, that cmake complains if a target isn't found before it's used, like Qt5Concurrent missing from the find_package_call here. Reviewers: #kube, cmollekopf Reviewed By: #kube, cmollekopf Subscribers: #kube Differential Revision: https://phabricator.kde.org/D6362
* One QT_MIN_VERSION is enough, also it's 5.7Christian Mollekopf2017-07-05
|
* kube-mail is now kubeChristian Mollekopf2017-04-05
|
* Normalize the component package structureChristian Mollekopf2017-02-20