Creating a 'test site' containing corner/tricky cases encountered over time

[IanCheah]

Please confirm that you have searched existing issues in the repo

Yes, I have searched the existing issues

Any related issues?

No response

What is the area that this feature belongs to?

Testing

Is your feature request related to a problem? Please describe.

This is a follow up from the comment by @damithc under PR #2678.

It can be quite troublesome to look through the whole CS2103/T website to check for any differences between the new and current version, whenever a change is being made.

Some of these tricky cases includes
#2670
#2667

Describe the solution you'd like

It would be good to have a 'test site' that contains all the corner cases we have envountered over time, to use it to easily smoke-test a new version.

Describe alternatives you've considered

No response

Additional context

No response

[arshinsikka]

Test site added for tricky/corner cases — PR #2741

Hi! I've submitted PR #2741 as part of Milestone 3B, which addresses this issue.

• It introduces a dedicated test site at core/test/unit/tricky-site/ containing tricky/corner cases we've encountered (e.g., tables, diagrams, shorthand syntax).
• This will help catch regressions earlier and make smoke testing more efficient when changes are made.

Feel free to share if you'd like any additional cases included @IanCheah !

---