git: 5c0cf55f158b - main - devel/venom: new port

The branch main has been updated by bapt:

URL: https://cgit.FreeBSD.org/ports/commit/?id=5c0cf55f158bd29c06f75912b69f1d890cff3e42

commit 5c0cf55f158bd29c06f75912b69f1d890cff3e42
Author:     Baptiste Daroussin <bapt@FreeBSD.org>
AuthorDate: 2024-03-29 09:16:05 +0000
Commit:     Baptiste Daroussin <bapt@FreeBSD.org>
CommitDate: 2024-03-29 09:32:33 +0000

    devel/venom: new port
    
    Venom allows you to handle integration tests the same way you code your
    application. With Venom, testcases will be managed as code: the readability of
    the tests means that the tests are part of the code reviews. Thanks to that,
    write and execute testsuites become easier for developers and teams.
    
    Concretely, you have to write testsuite in a YAML file. Venom run executors
    (scripts, HTTP Request, web, IMAP, etc.) and apply assertions. It can also
    generate xUnit result files
---
 devel/Makefile        |  1 +
 devel/venom/Makefile  | 20 ++++++++++++++++++++
 devel/venom/distinfo  |  5 +++++
 devel/venom/pkg-descr |  8 ++++++++
 4 files changed, 34 insertions(+)

diff --git a/devel/Makefile b/devel/Makefile
index 7ebd060da030..d7e485d6c5d5 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -7932,6 +7932,7 @@
     SUBDIR += vc
     SUBDIR += vc-intrinsics
     SUBDIR += vcglib
+    SUBDIR += venom
     SUBDIR += vera++
     SUBDIR += vexcl
     SUBDIR += viewvc-devel
diff --git a/devel/venom/Makefile b/devel/venom/Makefile
new file mode 100644
index 000000000000..f80158eca53f
--- /dev/null
+++ b/devel/venom/Makefile
@@ -0,0 +1,20 @@
+PORTNAME=	venom
+PORTVERSION=	1.2.0
+DISTVERSIONPREFIX=	v
+CATEGORIES=	devel
+
+MAINTAINER=	bapt@FreeBSD.org
+COMMENT=	Manage and run integration tests with efficiency
+WWW=		https://github.com/ovh/venom
+
+LICENSE=	APACHE20
+LICENSE_FILES=	${WRKSRC}/LICENSE
+
+USES=		go:modules
+
+GO_MODULE=	github.com/ovh/venom
+GO_TARGET=	./cmd/venom
+
+PLIST_FILES=	bin/venom
+
+.include <bsd.port.mk>
diff --git a/devel/venom/distinfo b/devel/venom/distinfo
new file mode 100644
index 000000000000..c6ca6b961420
--- /dev/null
+++ b/devel/venom/distinfo
@@ -0,0 +1,5 @@
+TIMESTAMP = 1711703192
+SHA256 (go/devel_venom/venom-v1.2.0/v1.2.0.mod) = 494cf21d1b8fd84af689bf23ad1cce2f984153f9efb4b01cc64d4ffd14da6132
+SIZE (go/devel_venom/venom-v1.2.0/v1.2.0.mod) = 5294
+SHA256 (go/devel_venom/venom-v1.2.0/v1.2.0.zip) = 4cbabd5c826f09dbaff1d83852dee6f6ce8af86ec6adcd5df4d1a584d416ff93
+SIZE (go/devel_venom/venom-v1.2.0/v1.2.0.zip) = 687085
diff --git a/devel/venom/pkg-descr b/devel/venom/pkg-descr
new file mode 100644
index 000000000000..f9b28031e82f
--- /dev/null
+++ b/devel/venom/pkg-descr
@@ -0,0 +1,8 @@
+Venom allows you to handle integration tests the same way you code your
+application. With Venom, testcases will be managed as code: the readability of
+the tests means that the tests are part of the code reviews. Thanks to that,
+write and execute testsuites become easier for developers and teams.
+
+Concretely, you have to write testsuite in a YAML file. Venom run executors
+(scripts, HTTP Request, web, IMAP, etc.) and apply assertions. It can also
+generate xUnit result files