remove js testing references

docs/build/differences-vs-evm/index.md

@@ -171,4 +171,3 @@ If you’re already familiar with blockchain development, here's a comparison be
 - [Testing Smart Contracts](https://ethereum.org/en/developers/docs/smart-contracts/testing/)
   - [Cadence testing framework](https://cadence-lang.org/docs/testing-framework) enables native tests in Cadence.
   - [overflow](https://github.com/bjartek/overflow) for testing in Go.
-  - [js-testing](https://github.com/onflow/flow-js-testing) for testing in JS.

docs/build/smart-contracts/best-practices/project-development-tips.md

@@ -173,7 +173,6 @@ which are noteworthy to mention for a typical smart contract project.
 
 Popular testing frameworks to use for cadence are listed here:
 - Cadence: [Cadence Testing Framework](../../smart-contracts/testing.md)
-- Javascript: [Flow JS Testing](../../../tools/flow-js-testing/index.md)
 - Go: [Overflow](https://github.com/bjartek/overflow)
 
 The same person who writes the code should also write the tests.

docs/build/smart-contracts/overview.md

@@ -26,7 +26,6 @@ To build confidently, you will want to set up the appropriate local environment
 - [Flow Emulator](../../tools/emulator/index.md): A lightweight server that simulates the Flow blockchain (strongly recommended during development).
 - [Flow Dev Wallet](https://github.com/onflow/fcl-dev-wallet/): A utility to simulate user wallets in development.
 - [Visual Studio Code Extension](../../tools/vscode-extension/index.mdx): An IDE integration for developing smart contracts.
-- [JS Testing Framework](https://github.com/onflow/flow-js-testing): A framework to test your smart contracts.
 
 ## Storing Data on Flow
 

docs/build/smart-contracts/testing.md

@@ -250,19 +250,13 @@ You can find examples of Go tests in the following projects: [flow-core-contract
 These tests are tied to the emulator but can be refactored to run on testnet
 </Callout>
 
-### JavaScript Tests
-
-Tests in JavaScript can be written using [flow-js-testing](https://github.com/onflow/flow-js-testing).
-
-It is critical to test your applications and contracts thoroughly on the testnet as part of your road to the mainnet. Testing will help you understand how to create stable and robust applications using the Flow development stack.
-
 ## Testing Your Application
 
 ### Automated Testing of Contract Code
 
 All contracts should include test coverage for _all contract functions_. Make sure you've accounted for success and failure cases appropriately.
 
-Tests should also be runnable in automated environments (CI). You can use the [JavaScript testing framework](https://github.com/onflow/flow-js-testing) to create tests for your smart contract code.
+Tests should also be runnable in automated environments (CI). You can use the [Cadence testing utils](https://cadence-lang.org/docs/testing-framework) to create tests for your smart contract code.
 
 ### Stress Testing Live Applications Before Mainnet
 

src/data/tools/index.ts

@@ -114,22 +114,6 @@ const cdcWebpackPlugin: Tool = {
   description: 'Webpack plugin that helps importing Cadence files.',
 };
 
-const jsTestingLibTool: Tool = {
-  repo: {
-    name: 'flow-js-testing',
-    owner: 'onflow',
-  },
-  title: 'JS Testing Library',
-  authorIcon: 'https://avatars.githubusercontent.com/u/62387156?s=64&v=4',
-  authorName: 'onflow',
-  tags: ['documentation', 'active', 'local-dev'],
-  link: '/tools/flow-js-testing/',
-  stars: 38,
-  iconSrc: ToolTestingIconSrc,
-  description:
-    'A Jest based framework to enable Cadence testing via a set of JavaScript methods and tools',
-};
-
 const cadutTool: Tool = {
   repo: {
     name: 'flow-cadut',