details:
https://github.com/nginx/njs/commit/29c71bf771a30e8120bf332f240c14257000dd05
branches: master
commit:29c71bf771a30e8120bf332f240c14257000dd05
user: Dmitry Volyntsev
date: Thu, 18 Jul 2024 22:37:25 -0700
description:
Tests: making exception test more portable in js.t
details:
https://github.com/nginx/njs/commit/3ac496802862347c5cf8f0b6e3825163dc7bb1c9
branches: master
commit:3ac496802862347c5cf8f0b6e3825163dc7bb1c9
user: Dmitry Volyntsev
date: Thu, 25 Jul 2024 17:28:37 -0700
description:
Tests: adapting unsafe redirect test for QuickJS
details: https://hg.nginx.org/njs/rev/7c671d50f646
branches:
changeset: 2348:7c671d50f646
user: Dmitry Volyntsev
date: Wed May 29 22:26:09 2024 -0700
description:
Test262: fixed unstable fs test.
Ensuring that symlink file is removed even if regular file does not
exist.
diffstat
details: https://hg.nginx.org/nginx/rev/31fe21f04103
branches: stable-1.26
changeset: 9259:31fe21f04103
user: Edgar Bonet
date: Thu May 16 11:15:10 2024 +0200
description:
Configure: fixed building libatomic test.
Using "long *" instead of "AO_t *" leads eith
details: https://hg.nginx.org/nginx/rev/f58b6f636238
branches:
changeset: 9247:f58b6f636238
user: Edgar Bonet
date: Thu May 16 11:15:10 2024 +0200
description:
Configure: fixed building libatomic test.
Using "long *" instead of "AO_t *" leads either to -Wincomp
# HG changeset patch
# User Piotr Sikora
# Date 1714589827 0
# Wed May 01 18:57:07 2024 +
# Node ID 2d5e754e3a4e7a59eaf7f653ad4fd5346f53eab4
# Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43
Configure: postpone running the test binary.
Previously, the ./configure script would attempt
# HG changeset patch
# User Piotr Sikora
# Date 1714589815 0
# Wed May 01 18:56:55 2024 +
# Node ID 787e1adea9aa7f681884657f119e864af0be3e0d
# Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43
Configure: build C++ test module using C++ compiler.
This fixes build when using C compiler
# HG changeset patch
# User Piotr Sikora
# Date 1714589692 0
# Wed May 01 18:54:52 2024 +
# Node ID df39b5d3c3a0c670f3d94e623351b6c659f5be84
# Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43
Configure: always test with provided C compiler options.
Previously, build in auto/include
# HG changeset patch
# User Piotr Sikora
# Date 1714589524 0
# Wed May 01 18:52:04 2024 +
# Node ID 0d5498e86bf8a7f119ed83dbc0789be37d728334
# Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43
Configure: test --with-cc-opt options.
Previously, invalid C compiler options would fail
details: https://hg.nginx.org/nginx/rev/fb989e24c60a
branches:
changeset: 9230:fb989e24c60a
user: Sergey Kandaurov
date: Mon Feb 26 20:00:38 2024 +
description:
Configure: fixed Linux crypt_r() test to add libcrypt.
Previously, the resulting binary was successfully linked
;
#Session resumption - Session ID
ssl_session_tickets off;
ssl_session_cache shared:SSL:10m;
#Session resumption - Session Tickets
ssl_session_tickets on;
ssl_session_cache off;
After set each one, I can test if they are active using the following
command and check Session-ID or TLS session ticket
y_depth.t, failing 13/17 and 3/11 tests respectively
> with the same error:
>
> ```
> # Failed test 'verify depth 2 - end'
> # at ssl_verify_depth.t line 169.
> # 'HTTP/1.1 400 Bad Request
> # Server: nginx/1.24.0
> # Date: Fri, 26 Jan 2024 01:08:1
Hey Maxim,
Thanks, I installed homebrew’s Perl and all these tests are passing now, woohoo!
However a few others are failing now including ssl_ocsp.t and
ssl_verify_depth.t, failing 13/17 and 3/11 tests respectively with the same
error:
```
# Failed test 'verify depth 2 - end
for nginx-tests? I might be setting up perl wrong.
From: Sergey Kandaurov
Date: Wednesday, January 24, 2024 at 2:59 PM
To: nginx-devel@nginx.org
Cc: Mayerhofer, Austin
Subject: [EXTERNAL] Re: Nginx-tests stream_ssl_conf_command.t test hanging
indefinitely
> On 25 Jan 2024, at 01:15, Mayerho
> On 25 Jan 2024, at 01:15, Mayerhofer, Austin via nginx-devel
> wrote:
>
> Hi all,
> Apologies if I sent this twice, I don’t think the first one went through
> because I wasn’t subscribed to the list.
> nginx-tests’ stream_ssl_conf_command.t is hanging for me and not running to
>
:
```
TEST_NGINX_BINARY=/usr/local/nginx/sbin/nginx prove -v stream_ssl_conf_command.t
```
The output is:
```
stream_ssl_conf_command.t ..
1..5
ok 1 - Certificate
ok 2 - SessionTicket
ok 3 – ServerPreference
```
And it hangs there. It seems to be something with the ServerPreference test, as
if I remove this code
details: https://hg.nginx.org/njs/rev/e4105b65d105
branches:
changeset: 2234:e4105b65d105
user: Dmitry Volyntsev
date: Wed Nov 15 15:08:18 2023 -0800
description:
Tests: added console test for stream module.
diffstat:
nginx/t/stream_js_console.t | 142
test to make sure i'm good..
___
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
e8231c9805d50abcb5
> Tests: added has_feature() test for CryptX.
>
> diff --git a/h3_absolute_redirect.t b/h3_absolute_redirect.t
> --- a/h3_absolute_redirect.t
> +++ b/h3_absolute_redirect.t
> @@ -23,10 +23,7 @@ use Test::Nginx::HTTP3;
> select STDERR; $| = 1;
> select S
# HG changeset patch
# User Sergey Kandaurov
# Date 1685028552 -14400
# Thu May 25 19:29:12 2023 +0400
# Node ID 4dad7cf8ebe807f9230a82dde5fc02b5e12e390b
# Parent acd68670b0649da2fbcfd3e8231c9805d50abcb5
Tests: added has_feature() test for CryptX.
diff --git a/h3_absolute_redirect.t b
details: https://hg.nginx.org/njs/rev/e7aedbc18246
branches:
changeset: 2128:e7aedbc18246
user: Dmitry Volyntsev
date: Fri May 19 21:29:23 2023 -0700
description:
Removed leftover String.prototype.toBytes() from benchmark test.
The String.prototype.toBytes() and friends were
# HG changeset patch
# User Maxim Dounin
# Date 1681702255 -10800
# Mon Apr 17 06:30:55 2023 +0300
# Node ID a8e22a3212da945e9060d4233905eb6de1399d34
# Parent 605cab711606724e5879e8a81d5d21797e5ddcfb
Tests: added has_feature() test for SSL libraries.
This makes it possible to further
details: https://hg.nginx.org/nginx/rev/9bcc5cc94ff4
branches:
changeset: 8126:9bcc5cc94ff4
user: Maxim Dounin
date: Thu Feb 23 18:15:53 2023 +0300
description:
Win32: removed unneeded wildcard in NGX_CC_NAME test for msvc.
Wildcards for msvc in NGX_CC_NAME tests are not needed
this is not important for the particular test (since all
known Linux versions with SO_COOKIE do have stdint.h), using the
same header in all tests and the code is good from consistency
point of view.
--
<http://www.alejandro-colomar.es/>
OpenPGP_signature
Description: OpenPGP digital sig
> # Branch quic
> > # Node ID 849f3b4043ee07a65bbfc4ad136e4246002ec00c
> > # Parent 6bb884dc72916dc675df65d02abee0c9cfabc916
> > QUIC: improved SO_COOKIE configure test.
> >
> > In nginx source code the inttypes.h include, if available, is used to define
> > standard integer types. Cha
configure test.
In nginx source code the inttypes.h include, if available, is used to define
standard integer types. Changed the SO_COOKIE configure test to follow this.
May I ask for curiosity why do you prefer for the standard
integer types?
Normally, the preferred header file is , since
details: https://hg.nginx.org/nginx/rev/ec26874c3f60
branches:
changeset: 8119:ec26874c3f60
user: Maxim Dounin
date: Mon Jan 23 05:01:01 2023 +0300
description:
Configure: removed unneeded header from UDP_SEGMENT test.
diffstat:
auto/os/linux | 1 -
1 files changed, 0 insertions
> # Branch quic
> > # Node ID 849f3b4043ee07a65bbfc4ad136e4246002ec00c
> > # Parent 6bb884dc72916dc675df65d02abee0c9cfabc916
> > QUIC: improved SO_COOKIE configure test.
> >
> > In nginx source code the inttypes.h include, if available, is used to define
> > st
01 2023 +0300
> > # Node ID ec26874c3f60b115eea5a75b383aaa482837e628
> > # Parent 07b0bee87f32be91a33210bc06973e07c4c1dac9
> > Configure: removed unneeded header from UDP_SEGMENT test.
> >
> > diff --git a/auto/os/linux b/auto/os/linux
> > --- a/auto/os/linux
> >
f65d02abee0c9cfabc916
> QUIC: improved SO_COOKIE configure test.
>
> In nginx source code the inttypes.h include, if available, is used to define
> standard integer types. Changed the SO_COOKIE configure test to follow this.
>
> diff --git a/auto/os/linux b/auto/os/linux
>
c1dac9
> Configure: removed unneeded header from UDP_SEGMENT test.
>
> diff --git a/auto/os/linux b/auto/os/linux
> --- a/auto/os/linux
> +++ b/auto/os/linux
> @@ -238,7 +238,6 @@ ngx_feature="UDP_SEGMENT"
> ngx_feature_name="NGX_HAVE_UDP_SEGMEN
# HG changeset patch
# User Maxim Dounin
# Date 1674441584 -10800
# Mon Jan 23 05:39:44 2023 +0300
# Branch quic
# Node ID 849f3b4043ee07a65bbfc4ad136e4246002ec00c
# Parent 6bb884dc72916dc675df65d02abee0c9cfabc916
QUIC: improved SO_COOKIE configure test.
In nginx source code the inttypes.h
# HG changeset patch
# User Maxim Dounin
# Date 1674439261 -10800
# Mon Jan 23 05:01:01 2023 +0300
# Node ID ec26874c3f60b115eea5a75b383aaa482837e628
# Parent 07b0bee87f32be91a33210bc06973e07c4c1dac9
Configure: removed unneeded header from UDP_SEGMENT test.
diff --git a/auto/os/linux b
8f7b80d1c1
> Win32: removed unneeded wildcard in NGX_CC_NAME test for msvc.
>
> Wildcards for msvc in NGX_CC_NAME tests are not needed since 78f8ac479735.
>
> diff -r 2af1287d2da7 -r f5d9c24fb4ac auto/cc/conf
> --- a/auto/cc/confSun Dec 18 21:29:02 2022 +0300
> +++ b/a
# HG changeset patch
# User Maxim Dounin
# Date 1671541071 -10800
# Tue Dec 20 15:57:51 2022 +0300
# Node ID f5d9c24fb4ac2a6b82b9d842b88978a329690138
# Parent 2af1287d2da744335932f6dca345618f7b80d1c1
Win32: removed unneeded wildcard in NGX_CC_NAME test for msvc.
Wildcards for msvc
Hi there,
I am happy to announce the new 0.30 release of Test::Nginx:
https://openresty.org/en/ann-test-nginx-030.html
This version has many new features and fixes several bugs since 0.29,
refer to the above link for details.
This Perl module provides a test scaffold for automated testing
Hi there,
I am happy to announce the new 0.30 release of Test::Nginx:
https://openresty.org/en/ann-test-nginx-030.html
This version has many new features and fixes several bugs since 0.29,
refer to the above link for details.
This Perl module provides a test scaffold for automated testing
Hi, Vadim
We assume that your test has been passed whether applying Maxim's
patch or not the conventional one.
(my verification may be inadequate...)
:server {
:listen 127.0.0.1:8080;
:location / {
:proxy_pass http://127.0.0.2:8080;
:proxy_cache
# HG changeset patch
# User Maxim Dounin
# Date 1650492934 -10800
# Thu Apr 21 01:15:34 2022 +0300
# Node ID 01665f0b84e6cb185ec289955b0058a22459566c
# Parent bde65a069a0d7ea1d7c456a9b9ed02daf9cb99fb
Tests: perl $r->header_in("Connection") test.
diff --git a/perl.t b/perl.t
# HG changeset patch
# User Maxim Dounin
# Date 1650492936 -10800
# Thu Apr 21 01:15:36 2022 +0300
# Node ID 97a72607140290452a991ce98f3eb1d004b6eabc
# Parent 01665f0b84e6cb185ec289955b0058a22459566c
Tests: perl $r->header_in() combining headers test.
diff --git a/perl.t b/per
# HG changeset patch
# User Vadim Fedorenko
# Date 1649976970 -10800
# Fri Apr 15 01:56:10 2022 +0300
# Node ID 3d5684530a8ef228cd7f20ff3e51f9ea5e77f2ec
# Parent 0c50a00e67334659d58d3cf7cb81fcf5872a8285
Tests: added Expires and Cache-Control headers test
diff -r 0c50a00e6733 -r
# HG changeset patch
# User Vadim Fedorenko
# Date 1649976970 -10800
# Fri Apr 15 01:56:10 2022 +0300
# Node ID 39dea3973d47e0bcd226beb3c6554dcdc0e26495
# Parent 0c50a00e67334659d58d3cf7cb81fcf5872a8285
Tests: added Expires and Cache-Control headers test
diff -r 0c50a00e6733 -r
details: https://hg.nginx.org/njs/rev/4d38ea471228
branches:
changeset: 1822:4d38ea471228
user: Dmitry Volyntsev
date: Thu Jan 27 13:01:55 2022 +
description:
Tests: refactored modules tests using test262 test suite.
diffstat:
auto/expect
if I did something wrong in my measurements, if this is a
> > known weakness of the test-suite, and in the latter case, if this is
> > something that the Nginx project is open to receiving contributions on.
>
> Probably not a weakness but unjustified expectations? :-)
>
>
Hi Hugo,
This is great to see your interest to nginx tests.
On 14.01.2022 18:45, Hugo Lefeuvre wrote:
Hello!
As part of a research project, I measured the coverage achieved by Nginx's
test-suite using gcov. Taking a look at the results, my colleagues and
myself were somewhat surprised
Hello!
As part of a research project, I measured the coverage achieved by Nginx's
test-suite using gcov. Taking a look at the results, my colleagues and
myself were somewhat surprised to realize that the coverage capped at about
70% line coverage and 81% function coverage; we expected something
Hello!
On Tue, Jan 11, 2022 at 02:05:31AM +0300, Maxim Dounin wrote:
> The test suite can be run as root, but, given that nginx switches
> to a non-privileged user by default (https://nginx.org/r/user),
> and temporary directory is only readable by the owner, running
> test s
Hello!
On Mon, Jan 10, 2022 at 01:28:52PM +, Hugo Lefeuvre wrote:
> Hi Maxim,
>
> On Sun, Jul 04, 2021 at 04:29:43AM +0300, Maxim Dounin wrote:
> > Hello!
> >
> > On Sat, Jul 03, 2021 at 09:18:53AM +0100, Hugo Lefeuvre wrote:
> >
> > > I am
Hi Maxim,
On Sun, Jul 04, 2021 at 04:29:43AM +0300, Maxim Dounin wrote:
> Hello!
>
> On Sat, Jul 03, 2021 at 09:18:53AM +0100, Hugo Lefeuvre wrote:
>
> > I am trying to run the test suite, but it seems that, no matter how I build
> > Nginx, it systematically fails.
>
details: https://hg.nginx.org/njs/rev/8843d18bee30
branches:
changeset: 1777:8843d18bee30
user: Dmitry Volyntsev
date: Wed Dec 22 16:54:27 2021 +
description:
Tests: improved test262 output when a test fails.
diffstat:
test/report | 1 +
test/setup | 3 +++
test/test262
details: https://hg.nginx.org/njs/rev/1efb00924df8
branches:
changeset: 1770:1efb00924df8
user: Dmitry Volyntsev
date: Tue Dec 21 15:49:13 2021 +
description:
Tests: moving module tests into separate test suites.
diffstat:
src/test/njs_unit_test.c | 2609
details: https://hg.nginx.org/njs/rev/ce5cd29751a4
branches:
changeset: 1769:ce5cd29751a4
user: Dmitry Volyntsev
date: Tue Dec 21 15:49:05 2021 +
description:
Tests: moving backtraces test into a separate test suite.
diffstat:
src/test/njs_unit_test.c | 115
details: https://hg.nginx.org/njs/rev/6aaf1c14c1e7
branches:
changeset: 1754:6aaf1c14c1e7
user: Dmitry Volyntsev
date: Mon Nov 29 18:14:25 2021 +
description:
Tests: making async/await test filenames shorter.
diffstat:
test/js/async_add.t.js | 15
Hi Francis,
On Mon, Nov 22, 2021 at 6:17 PM Francis Daly wrote:
>
> On Mon, Nov 22, 2021 at 03:42:39PM -0300, Fabiano Furtado Pessoa Coelho wrote:
>
> Hi there,
>
> > NGINX has a -T option, where you can "test configuration, dump it and exit".
> > I
On Mon, Nov 22, 2021 at 03:42:39PM -0300, Fabiano Furtado Pessoa Coelho wrote:
Hi there,
> NGINX has a -T option, where you can "test configuration, dump it and exit".
> Is there a way to process the "include" directive and dump the
> configuration "expande
Hi...
NGINX has a -T option, where you can "test configuration, dump it and exit".
Is there a way to process the "include" directive and dump the
configuration "expanded"?
Thanks in advance.
Fabiano Furtado
___
nginx mai
details: https://hg.nginx.org/nginx/rev/84c60a3cd12a
branches: stable-1.20
changeset: 7969:84c60a3cd12a
user: Maxim Dounin
date: Sat Oct 30 02:39:19 2021 +0300
description:
Changed ngx_chain_update_chains() to test tag first (ticket #2248).
Without this change, aio used with HTTP/2
details: https://hg.nginx.org/njs/rev/8dd6868a8748
branches:
changeset: 1733:8dd6868a8748
user: Dmitry Volyntsev
date: Mon Nov 01 15:53:30 2021 +
description:
Tests: allowing to define own test function per test suite.
diffstat:
test/webcrypto/aes.js | 8
details: https://hg.nginx.org/nginx/rev/c7a8bdf5af55
branches:
changeset: 7951:c7a8bdf5af55
user: Maxim Dounin
date: Sat Oct 30 02:39:19 2021 +0300
description:
Changed ngx_chain_update_chains() to test tag first (ticket #2248).
Without this change, aio used with HTTP/2 can result
# HG changeset patch
# User Maxim Dounin
# Date 1633526031 -10800
# Wed Oct 06 16:13:51 2021 +0300
# Node ID ac42b4b31026ec24345331e9bd5c38ac4b6e7502
# Parent bfad703459b4e2416548ac66f548e96c2197d9cc
Changed ngx_chain_update_chains() to test tag first (ticket #2248).
Without this change
Thanks! It worked :)
On Tue, Sep 21, 2021 at 7:55 AM Sergey Kandaurov wrote:
>
>
> > On 21 Sep 2021, at 17:46, Greeshma A
> wrote:
> >
> > Thanks for pointing to the variable I can use.
> >
> > What variable would capture the ip address and port number together?
> > As far as I see, it's
> On 21 Sep 2021, at 17:46, Greeshma A wrote:
>
> Thanks for pointing to the variable I can use.
>
> What variable would capture the ip address and port number together?
> As far as I see, it's either the ip address or port?
> How can I combine them in the map definition?
> Can I put a colon
:$proxy_protocol_port $proxy_state{
}
On Tue, Sep 21, 2021, 2:43 AM Sergey Kandaurov wrote:
>
> > On 21 Sep 2021, at 07:56, Greeshma A
> wrote:
> >
> > I am trying to test the following config :
> > For proxy_protocol I have made changes in the nginx source co
> On 21 Sep 2021, at 07:56, Greeshma A wrote:
>
> I am trying to test the following config :
> For proxy_protocol I have made changes in the nginx source code to support
> variable input parameter as well.
> Im writing unit tests for this. However, Im not sure how to
I am trying to test the following config :
For proxy_protocol I have made changes in the nginx source code to support
variable input parameter as well.
Im writing unit tests for this. However, Im not sure how to configure the
map directive. The variable $ssl_preread_server_nameis wrong. I need
Hello!
On Sat, Jul 03, 2021 at 09:18:53AM +0100, Hugo Lefeuvre wrote:
> I am trying to run the test suite, but it seems that, no matter how I build
> Nginx, it systematically fails.
>
> It seems that, most (all?) of the time, tests fail because Nginx returns
> 403 e
Hi,
I am trying to run the test suite, but it seems that, no matter how I build
Nginx, it systematically fails.
It seems that, most (all?) of the time, tests fail because Nginx returns
403 error codes, e.g.:
./ssi_waited.t . 1/3
# Failed test 'waited non-active
details: https://hg.nginx.org/nginx/rev/e2e9e0fae747
branches:
changeset: 7818:e2e9e0fae747
user: Maxim Dounin
date: Mon Apr 05 20:14:16 2021 +0300
description:
Configure: fixed --test-build-epoll on FreeBSD 13.
In FreeBSD 13, eventfd(2) was added, and this breaks build
with --test
sers.
>>>
>>>
>>> Try cleaning browser cache.
>>>
>>> Also check if there are lines with the word ‘quic’ in the debug log when
>>> you open the page.
>>>
>>> Thanks. Regards
>>>
>>>
>>> On Tue, Feb 2, 2021 a
ginx.org <https://quic.nginx.org/> website detects HTTP/3
>> (QUIC) support in the browsers.
>
> Try cleaning browser cache.
>
> Also check if there are lines with the word ‘quic’ in the debug log when you
> open the page.
>
>> Thanks. Regards
>>
>
..
>> The https://quic.nginx.org website detects HTTP/3 (QUIC) support in the
>> browsers.
>>
>>
>> Try cleaning browser cache.
>>
>> Also check if there are lines with the word ‘quic’ in the debug log when
>> you open the page.
>>
>> Thanks
Hi Andrey,
>>
>> On 2 Feb 2021, at 17:30, Andrey Khramov wrote:
>>
>> Hello, there
>>
>> I tried to test the HTTP/3 (QUIC) with nginx-quic in several days.
>> But I couldn't test HTTP/3 (QUIC).
>>
>> I built the quic branch of nginx-quic repo ac
gt;
> On Tue, Feb 2, 2021 at 2:47 PM Roman Arutyunyan <mailto:a...@nginx.com>> wrote:
> Hi Andrey,
>
>> On 2 Feb 2021, at 17:30, Andrey Khramov > <mailto:and...@apporto.com>> wrote:
>>
>> Hello, there
>>
>> I tried to test the HTTP/3 (QUIC) w
Roman Arutyunyan wrote:
> Hi Andrey,
>
> On 2 Feb 2021, at 17:30, Andrey Khramov wrote:
>
> Hello, there
>
> I tried to test the HTTP/3 (QUIC) with nginx-quic in several days.
> But I couldn't test HTTP/3 (QUIC).
>
> I built the quic branch of nginx-quic repo acco
Hi Andrey,
> On 2 Feb 2021, at 17:30, Andrey Khramov wrote:
>
> Hello, there
>
> I tried to test the HTTP/3 (QUIC) with nginx-quic in several days.
> But I couldn't test HTTP/3 (QUIC).
>
> I built the quic branch of nginx-quic repo according to README of that repo.
>
Hello, there
I tried to test the HTTP/3 (QUIC) with nginx-quic in several days.
But I couldn't test HTTP/3 (QUIC).
I built the quic branch of nginx-quic repo according to README of that repo.
The configuration options follows as below:
$ ./auto/configure --prefix=/etc/nginx
Hi there,
I am happy to announce the new 0.29 release of Test::Nginx:
https://openresty.org/en/ann-test-nginx-029.html
This version fixes the Test2::Util module dependency problem
introduced in the previous 0.28 release.
This Perl module provides a test scaffold for automated testing in
Nginx
details: https://hg.nginx.org/nginx/rev/f1e6f65ddfeb
branches:
changeset: 7727:f1e6f65ddfeb
user: Ruslan Ermilov
date: Tue Oct 13 07:44:09 2020 +0300
description:
Cpp test: added stream.
diffstat:
src/misc/ngx_cpp_test_module.cpp | 2 ++
1 files changed, 2 insertions(+), 0
details: https://hg.nginx.org/njs/rev/00fcf5b00ce3
branches:
changeset: 1526:00fcf5b00ce3
user: Dmitry Volyntsev
date: Mon Sep 21 17:15:10 2020 +
description:
Fixed unit test on big-endian platforms.
diffstat:
src/test/njs_unit_test.c | 43
y case I have a two internal DNS zones, .develop and .test.
>
> On global http section I added my resolver:
>
> ...
>
> http {
> resolver 192.168.140.249 valid=300s;
> resolver_timeout 1s;
>
> ...
>
> And I use proxy_pass directive with DNS name l
Hi everyone!
Unfortunately, I can't find information about how Nginx tests
configuration files.
In my case I have a two internal DNS zones, .develop and .test.
On global http section I added my resolver:
...
http {
resolver 192.168.140.249 valid=300s;
resolver_timeout 1s
details: https://hg.nginx.org/njs/rev/f4fe4b4b9730
branches:
changeset: 1517:f4fe4b4b9730
user: Dmitry Volyntsev
date: Thu Sep 03 13:30:17 2020 +
description:
Fixed TextDecoder() test on big-endian platforms.
diffstat:
src/test/njs_unit_test.c | 4 ++--
1 files changed, 2
Hi there,
I am happy to announce the new 0.28 release of Test::Nginx:
https://openresty.org/en/ann-test-nginx-028.html
This version fixes the Test2::Util module dependency problem
introduced in the previous 0.27 release.
This Perl module provides a test scaffold for automated testing in
Nginx
details: https://hg.nginx.org/njs/rev/fcb5e172abaf
branches:
changeset: 1466:fcb5e172abaf
user: Dmitry Volyntsev
date: Tue Jul 14 13:16:06 2020 +
description:
Fixed unit test on big-endian platforms.
This closes #326 issue on Github.
diffstat:
auto/endianness | 36
Hi there,
I am happy to announce the new 0.27 release of Test::Nginx:
https://openresty.org/en/ann-test-nginx-027.html
This Perl module provides a test scaffold for automated testing in
Nginx C module or OpenResty-based Lua library development and
regression testing.
This class inherits from
details: https://hg.nginx.org/njs/rev/29ff89055e29
branches:
changeset: 1452:29ff89055e29
user: Dmitry Volyntsev
date: Mon Jul 06 18:37:13 2020 +
description:
Added TypeScript test.
diffstat:
auto/make | 3 ++
test/ts/test.ts | 66
4978
> Allow some syslog message to arrive in either order
>
> This test flakes occasionally with good,work arriving as work,good.
A slightly different version committed, thanks.
https://hg.nginx.org/nginx-tests/rev/9e142c0e34b2
--
Sergey Kandaurov
__
Appreciate your confidence on Nignx!!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,288558,288564#msg-288564
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Yup thanks I mailed them today.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,288558,288563#msg-288563
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
and I rolled up to a Bugatti dealer and asked for a test drive
the dealer would laugh at me. People buy super cars sight unseen because they
know they are super cars. In the same way, if you need a reverse proxy Then
nginx is what you need. It’s that simple. I don’t work for nginx, I’m
> I am assessing the capabilities and doing a POC on Nignx integration as
> reverse proxy. Are there any pre-configured image with all the protocols and
> the necessary clients to test and demo the capabilities of Nignx or Nignx
> plus? Doing a self-assessment with all the necessary
Hi Team,
I am assessing the capabilities and doing a POC on Nignx integration as
reverse proxy. Are there any pre-configured image with all the protocols and
the necessary clients to test and demo the capabilities of Nignx or Nignx
plus? Doing a self-assessment with all the necessary setup on my
# HG changeset patch
# User Dionna Glaze
# Date 1593542175 25200
# Tue Jun 30 11:36:15 2020 -0700
# Node ID a2a00a127689c64d21842d2aba7f1dc53e06b095
# Parent f55d25e08b3edaab6f3a30a000ac486334994978
Allow some syslog message to arrive in either order
This test flakes occasionally
details: https://hg.nginx.org/njs/rev/02634f76f6d0
branches:
changeset: 1434:02634f76f6d0
user: Dmitry Volyntsev
date: Wed Jun 17 14:38:23 2020 +
description:
Improved unit test.
1) Accepting multiple options.
2) Added filter option, to run only selected suites.
For example
and create a test suite for any needs in every
particular case.
Please let me know if you have any questions.
--
Sergey
On Thu, Jun 04, 2020 at 05:53:50PM +, Yigal Edery wrote:
> Hi
>
> I hope this is the right forum to ask.
>
> I need to set up NGINX and run a ful
as expected?
>
> -Original Message-
> From: Maxim Konovalov
> Sent: Wednesday, June 10, 2020 15:18
> To: nginx-devel@nginx.org
> Cc: Yigal Edery
> Subject: Re: nginx test plan with max coverage?
>
> Hi Yigal,
>
> We use nginx-tests for that. The suite provides &q
test plan with max coverage?
Hi Yigal,
We use nginx-tests for that. The suite provides "good enough" coverage already
which is also monitored by the development team.
Maxim
On 10.06.2020 15:11, Yigal Edery wrote:
> Anyone?
>
>
>
> *From:* Yigal Edery
> *Sent:*
gt; *To:* nginx-devel@nginx.org
> *Subject:* nginx test plan with max coverage?
>
>
>
> Hi
>
>
>
> I hope this is the right forum to ask.
>
>
>
> I need to set up NGINX and run a full test coverage on it.
>
>
>
> Other than the
Anyone?
From: Yigal Edery
Sent: Thursday, June 4, 2020 20:54
To: nginx-devel@nginx.org
Subject: nginx test plan with max coverage?
Hi
I hope this is the right forum to ask.
I need to set up NGINX and run a full test coverage on it.
Other than the nginx-tests, is there some formal test plan
Hi
I hope this is the right forum to ask.
I need to set up NGINX and run a full test coverage on it.
Other than the nginx-tests, is there some formal test plan for nginx that you
use, to exercises an nginx server before declaring a release? I am thinking
some long duration tests with maximum
1 - 100 of 260 matches
Mail list logo
