From 373ea0d060960500f7ef8b43b22549fbb3d820e7 Mon Sep 17 00:00:00 2001
From: Evan Hahn <69474926+EvanHahn-Signal@users.noreply.github.com>
Date: Fri, 14 Aug 2020 17:16:30 -0500
Subject: [PATCH] Fix instructions for running libtextsecure tests

---
 CONTRIBUTING.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 22f25163335f..bf8defedf32b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -176,10 +176,10 @@ Please write tests! Our testing framework is
 The easiest way to run all tests at once is `yarn test`.
 
 You can browse tests from the command line with `grunt unit-tests` or in an
-interactive session with `NODE_ENV=test yarn run start`. The `libtextsecure` tests are run
-similarly: `grunt lib-unit-tests` and `NODE_ENV=test-lib yarn run start`. You can tweak
-the appropriate `test.html` for both of these runs to get code coverage numbers via
-`blanket.js` (it's shown at the bottom of the web page when the run is complete).
+interactive session with `NODE_ENV=test yarn run start`.
+
+If you want to run the `libtextsecure` tests, you can run `yarn run test-electron`,
+which also runs the unit tests.
 
 To run Node.js tests, you can run `yarn test-server` from the command line. You can get
 code coverage numbers for this kind of run via `yarn test-server-coverage`, then display