From be2f4b18e0c8fe54aff960b18d12190e05122213 Mon Sep 17 00:00:00 2001
From: George Xu <33054982+georgexu99@users.noreply.github.com>
Date: Wed, 16 Nov 2022 16:04:12 -0800
Subject: [PATCH] docs: remove mentions of lerna run test in contributing.md
 (#3081)

---
 CONTRIBUTING.md | 13 +++----------
 1 file changed, 3 insertions(+), 10 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a374a846bc..620f2bf2d5 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -71,17 +71,10 @@ Please ensure that all changes are committed using [semantic commit messages](ht
 ### Running the Tests
 
 The Electron Forge repository has a lot of tests, some of which take a decent
-amount of time to run when uncached. The repository will automatically cache test results for future runs.
-Adding `skip-nx-cache` will skip the cache.
+amount of time to run.
 
 ```bash
-lerna run test
-```
-
-Tests can also run within a specific scope.
-
-```bash
-lerna run test --scope @electron-forge/core
+yarn test
 ```
 
 ## Filing Pull Requests
@@ -107,7 +100,7 @@ Here are some things to keep in mind as you file pull requests to fix bugs, add
 
 ### Release process
 
-- Make sure the tests pass with `lerna run test`
+- Make sure the tests pass with `yarn test`
 - Run `git clean -fdx` - this will ensure unneeded build files (and potentially sensitive files) are not included in the npm package.
 - Ensure that you are logged into npm via command line (`npm login`)
 - `lerna publish --force-publish`