Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support running API tests with certain server configuration #1009

Open
11 tasks
acelaya opened this issue Feb 8, 2021 · 1 comment
Open
11 tasks

Support running API tests with certain server configuration #1009

acelaya opened this issue Feb 8, 2021 · 1 comment

Comments

@acelaya
Copy link
Member

acelaya commented Feb 8, 2021

API tests depend on the global app config to pass, which means it's also not possible to test different config combinations.

Add this, so that a test can load some new config, restart the server, and run the tests against that config.

Scenarios to test:

  • Error returned by /mercure-info endpoint when mercure is not configured
  • "Not found" redirects, both global and domain-specific
  • Redis integration (single instance, cluster and sentinels)
  • Short URL deletion when visits threshold is reached
  • Support for multi-segment slugs
  • Support for trailing slashes in short URLs
  • Short URLs with and without trailing slash, combined with multi-segment slugs
  • Multiple status codes for short URLs
  • strict and loose mode
  • QR codes for enabled and disabled short URLs
  • ...
@acelaya acelaya added this to the 2.8.0 milestone Mar 10, 2021
@acelaya acelaya removed this from the 2.8.0 milestone Jul 13, 2021
@acelaya acelaya added this to the 2.9.0 milestone Aug 4, 2021
@acelaya acelaya removed this from the 2.9.0 milestone Aug 13, 2021
@acelaya acelaya added this to the 3.1.0 milestone Jan 18, 2022
@acelaya acelaya changed the title Add support to run API tests with certain server configuration Support running API tests with certain server configuration Mar 18, 2022
@acelaya acelaya modified the milestones: 3.1.0, 3.2.0 Apr 23, 2022
@acelaya acelaya added this to Shlink Aug 1, 2022
@acelaya acelaya moved this to Todo in Shlink Aug 1, 2022
@acelaya acelaya modified the milestones: 3.2.0, 3.3.0 Aug 4, 2022
@acelaya acelaya removed this from Shlink Aug 4, 2022
@acelaya acelaya added this to Shlink Aug 8, 2022
@acelaya acelaya moved this to Todo 🗒️ in Shlink Aug 8, 2022
@acelaya acelaya moved this from Todo 🗒️ to In Progress 📝 in Shlink Aug 9, 2022
@acelaya acelaya moved this from In Progress 📝 to Todo 🗒️ in Shlink Aug 9, 2022
@acelaya acelaya modified the milestones: 3.3.0, 3.4.0 Sep 17, 2022
@acelaya acelaya removed this from Shlink Sep 17, 2022
@acelaya acelaya added this to Shlink Sep 25, 2022
@acelaya acelaya moved this to Todo 🗒️ in Shlink Sep 25, 2022
@acelaya acelaya removed the status in Shlink Sep 25, 2022
@acelaya acelaya moved this to Todo 🗒️ in Shlink Dec 3, 2022
@acelaya acelaya removed this from the 3.4.0 milestone Dec 12, 2022
@acelaya acelaya removed the status in Shlink Dec 12, 2022
@acelaya acelaya moved this to Todo 🗒️ in Shlink Jan 2, 2023
@acelaya acelaya added this to the 3.6.0 milestone Apr 16, 2023
@acelaya acelaya removed this from the 3.6.0 milestone May 21, 2023
@acelaya acelaya added this to the 3.7.0 milestone May 21, 2023
@acelaya acelaya removed this from Shlink May 21, 2023
@acelaya
Copy link
Member Author

acelaya commented May 21, 2023

Depends on #1786

@acelaya acelaya moved this to Todo in Shlink Jul 31, 2023
@acelaya acelaya modified the milestones: 3.7.0, 4.0.0 Nov 4, 2023
@acelaya acelaya removed the status in Shlink Nov 4, 2023
@acelaya acelaya moved this to Todo in Shlink Feb 1, 2024
@acelaya acelaya moved this from Todo to In Progress in Shlink Feb 22, 2024
@acelaya acelaya moved this from In Progress to Todo in Shlink Feb 24, 2024
@acelaya acelaya removed the status in Shlink Mar 3, 2024
@acelaya acelaya removed this from the 4.0.0 milestone Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant