feat: add unit test for app store

docs/test.md

@@ -0,0 +1,33 @@
+# Test
+
+
+##  How to write a test
+
+it's essential to adhere to the following principles:
+
+- Test descriptions should be meaningful.
+- Use only English lowercase letters for descriptions.
+- Test descriptions is better to start with the verb.
+- Provide specific details about the functionality being tested.
+- Use descriptive names for tests to facilitate understanding.
+- Organize tests logically to enhance readability and navigation.
+- Use edge cases and boundary conditions to ensure comprehensive testing.
+- You can use `@faker-js/faker` library to create fake data
+
+
+
+## Examples
+
+To clarify the topic, some examples of token sort tests are given:
+
+good example:
+ - put pinned tokens first
+ - put native tokens first
+ - should be first result when address contains searched term
+
+bad example:
+- pinned tokens are displayed first
+- put pinned tokens
+- Put Pinned tokens first
+- when address contains searched term, should be first
+

package.json

@@ -61,6 +61,7 @@
     "@babel/core": "^7.22.5",
     "@commitlint/cli": "^18.6.1",
     "@commitlint/config-conventional": "^18.6.2",
+    "@faker-js/faker": "^8.4.1",
     "@lingui/cli": "^4.2.1",
     "@nrwl/workspace": "^15.9.2",
     "@types/react": "^18.0.26",

widget/embedded/package.json

@@ -16,7 +16,10 @@
     "ts-check": "tsc --declaration --emitDeclarationOnly -p ./tsconfig.json",
     "clean": "rimraf dist",
     "format": "prettier --write '{.,src}/**/*.{ts,tsx}'",
-    "lint": "eslint \"**/*.{ts,tsx}\" --ignore-path ../../.eslintignore"
+    "lint": "eslint \"**/*.{ts,tsx}\" --ignore-path ../../.eslintignore",
+    "test": "vitest",
+    "test:watch": "vitest --watch",
+    "test:coverage": "vitest run --coverage"
   },
   "dependencies": {
     "@lingui/core": "4.2.1",
@@ -49,4 +52,4 @@
   "publishConfig": {
     "access": "public"
   }
-}
+}