La liste de diffusion est fermée depuis juillet 2022, mais sert toujours d'archive d'informations sur QF-Test.
Cependant, si vous souhaitez rester informé des nouveautés concernant QF-Test, vous pouvez simplement vous
abonner à la newsletter
our obtenir des informations à jour sur chaque version - y compris les versions mineures - vous pouvez
nous pouvez vous abonner au flux RSS ou nous suivre sur les médias sociaux.
Alternativement, QF-Test fournit également des informations sur la version elle-même.
Une autre source d'information est notre blog, qui contient des articles actuels sur des thèmes généraux, sur l'entreprise QFS et aussi divers "how-tos", veuillez vous
ABonner au Blog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] Server HTTP request with an expected 404 response
Hello Chris, a request returning a 404 is throwing and error by now. What you could do is simply wrap your Server HTTP-Request in a "sequence" and set the "maximum error level" to "no error". We will also discuss this internal if we need to tweak this node a bit to allow checking for negative cases a bit more straight forward. Best regards, Thomas -------- Original Message -------- From: Chris Stanbridge Sent: Wednesday, May 25, 2016 2:22:29 AM CEST To: qftest-list@?.de Subject: [QF-Test] Server HTTP request with an expected 404 response Hi, I'm using the server HTTP request node to test a rest api, but I want to periodically check that my server is (correctly) responding with a 404 response when I send invalid content. It seems a 404 is detected by QF-Test and an error is automatically raised in the run log. I want to suppress this error as I expect this result, but I can't see a way to do it for this node type. Thanks in advance, Chris The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files. _______________________________________________ qftest-list mailing list qftest-list@?.de https://www.qfs.de/mailman/listinfo/qftest-list -- _______________________________________________________________ Get the most out of QF-Test - Support directly from the authors * Training & consulting: www.qfs.de/en/qftest/training.html * Phone & email support: www.qfs.de/en/qftest/support.html _______________________________________________________________ Thomas Max Development & Support E: support@?.de T: +49 8171 38648-20 F: +49 8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer HRB München 140833
|
1. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.