test1903: actually verify the cookies after the test

The test otherwise could do just about anything (except leak memory in
debug mode) and its bad behaviour wouldn't be detected. Now, check the
resulting cookie file to ensure the cookies are still there.

Closes #12041

diff --git a/tests/data/test1903 b/tests/data/test1903
index 24ad174663755398f0fffc2900c690c1a8bd9fab..6c879de961f0783292faca11af01508c4177f7e8 100644 (file)
--- a/tests/data/test1903
+++ b/tests/data/test1903
@@ -33,7 +33,7 @@ CURLOPT_COOKIEFILE then reset then set again
 lib%TESTNUMBER
 </tool>
 <command>
-http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER %LOGDIR/cookies%TESTNUMBER
+http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER %LOGDIR/cookies%TESTNUMBER %LOGDIR/cookiesout%TESTNUMBER
 </command>
 <features>
 cookies
@@ -50,5 +50,13 @@ cookies
 
 # Verify data after the test has been "shot"
 <verify>
+<file name="%LOGDIR/cookiesout%TESTNUMBER" mode="text">
+# Netscape HTTP Cookie File
+# https://curl.se/docs/http-cookies.html
+# This file was generated by libcurl! Edit at your own risk.
+
+%HOSTIP        FALSE   /we/want/       FALSE   0       foobar  name
+%HOSTIP        FALSE   /we/want/       FALSE   0       secondcookie    present
+</file>
 </verify>
 </testcase>

diff --git a/tests/libtest/lib1903.c b/tests/libtest/lib1903.c
index a8a767e5c0b0777b282b32ecae73a56bafa19519..3c4ae3073451d4b2ec5b1aa8f19ed87b0022f235 100644 (file)
--- a/tests/libtest/lib1903.c
+++ b/tests/libtest/lib1903.c
@@ -46,6 +46,7 @@ int test(char *URL)
 
   easy_setopt(ch, CURLOPT_URL, URL);
   easy_setopt(ch, CURLOPT_COOKIEFILE, libtest_arg2);
+  easy_setopt(ch, CURLOPT_COOKIEJAR, libtest_arg3);
   res = curl_easy_perform(ch);
 
 test_cleanup: