addressing dropped sites with 0 birds

[see24]

Trying to address #46

[see24]

I also made some changes to the way the tests are structured. First of all I changed to a smaller ARU report to make the download faster. After downloading had been tested I changed the tests to use a global object for the downloaded report rather than redownloading inside each test_that. Downloading takes about 7s for me which quickly adds up so although it breaks the guideline of having each test_that be independent I think it is worth it because you will be more willing to re-run the tests more often.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Username Password	298e5c0	tests/testthat/test-first.R	View secret
-		Username Password	4cb7543	tests/testthat/test-first.R	View secret
-		Username Password	e101130	tests/testthat/test-first.R	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>