-
Updated
Jun 5, 2022 - CSS
lightweight
Here are 2,140 public repositories matching this topic...
Tests
-
Updated
Jun 7, 2022 - JavaScript
-
Updated
Jun 21, 2022 - SCSS
-
Updated
Jul 5, 2022 - TypeScript
-
Updated
Jul 8, 2022 - Go
-
Updated
Jun 25, 2022 - JavaScript
-
Updated
Dec 17, 2019
-
Updated
Jun 11, 2022 - JavaScript
-
Updated
Jul 5, 2022 - C
-
Updated
Jul 8, 2022 - Java
-
Updated
Jul 7, 2022 - Shell
-
Updated
May 21, 2022 - C
-
Updated
Dec 7, 2021 - Swift
-
Updated
Oct 7, 2021 - HTML
-
Updated
Jun 11, 2022 - TypeScript
-
Updated
Apr 11, 2022 - JavaScript
-
Updated
Dec 21, 2020 - JavaScript
-
Updated
Jun 27, 2022 - C
-
Updated
Jun 29, 2022 - JavaScript
It might be useful to detect a redirect loop, not just guess based on the number of tries, but actually check the URL, to allow to fail early and a larger default number.
-
Updated
Nov 18, 2021 - JavaScript
-
Updated
Jul 7, 2022 - Shell
-
Updated
Jul 6, 2022 - Python
-
Updated
Mar 10, 2022 - Kotlin
-
Updated
Oct 28, 2021 - C++
-
Updated
Jul 5, 2021 - Go
-
Updated
Jun 22, 2022 - TypeScript
-
Updated
Jul 19, 2020 - JavaScript
Improve this page
Add a description, image, and links to the lightweight topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the lightweight topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.
now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.
a lot of code can already be regression-tested by simply running all the demos and val