On Wed, Aug 5, 2015 at 3:17 AM, Jan Viktorin <viktorin@xxxxxxxxxxxxxx> wrote:
> Do I understand well that you are complaining about too
> narrow commmit message?
Yes, I'm a complainer. ;-) It's minor, though, not a big deal, and
certainly not worth a re-roll if that was the only issue. In fact,
other than the undesirable "Supported:" line in the documentation, all
comments on v2 were minor and not demanding of a re-roll.
> I am trying to figure out how to write a test. It is
> not very clear to me, what the testing suite does. My
> attempt looks this way at the moment:
>
> 1657 do_smtp_auth_test() {
> 1658 git send-email \
> 1659 --from="Example <nobody@xxxxxxxxxxx>" \
> 1660 --to=someone@xxxxxxxxxxx \
> 1661 --smtp-server="$(pwd)/fake.sendmail" \
> 1662 --smtp-auth="$1" \
> 1663 -v \
> 1664 0001-*.patch \
> 1665 2>errors >out
> 1666 }
> 1667
> 1668 test_expect_success $PREREQ 'accepts SMTP AUTH mechanisms (see RFC-4422, p. 8)' '
> 1669 do_smtp_auth_test "PLAIN LOGIN CRAM-MD5 DIGEST-MD5 GSSAPI EXTERNAL ANONYMOUS" &&
> 1670 do_smtp_auth_test "ABCDEFGHIKLMNOPQRSTUVWXYZ 0123456789_-"
Wouldn't this one fail the regex check you added which limits the
length to 20 characters?
> 1671 '
> 1672
> 1673 test_expect_success $PREREQ 'does not accept non-RFC-4422 strings for SMTP AUTH' '
> 1674 test_must_fail do_smtp_auth_test "../ATTACK" &&
> 1675 test_must_fail do_smtp_auth_test "TOO-LONG-BUT-VALID-STRING" &&
> 1676 test_must_fail do_smtp_auth_test "no-lower-case-sorry"
> 1677 '
>
> * I do not know yet, what to check after each do_smtp_auth_test call.
If you were able somehow to capture the interaction with
Auth::SASL::Perl, then you'd probably want to test if it received the
whitelisted mechanisms specified via --smtp-auth, however... (see
below)
> * Perhaps, each case should have its own test_expect_success call?
The grouping seems okay as-is.
> * Why send-email -v does not generate any output?
As far as I know, git-send-email doesn't accept a -v flag.
> (I found a directory 'trash directory.t9001-send-email', however, the
> errors file is always empty.)
Was it empty even for the cases which should have triggered the
validation regex to invoke die()?
> * Is there any other place where the files out, errors are placed?
No.
> * I have no idea what the fake.sendmail does (I could see its contents
> but still...). Is it suitable for my tests?
It dumps its command-line arguments to one file ("commandline") and
its stdin to another ("msgtxt"), but otherwise does no work. This is
useful for tests which need to make sure that the command-line and/or
message content gets augmented in some way, but won't help your case
since it can't capture the script's interaction with
Authen::SASL::Perl.
> * Should I check the behaviour '--smtp-auth overrides
> sendemail.smtpAuth'?
That would be nice, but there doesn't seem to be a good way to do it
via an existing testing mechanism since you can't check the
git-sendemail's interaction with Auth::SASL::Perl. The same holds for
your question above about what to check after each do_smtp_auth_test()
call.
One possibility which comes to mind is to create a fake
Authen::SASL::Perl which merely dumps its input mechanisms to a file,
and arrange for the Perl search path to find the fake one instead. You
could then check the output file to see if it reflects your
expectations. However, this may be overkill and perhaps not worth the
effort (especially if you're not a Perl programmer).
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html