Skip to content
#

crate

Here are 203 public repositories matching this topic...

jonhoo
jonhoo commented Nov 23, 2018

A fellow tester! How exciting! Welcome!

Since #102, the imap crate gained the ability to run full IMAP integration tests against a "real" IMAP server (GreenMail) running in a Docker container. That server supports both SMTP (for sending mail) and IMAP (for receiving them), and is particularly well suited for testing as it automatically creates accounts as

gak
gak commented Mar 23, 2021

Right now there's no way of seeing a wallet's phrase or private key via the CLI. The private key is visible via the wallet file, but not the phrase--it uses an Entropy rather than saving the words.

It would be good to have a command, e.g.:

> feeless wallet secret --id

The output would vary depending on the wallet type:

> feeless wallet secret --id xxx # phrase, must match 
lighthouse
finnkauski
finnkauski commented Aug 23, 2020

Is your feature request related to a problem? Please describe.
This basically relates to the fact that the bridge as of now is not fully tested because we need to mock request calls to a bridge with our own bridge somehow in order to be able to test.

Describe the solution you'd like
This could be implemented in the form of a bridge tester struct that spins up its own thread and liste

ralpha
ralpha commented Oct 15, 2021

There are many places where .unwrap() is currently called.
These should be removed or replaces with the correct error handing or .expect(...) if it is very clear that it could not be triggered.

This is not needed for tests, unwrap is fine in those cases.
The effort should be mainly focused on the rrule/src/iter and rrule/src/parser folder.

Improve this page

Add a description, image, and links to the crate topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the crate topic, visit your repo's landing page and select "manage topics."

Learn more