feat: Add NotApplicable benchmark result type

CONTRIBUTING.md

@@ -371,6 +371,7 @@ export const BenchmarkResults = {
   Pass: "passed",
   PartialPass: "partially-passed",
   Fail: "failed",
+  NotApplicable: "not-applicable",
 } as const;
 
 export type BenchmarkResult = (typeof BenchmarkResults)[keyof typeof BenchmarkResults];
@@ -444,10 +445,23 @@ export interface AcceptanceTestBenchmarkPartialPass
 export interface AcceptanceTestBenchmarkFail
   extends AcceptanceTestBenchmarkAbstract<typeof BenchmarkResults.Fail> {}
 
-export type AcceptanceTestBenchmark =
+/**
+ * Represents a benchmark of an {@link AcceptanceTest} on an {@link App} against a {@link BestPractice},
+ * that is not applicable to the acceptance test scenario.
+ * Most often, this is because the app doesn't use ENS at all,
+ * in places where it should.
+ */
+export interface NotApplicableAcceptanceTestBenchmark
+  extends AcceptanceTestBenchmarkAbstract<typeof BenchmarkResults.NotApplicable> {}
+
+export type ApplicableAcceptanceTestBenchmark =
   | AcceptanceTestBenchmarkPass
   | AcceptanceTestBenchmarkPartialPass
   | AcceptanceTestBenchmarkFail;
+
+export type AcceptanceTestBenchmark =
+  | ApplicableAcceptanceTestBenchmark
+  | NotApplicableAcceptanceTestBenchmark;
 ```
 
 3. Add notes made during the benchmarking process in the form of a simple JSX element that is a part of the new item in the `benchmarks` record. For reference, see 

ensawards.org/data/acceptance-tests/types.ts

@@ -44,6 +44,7 @@ export interface AcceptanceTest {
   examplePartialPass?: AcceptanceTestBenchmarkPartialPass;
   exampleFail?: AcceptanceTestBenchmarkFail;
 }
+// TODO: Decided that there is no point in adding an example for NotApplicable.
 
 /**
  * Represents the benchmark of an {@link AcceptanceTest} on an {@link App} against a {@link BestPractice}.
@@ -92,7 +93,20 @@ export interface AcceptanceTestBenchmarkPartialPass
 export interface AcceptanceTestBenchmarkFail
   extends AcceptanceTestBenchmarkAbstract<typeof BenchmarkResults.Fail> {}
 
-export type AcceptanceTestBenchmark =
+/**
+ * Represents a benchmark of an {@link AcceptanceTest} on an {@link App} against a {@link BestPractice},
+ * that is not applicable to the acceptance test scenario.
+ * Most often, this is because the app doesn't use ENS at all,
+ * in places where it should.
+ */
+export interface NotApplicableAcceptanceTestBenchmark
+  extends AcceptanceTestBenchmarkAbstract<typeof BenchmarkResults.NotApplicable> {}
+
+export type ApplicableAcceptanceTestBenchmark =
   | AcceptanceTestBenchmarkPass
   | AcceptanceTestBenchmarkPartialPass
   | AcceptanceTestBenchmarkFail;
+
+export type AcceptanceTestBenchmark =
+  | ApplicableAcceptanceTestBenchmark
+  | NotApplicableAcceptanceTestBenchmark;

ensawards.org/data/acceptance-tests/utils.test.ts

@@ -25,25 +25,32 @@ describe("Acceptance test utils", () => {
       },
     );
 
-    it("Returns `BenchmarkResults.Fail` if all defined benchmarks are `BenchmarkResults.Fail`", () => {
-      const expectedResult = BenchmarkResults.Fail;
+    it(
+      "Returns `BenchmarkResults.Fail` if in all defined benchmarks there is at least one `BenchmarkResults.Fail`" +
+        " and all others are `BenchmarkResults.Fail` or `BenchmarkResults.NotApplicable`",
+      () => {
+        const expectedResult = BenchmarkResults.Fail;
 
-      const inputBenchmarks = {
-        "mock-acceptance-test-1": createMockAcceptanceTestBenchmark(BenchmarkResults.Fail),
-        "mock-acceptance-test-2": createMockAcceptanceTestBenchmark(BenchmarkResults.Fail),
-        "mock-acceptance-test-3": undefined,
-        // pending benchmarks should be ignored in this case of the generalization
-      } as const satisfies AcceptanceTestBenchmarks;
+        const inputBenchmarks = {
+          "mock-acceptance-test-1": createMockAcceptanceTestBenchmark(BenchmarkResults.Fail),
+          "mock-acceptance-test-2": createMockAcceptanceTestBenchmark(BenchmarkResults.Fail),
+          "mock-acceptance-test-3": createMockAcceptanceTestBenchmark(
+            BenchmarkResults.NotApplicable,
+          ),
+          "mock-acceptance-test-4": undefined,
+          // pending benchmarks should be ignored in this case of the generalization
+        } as const satisfies AcceptanceTestBenchmarks;
 
-      expect(
-        generalizeAcceptanceTestBenchmarks(inputBenchmarks),
-        "generalizeAcceptanceTestBenchmarks should return `BenchmarkResults.Fail`",
-      ).toEqual(expectedResult);
-    });
+        expect(
+          generalizeAcceptanceTestBenchmarks(inputBenchmarks),
+          "generalizeAcceptanceTestBenchmarks should return `BenchmarkResults.Fail`",
+        ).toEqual(expectedResult);
+      },
+    );
 
     it(
       "Returns `BenchmarkResults.PartialPass` if at least one defined benchmark is `BenchmarkResults.Fail`" +
-        " and at least one defined benchmark is `BenchmarkResults.Pass`",
+        " and at least one defined benchmark is `BenchmarkResults.Pass` or `BenchmarkResults.PartialPass`",
       () => {
         const expectedResult = BenchmarkResults.PartialPass;
 
@@ -78,6 +85,22 @@ describe("Acceptance test utils", () => {
       ).toEqual(expectedResult);
     });
 
+    it("Returns `BenchmarkResults.NotApplicable` if all defined benchmarks are `BenchmarkResults.NotApplicable`", () => {
+      const expectedResult = BenchmarkResults.NotApplicable;
+
+      const inputBenchmarks = {
+        "mock-acceptance-test-1": createMockAcceptanceTestBenchmark(BenchmarkResults.NotApplicable),
+        "mock-acceptance-test-2": createMockAcceptanceTestBenchmark(BenchmarkResults.NotApplicable),
+        "mock-acceptance-test-3": undefined,
+        // pending benchmarks should be ignored in this case of the generalization
+      } as const satisfies AcceptanceTestBenchmarks;
+
+      expect(
+        generalizeAcceptanceTestBenchmarks(inputBenchmarks),
+        "generalizeAcceptanceTestBenchmarks should return `BenchmarkResults.NotApplicable`",
+      ).toEqual(expectedResult);
+    });
+
     it("Returns `undefined` if all benchmarks are `undefined` (pending)", () => {
       const expectedResult = undefined;
 

ensawards.org/data/acceptance-tests/utils.ts

@@ -55,15 +55,20 @@ export const getAcceptanceTestBenchmarksByApp = (
  *       {@link BenchmarkResults.Pass}
  *     - and all others are {@link BenchmarkResults.Pass} or {@link BenchmarkResults.PartialPass}
  *
- * - Returns {@link BenchmarkResults.Fail} if all defined benchmarks
- * are {@link BenchmarkResults.Fail},
+ * - Returns {@link BenchmarkResults.Fail} if:
+ *     - in all defined benchmarks there is at least one
+ *       {@link BenchmarkResults.Fail}
+ *     - and all others are {@link BenchmarkResults.Fail} or {@link BenchmarkResults.NotApplicable}
  *
  * - Returns {@link BenchmarkResults.PartialPass} if:
  *     - at least one defined benchmark is {@link BenchmarkResults.Fail}
  *       and at least one defined benchmark is
  *       {@link BenchmarkResults.Pass} or {@link BenchmarkResults.PartialPass},
  *     - or all defined benchmarks are {@link BenchmarkResults.PartialPass},
  *
+ * - Returns {@link BenchmarkResults.NotApplicable} if:
+ *    - all defined benchmarks are {@link BenchmarkResults.NotApplicable}
+ *
  * -  Returns `undefined` if all benchmarks are `undefined` (pending).
  */
 export const generalizeAcceptanceTestBenchmarks = (
@@ -87,6 +92,14 @@ export const generalizeAcceptanceTestBenchmarks = (
     return BenchmarkResults.PartialPass;
   }
 
+  const allDefinedBenchmarksNotApplicable = definedBenchmarkResults.every(
+    (result) => result === BenchmarkResults.NotApplicable,
+  );
+
+  if (allDefinedBenchmarksNotApplicable) {
+    return BenchmarkResults.NotApplicable;
+  }
+
   // For now, we'll explicitly treat pass and partial pass equally
   // (For cases where not all benchmarks are partial pass)
   const allDefinedBenchmarksPass = definedBenchmarkResults.every(
@@ -97,8 +110,10 @@ export const generalizeAcceptanceTestBenchmarks = (
     return BenchmarkResults.Pass;
   }
 
+  // For now, we'll explicitly treat fail and not applicable equally
+  // (For cases where not all benchmarks are not applicable)
   const allDefinedBenchmarksFail = definedBenchmarkResults.every(
-    (result) => result === BenchmarkResults.Fail,
+    (result) => result === BenchmarkResults.Fail || result === BenchmarkResults.NotApplicable,
   );
 
   if (allDefinedBenchmarksFail) {

ensawards.org/data/apps/binance-exchange/benchmarks/index.tsx

@@ -16,19 +16,28 @@ import { cn } from "@/utils/tailwindClassConcatenation";
 import correctlyResolveEnsv2TestNameAddressProofImageCopyTrading from "./correctly-resolve-ensv2-test-name-address-proof-copy-trading.gif";
 import correctlyResolveEnsv2TestNameAddressProofImageWithdrawal from "./correctly-resolve-ensv2-test-name-address-proof-withdrawal.png";
 
+// TODO: Here we can test how the layout looks
+// when the explanation for the not applicable result is separated
+// from the result description and joined with it.
+// In my opinion the separation looks better but I'm open to using either of these.
 const benchmarks: BestPracticeBenchmarks = {
   "ensv2-ready-resolution": {
     "correctly-resolve-ensv2-test-name-address": {
-      result: BenchmarkResults.Fail,
+      result: BenchmarkResults.NotApplicable,
       contributions: [
         { from: contributors.y3drk, lastUpdated: parseTimestamp("2026-06-11T07:30:06Z") },
       ],
       notes: (
         <div className={cn(acceptanceTestDetailsContainerStyles, "w-full")}>
           <p className="w-full">
             ENSv2 ready resolution was tested using the search tool in the &quot;copy-trading&quot;
-            flow. The app either doesn't allow using ENS name as the trader identifier or fails to
-            resolve it, both of which we interpret as a failure.
+            flow. The app doesn't support the use of ENS names at all as the trader identifier.
+            <br />
+            <br />
+            While that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <img
             alt="Binance exchange doesn't allow ENS name as trader in the copy-trading flow"
@@ -37,8 +46,11 @@ const benchmarks: BestPracticeBenchmarks = {
           />
           <p className="w-full">
             The ENSv2 ready resolution was also tested using the &quot;withdrawal&quot; flow. The
-            app doesn't allow using ENS name as the recipient identifier, which we interpret as a
-            failure.
+            app doesn't support the use of ENS names at all as the recipient identifier. While
+            that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <img
             alt="Binance exchange doesn't allow ENS name as recipient in the withdrawal flow"

ensawards.org/data/apps/binance-wallet/benchmarks/index.tsx

@@ -28,15 +28,21 @@ const benchmarks: BestPracticeBenchmarks = {
   },
   "ensv2-ready-resolution": {
     "correctly-resolve-ensv2-test-name-address": {
-      result: BenchmarkResults.Fail,
+      result: BenchmarkResults.NotApplicable,
       contributions: [
         { from: contributors.y3drk, lastUpdated: parseTimestamp("2026-06-11T07:33:06Z") },
       ],
       notes: (
         <div className={cn(acceptanceTestDetailsContainerStyles, "w-full")}>
           <p className="w-full">
             ENSv2 ready resolution was tested using the &quot;send&quot; flow. The wallet doesn't
-            allow using ENS name as the recipient identifier, which we interpret as a failure.
+            support the use of ENS names at all as the recipient identifier.
+            <br />
+            <br />
+            While that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <img
             alt="Binance Wallet doesn't allow ENS name as recipient in the send flow"

ensawards.org/data/apps/cryptocom-exchange/benchmarks/index.tsx

@@ -18,15 +18,21 @@ import correctlyResolveEnsv2TestNameAddressProofImage from "./correctly-resolve-
 const benchmarks: BestPracticeBenchmarks = {
   "ensv2-ready-resolution": {
     "correctly-resolve-ensv2-test-name-address": {
-      result: BenchmarkResults.Fail,
+      result: BenchmarkResults.NotApplicable,
       contributions: [
         { from: contributors.y3drk, lastUpdated: parseTimestamp("2026-06-11T13:47:40Z") },
       ],
       notes: (
         <div className={cn(acceptanceTestDetailsContainerStyles, "w-full")}>
           <p className="w-full">
             ENSv2 ready resolution was tested using the &quot;withdrawal&quot; flow. The app doesn't
-            allow using ENS name as the recipient identifier, which we interpret as a failure.
+            support the use of ENS names at all as the recipient identifier.
+            <br />
+            <br />
+            While that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <img
             alt="Crypto.com exchange doesn't allow ENS name as recipient in the withdrawal flow"

ensawards.org/data/apps/kraken-exchange/benchmarks/index.tsx

@@ -18,15 +18,21 @@ import correctlyResolveEnsv2TestNameAddressProofImage from "./correctly-resolve-
 const benchmarks: BestPracticeBenchmarks = {
   "ensv2-ready-resolution": {
     "correctly-resolve-ensv2-test-name-address": {
-      result: BenchmarkResults.Fail,
+      result: BenchmarkResults.NotApplicable,
       contributions: [
         { from: contributors.y3drk, lastUpdated: parseTimestamp("2026-06-11T10:47:44Z") },
       ],
       notes: (
         <div className={cn(acceptanceTestDetailsContainerStyles, "w-full")}>
           <p className="w-full">
             ENSv2 ready resolution was tested using the &quot;withdrawal&quot; flow. The app doesn't
-            allow using ENS name as the recipient identifier, which we interpret as a failure.
+            support the use of ENS names at all as the recipient identifier.
+            <br />
+            <br />
+            While that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <img
             alt="Kraken exchange doesn't allow ENS name as recipient in the withdrawal flow"

ensawards.org/data/apps/okx-exchange/benchmarks/index.tsx

@@ -18,15 +18,21 @@ import correctlyResolveEnsv2TestNameAddressProofImage from "./correctly-resolve-
 const benchmarks: BestPracticeBenchmarks = {
   "ensv2-ready-resolution": {
     "correctly-resolve-ensv2-test-name-address": {
-      result: BenchmarkResults.Fail,
+      result: BenchmarkResults.NotApplicable,
       contributions: [
         { from: contributors.y3drk, lastUpdated: parseTimestamp("2026-06-11T11:42:14Z") },
       ],
       notes: (
         <div className={cn(acceptanceTestDetailsContainerStyles, "w-full")}>
           <p className="w-full">
             ENSv2 ready resolution was tested using the &quot;withdrawal&quot; flow. The app doesn't
-            allow using ENS name as the recipient identifier, which we interpret as a failure.
+            support the use of ENS names at all as the recipient identifier.
+            <br />
+            <br />
+            While that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <img
             alt="OKX exchange doesn't allow ENS name as recipient in the withdrawal flow"

ensawards.org/data/apps/readyx-wallet/benchmarks/index.tsx

@@ -28,15 +28,21 @@ const benchmarks: BestPracticeBenchmarks = {
   },
   "ensv2-ready-resolution": {
     "correctly-resolve-ensv2-test-name-address": {
-      result: BenchmarkResults.Fail,
+      result: BenchmarkResults.NotApplicable,
       contributions: [
         { from: contributors.y3drk, lastUpdated: parseTimestamp("2026-06-08T16:18:00Z") },
       ],
       notes: (
         <div className={cn(acceptanceTestDetailsContainerStyles, "w-full")}>
           <p className="w-full">
-            ENSv2 ready resolution was tested using the &quot;send&quot; flow. The app doesn't allow
-            using ENS name as the recipient identifier, which we interpret as a failure.
+            ENSv2 ready resolution was tested using the &quot;send&quot; flow. The app doesn't
+            support the use of ENS names at all as the recipient identifier.
+            <br />
+            <br />
+            While that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <img
             alt="ReadyX doesn't allow ENS name as recipient in the send flow"

ensawards.org/data/apps/robinhood-exchange/benchmarks/index.tsx

@@ -19,15 +19,21 @@ import correctlyResolveEnsv2TestNameAddressProofImage2 from "./correctly-resolve
 const benchmarks: BestPracticeBenchmarks = {
   "ensv2-ready-resolution": {
     "correctly-resolve-ensv2-test-name-address": {
-      result: BenchmarkResults.Fail,
+      result: BenchmarkResults.NotApplicable,
       contributions: [
         { from: contributors.y3drk, lastUpdated: parseTimestamp("2026-06-15T06:59:00Z") },
       ],
       notes: (
         <div className={cn(acceptanceTestDetailsContainerStyles, "w-full")}>
           <p className="w-full">
-            ENSv2 ready resolution was tested using the &quot;send&quot; flow. The app doesn't allow
-            using ENS name as the recipient identifier, which we interpret as a failure.
+            ENSv2 ready resolution was tested using the &quot;send&quot; flow. The app doesn't
+            support the use of ENS names at all as the recipient identifier.
+            <br />
+            <br />
+            While that's a key issue that this app is encouraged to improve, this best practice is
+            applicable specifically to apps that already have an existing ENS integration and making
+            sure existing integrations are ENSv2 compatible. Therefore, for this best practice we
+            apply a rating of not applicable.
           </p>
           <div className="flex flex-col justify-start items-center gap-5">
             <img