implement contract testing and readme update

README.md

@@ -18,7 +18,7 @@ a reward for doing sampling
 
 The following process outlines how clients can submit quantum circuits for sampling using the DQPU contract:
 
-1. **Client Submits Job**: A *Client* sends a quantum circuit along with a reward to the DQPU smart contract. The circuit data is uploaded to a distributed file storage system like IPFS. The smart contract adds the job to a queue in a 'pending' state with the associated reward.
+1. **Client Submits Job**: A *Client* sends a quantum circuit along with a reward to the DQPU smart contract. The circuit data is uploaded to a distributed file storage system like IPFS. The smart contract adds the job to a queue in a 'pending-validation' state with the associated reward.
 
 2. **Verifier Validates Circuit**: A *Verifier*[^1] validates the submitted circuit. This might involve checks for syntax errors or ensuring the circuit is within allowed parameters. The verifier also adds special verification elements (traps) into the circuit. Once validated, the job moves to a 'waiting' state, becomes 'invalid' otherwise.
 
@@ -121,9 +121,9 @@ dqpu-sampler --min-reward 0.0009 --sampler aersimulator
 
 ## Usage: running a verifier node
 
-A verifier node continuously pool the DQPU smart contract waiting for new 'pending' and 'validating' jobs. When a new job appear, the verifiers:
-- 'pending' job are checked for quantum circuit validity, and trap qubits are inserted
-- 'validating' job are checked for trap verification
+A verifier node continuously pool the DQPU smart contract waiting for new 'pending-validation' and 'validating-result' jobs. When a new job appear, the verifiers:
+- 'pending-validation' job are checked for quantum circuit validity, and trap qubits are inserted
+- 'validating-result' job are checked for trap verification
 
 After every validation, the verifier receives a percentage of the job reward.
 

dqpu-contract/package.json

@@ -5,7 +5,8 @@
   "type": "module",
   "scripts": {
     "build": "near-sdk-js build src/contract.ts build/dqpu.wasm",
-    "test": "$npm_execpath run build && ava -- ./build/dqpu.wasm"
+    "test": "$npm_execpath run build && ava -- ./build/dqpu.wasm",
+    "only-test": "ava -- ./build/dqpu.wasm"
   },
   "dependencies": {
     "near-cli": "^4.0.8",

dqpu-contract/sandbox-ts/main.ava.ts

@@ -32,6 +32,8 @@ test.beforeEach(async (t) => {
     process.argv[2],
   );
 
+  await contract.call(contract, "init", {})
+
   // Save state for test runs, it is unique for each test
   t.context.accounts = { root, contract };
 });
@@ -43,11 +45,17 @@ test.afterEach.always(async (t) => {
   });
 });
 
-// test('returns the default greeting', async (t) => {
-//   const { contract } = t.context.accounts;
-//   const greeting: string = await contract.view('get_greeting', {});
-//   t.is(greeting, 'Hello');
-// });
+test('returns the number of handled amount', async (t) => {
+  const { contract } = t.context.accounts;
+  const amount: string = await contract.view('get_handled_amount', {});
+  t.is(amount, '0');
+});
+
+test('returns the number of jobs', async (t) => {
+  const { contract } = t.context.accounts;
+  const amount: number = await contract.view('get_number_of_jobs', {});
+  t.is(amount, 0);
+});
 
 // test('changes the greeting', async (t) => {
 //   const { root, contract } = t.context.accounts;

dqpu-contract/src/contract.ts

@@ -12,7 +12,7 @@
 // See the License for the specific language governing permissions and
 // limitations under the License.
 
-import { NearBindgen, near, call, view, UnorderedMap, assert } from 'near-sdk-js';
+import { NearBindgen, near, call, view, UnorderedMap, assert, initialize } from 'near-sdk-js';
 import { AccountId } from 'near-sdk-js/lib/types';
 import { Job, JobStatus } from './model';
 
@@ -24,6 +24,7 @@ class DQPU {
   latest_jid: bigint = BigInt(0);
   money_handled: bigint = BigInt(0);
 
+  @initialize({ privateFunction: true })
   init() {
     this.owner = near.predecessorAccountId();
     this.verifiers.set(this.owner, this.owner);