From f9ace3996e4904206a14acaf82ad3746dd95b3ef Mon Sep 17 00:00:00 2001
From: Joe Goggins <joe@particle.io>
Date: Fri, 24 Jun 2022 17:47:07 -0500
Subject: [PATCH] Update docs to reflect not needing to set env vars

---
 README.md           | 2 --
 e2e-tests/README.md | 4 +++-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 5b40d49..4dad761 100644
--- a/README.md
+++ b/README.md
@@ -34,8 +34,6 @@ All essential commands are available at the root via `npm run <script name>` - e
 <summary><b>How to run your tests</b></summary>
 <p>
 
-The `Agent` integration tests ([source](./test/Agent.integration.js)) depend on a real HTTP api backend and a valid Particle access token. Be sure to set relevant environment variables to avoid test failures. You can prefix commands test commands like this `PARTICLE_API_BASE_URL=<url> PARTICLE_API_TOKEN=<token> npm test`
-
 `npm test` runs the tests.
 
 `npm run coverage` shows code coverage 
diff --git a/e2e-tests/README.md b/e2e-tests/README.md
index 1b6ea9c..8cb545d 100644
--- a/e2e-tests/README.md
+++ b/e2e-tests/README.md
@@ -5,4 +5,6 @@ They can be used to do deep validations on the behavior of the library against t
 Follow the directions at in each script for how to use them.
 
 Also, you'll need set valid values for env vars like PARTICLE_API_BASE_URL
-and PARTICLE_API_TOKEN
\ No newline at end of file
+and PARTICLE_API_TOKEN.
+
+Note also that these e2e-tests are not actively maintained.
\ No newline at end of file