Add Local Regression Tests topic

[PeterTurcan]

fix #218

Most of the introductory stuff for Regression was already included in the Introduction to testing, and Test Matrix sections. Added a single page on local regression tests.

[cppalliance-bot]

An automated preview of the documentation is available at https://221.site-docs.prtest2.cppalliance.org/contributor-guide/index.html

[joaquintides]

There're some problems with this part:

• The link is an abolute one (http://www.boost.org/development/tests/master/developer/summary.html) and points to a page in the old website that will be unavailable after migration.
• Additionally, the linked page is just one of the four pages collectively comprising the dashboard:
  • Develop branch: Summary, Unresolved Issues
  • Master branch: Summary, Unresolved Issues

So, we need to replace this single link with four links as described above, probably using a layout similar to this:

(The "Developers" header may be changed to something more pertinent such as "Results"). Now, the location of these four links in the new backend are:

• https://regression.boost.io/develop/developer/summary.html
• https://regression.boost.io/develop/developer/issues.html
• https://regression.boost.io/master/developer/summary.html
• https://regression.boost.io/master/developer/issues.html

These, again, are absolute links, and boost.io is not the final domain. We can include them in a couple of ways:

1. As

• https://regression.boost.org/develop/developer/summary.html
• https://regression.boost.org/develop/developer/issues.html
• https://regression.boost.org/master/developer/summary.html
• https://regression.boost.org/master/developer/issues.html
  This will work once we migrate to boost.org, but will 404 in the meantime.

2. Via relative URLs redirected to the proper regression.*/xx absolute URLs

@kennethreitz, @sdarwin which option do you think is best? Or maybe there's a better solution I haven't thought of.

Thank you,

[PeterTurcan]

Probably the right approach here is to use the four links that work for now, merge the PR, then file a reasonably high priority issue to change to the four new links when the migration is done and tested? By doing this the information gets out there and there is no pressure to rush the migration if or when issues arise? - Peter T

…

On Sat, Apr 27, 2024 at 2:38 AM joaquintides ***@***.***> wrote: There're some problems with this part: imagen.png (view on web) <https://github.com/boostorg/website-v2-docs/assets/3283164/1029162a-ed18-440f-930d-d2e5ae68cac8> - The link is an abolute one ( http://www.boost.org/development/tests/master/developer/summary.html) and points to a page in the old website that will be unavailable after migration. - Additionally, the linked page is just one of the four pages collectively comprising the dashboard: - Develop branch: Summary <https://www.boost.org/development/tests/develop/developer/summary.html>, Unresolved Issues <https://www.boost.org/development/tests/develop/developer/issues.html> - Master branch: Summary <https://www.boost.org/development/tests/master/developer/summary.html>, Unresolved Issues <https://www.boost.org/development/tests/master/developer/issues.html> So, we need to replace this single link with four links as described above, probably using a layout similar to this: imagen.png (view on web) <https://github.com/boostorg/website-v2-docs/assets/3283164/ed6419e1-5881-4748-9cb0-5abb5e39aa77> (The "Developers" header may be changed to something more pertinent such as "Results"). Now, the location of these four links in the new backend are: - https://regression.boost.io/develop/developer/summary.html - https://regression.boost.io/develop/developer/issues.html - https://regression.boost.io/master/developer/summary.html - https://regression.boost.io/master/developer/issues.html These, again, are absolute links, and boost.io is not the final domain. We can include them in a couple of ways: 1. As - https://regression.boost.org/develop/developer/summary.html - https://regression.boost.org/develop/developer/issues.html - https://regression.boost.org/master/developer/summary.html - https://regression.boost.org/master/developer/issues.html This will work once we migrate to boost.io, but will 404 in the meantime. 2. Via relative URLs redirected to the proper regression.*/xx absolute URLs @kennethreitz <https://github.com/kennethreitz>, @sdarwin <https://github.com/sdarwin> which option do you think is best? Or maybe there's a better solution I haven't thought of. Thank you, — Reply to this email directly, view it on GitHub <#221 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEIBS2JVIXS3TWW6WRCCLJLY7NWZVAVCNFSM6AAAAABGXQNRNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGQZTENJZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[joaquintides]

Hi Peter, yes, let's do as you propose. Other solutions are probably too complicated for what's esentially a one-time event (the migration).

[PeterTurcan]

@joaquintides OK - done!

[cppalliance-bot]

An automated preview of the documentation is available at https://221.site-docs.prtest2.cppalliance.org/contributor-guide/index.html

[joaquintides]

Merged, thank you!