openssl/test/recipes/90-test_external.t
Matt Caswell 06e452fbc1 Use the -allow-unimplemented feature of the BoringSSL runner
That way we can remove flags that we don't support

Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-11-04 10:38:54 +00:00

42 lines
1.3 KiB
Perl

#! /usr/bin/env perl
# Copyright 2015-2016 The OpenSSL Project Authors. All Rights Reserved.
#
# Licensed under the OpenSSL license (the "License"). You may not use
# this file except in compliance with the License. You can obtain a copy
# in the file LICENSE in the source distribution or at
# https://www.openssl.org/source/license.html
use OpenSSL::Test;
use OpenSSL::Test::Utils;
use OpenSSL::Test qw/:DEFAULT srctop_file cmdstr/;
setup("test_external");
if (!$ENV{BORING_RUNNER_DIR}) {
plan skip_all => "No external tests have been detected";
}
plan tests => 1;
indir $ENV{BORING_RUNNER_DIR} => sub {
ok(filter_run(cmd(["go", "test", "-shim-path",
srctop_file("test", "ossl_shim", "ossl_shim"),
"-shim-config",
srctop_file("test", "ossl_shim", "ossl_config.json"),
"-pipe", "-allow-unimplemented"])),
"running external tests");
}, create => 0, cleanup => 0;
# Filter the output so that the "ok" printed by go test doesn't confuse
# Test::More. Without that it thinks there has been one more test run than was
# planned
sub filter_run {
my $cmd = cmdstr(shift);
open(PIPE, "-|", $cmd);
while(<PIPE>) {
print STDOUT "go test: ", $_;
}
close PIPE;
}