Automate certain QA tests

[sdarwin]

After deploying to stage or production, run a script that verifies a predetermined set of URLs. These could be /news/ , /releases/ , /libraries/ , a few specific docs pages such as https://www.boost.org/doc/libs/1_89_0/doc/html/boost_asio/examples.html , randomly selected.
https://www.boost.org/doc/libs/1_89_0/libs/json/doc/html would test "missing final slash".
Test in a normal way, and also bypassing the CDN.
34.120.246.69 stage IP address
35.190.118.110 production IP address
Use a series of separate curl or wget commands in the script. Verify the result code is expected (200) and the "content" contains a certain word.
If this script were available, then perhaps once a week, right before deploying to production, check that stage is generally fine, and after a deployment, that production is. Just with one command each time.
An idea for @karimarie67

[karimarie67]

Hi @sdarwin - first pass at this is attached. I welcome any and all feedback!

boost-verify.sh

[sdarwin]

That is surprisingly good (on first pass).
AI is developing very quickly. Did you just pass the issue description to openai or something?

[sdarwin]

You should test it, be sure it works, and understand what it's doing. Then open a PR.

[karimarie67]

I did test it! All the possible versions and it was trial and error at first 😄 I worked with AI on it, Claude to be exact. I like to get a shell going then add to it, learning as I go along since I am not a developer.

I will go through some more tests and also add/remove/change URLs and make sure I completely understand. Thank you!

[karimarie67]

I shared the wrong file. This is the most current.

boost-verify.sh

[sdarwin]

The way to review the script is as a pull request, instead of an attachment in an issue. It's looking pretty good now.
If you are uncertain about the content of a pull request, mark a PR as a "draft". And also in the title it could say "Draft - ".

Note, new issue (1950), unusual characters  are appearing again. In boost-verify.sh add one test, that's checking that beast file for the presence of  and failing. (Or when needed, slightly adjust the test in terms of filename and contents, to check for these weird letters.)