11:32 a.m.
I'm pleased to announce first version of the Web Test Fixture is up and running.
It's a web server (nginx) running inside Docker that can simulate a specific HTTP
response code as well simple cron-like availability.
Please let me know whether this is useful for Hawkular URL monitoring and what you want to
see next. For example, a. simulate slow response time, b. cycle between http status codes,
etc.
Viet Nguyen
-----
Example usage:
[1] Launch a web fixture
docker run -d -p 8999:8080 hawkularqe/web-fixture
# get custom http code (replace 503 with any valid status code)
curl -I http://localhost:8999/http?return=503
--> HTTP/1.1 503 Service Temporarily Unavailable
[2] Launch a mostly-available fixture - server goes offline for 10 seconds every minute
docker run -p 8999:8080 -e "DURATION=50s" -e "CRON_EXP=* * * * *"
hawkularqe/web-fixture
[1] and [2] in the example above are also running on public OS1:
1. http://209.132.179.82:50001
2. http://209.132.179.82:50002
Github:
https://github.com/Hawkular-QE/web-fixture
1:47 p.m.
This looks interesting. Just out of curiosity, did you consider using Gatling (or anything
similar)? I have not worked with Gatling, but it sounds like there is some similarity.
On May 27, 2015, at 12:32 PM, Viet Nguyen <vnguyen(a)redhat.com>
wrote:
I'm pleased to announce first version of the Web Test Fixture is up and running.
It's a web server (nginx) running inside Docker that can simulate a specific HTTP
response code as well simple cron-like availability.
Please let me know whether this is useful for Hawkular URL monitoring and what you want
to see next. For example, a. simulate slow response time, b. cycle between http status
codes, etc.
Viet Nguyen
-----
Example usage:
[1] Launch a web fixture
docker run -d -p 8999:8080 hawkularqe/web-fixture
# get custom http code (replace 503 with any valid status code)
curl -I http://localhost:8999/http?return=503
--> HTTP/1.1 503 Service Temporarily Unavailable
[2] Launch a mostly-available fixture - server goes offline for 10 seconds every minute
docker run -p 8999:8080 -e "DURATION=50s" -e "CRON_EXP=* * * * *"
hawkularqe/web-fixture
[1] and [2] in the example above are also running on public OS1:
1. http://209.132.179.82:50001
2. http://209.132.179.82:50002
Github:
https://github.com/Hawkular-QE/web-fixture
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:14 p.m.
There must be a confusion. Viet's work is something Mike T had suggested
in the past, to help with functional testing of availability and
response time checks in the pinger. It's not related to load testing.
Le 27/05/2015 20:47, John Sanda a écrit :
This looks interesting. Just out of curiosity, did you consider using
Gatling (or anything similar)? I have not worked with Gatling, but it sounds like there is
some similarity.
> On May 27, 2015, at 12:32 PM, Viet Nguyen <vnguyen(a)redhat.com> wrote:
>
> I'm pleased to announce first version of the Web Test Fixture is up and running.
It's a web server (nginx) running inside Docker that can simulate a specific HTTP
response code as well simple cron-like availability.
>
> Please let me know whether this is useful for Hawkular URL monitoring and what you
want to see next. For example, a. simulate slow response time, b. cycle between http
status codes, etc.
>
> Viet Nguyen
>
> -----
>
> Example usage:
>
> [1] Launch a web fixture
> docker run -d -p 8999:8080 hawkularqe/web-fixture
>
> # get custom http code (replace 503 with any valid status code)
> curl -I http://localhost:8999/http?return=503
> --> HTTP/1.1 503 Service Temporarily Unavailable
>
> [2] Launch a mostly-available fixture - server goes offline for 10 seconds every
minute
> docker run -p 8999:8080 -e "DURATION=50s" -e "CRON_EXP=* * * * *"
hawkularqe/web-fixture
>
>
> [1] and [2] in the example above are also running on public OS1:
> 1. http://209.132.179.82:50001
> 2. http://209.132.179.82:50002
>
>
> Github:
> https://github.com/Hawkular-QE/web-fixture
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3484
days inactive
3484
days old
2 comments
3 participants
participants (3)
-
John Sanda -
Thomas Segismont -
Viet Nguyen