0 passing !!

[chrismogab]

hi i am running my yarn hardhat test and i am gettin 0 passing when i run the code. i saw that patrick told other people to change file name from .tests to .test but this is not my case i already have it on .test . what could be the problem? no matter how many functions i include i keep on getting 0 passing.
how can i solve it.
here is my Raffle.test.js file :

// unit tests bas lal development chains
const { assert, expect } = require("chai")
const { getNamedAccounts, deployments, ethers } = require("hardhat")
const { developmentChains, networkConfig } = require("../../helper-hardhat-config")

!developmentChains.includes(network.name)
    ? describe.skip
    : describe("Raffle Unit Tests", async function () {
          let raffle, vrfCoordinatorV2Mock
          const chainId = network.Config.chainId
          beforeEach(async function () {
              const { deployer } = await getNamedAccounts()
              await deployments.fixture(["all"])
              raffle = await ethers.getContract("Raffle", deployer)
              vrfCoordinatorV2Mock = await ethers.getContract("VRFCoordinatorV2Mock", deployer)
          })
          describe("constructor", async function () {
              it("Initializes the raffle correctly", async function () {
                  //ideallly we make our tests have just 1 assert per "it"
                  const raffleState = await raffle.getRaffleState()
                  const interval = await raffle.getInterval()
                  assert.equal(raffleState.toString(), "0")
                  assert.equal(interval.toString(), networkConfig[chainId]["interval"])
                  //bethot .to string eza its gna be a big number
              })
          })
          describe("enterRaffle", async function () {
              it("reverts when your don't pay enough", async function () {
                  await expect(raffle.enterRaffle()).to.be.revertedWith(
                      "Raffle__SendMoreToEnterRaffle"
                  )
              })
          })
      })

[alymurtazamemon]

@chrismogab First of all you should check whether the execution executes these tests or not. Add the console.log("with any message") to these tests and show the terminal.

[mghildiy]

Just have a simple test, and put a simple assertion like 2 == 2, and see if it passes. If not then configurations can be checked. If yes, then tests have issues.

[chrismogab]

i added a console.log and ran yarn hardhat test in my console this is what i got :::

chrismogab@Christophers-MacBook-Air hardhat-smartcontract-lottery % yarn hardhat test
yarn run v1.22.19
$ /Users/chrismogab/hardhat-smartcontract-lottery/node_modules/.bin/hardhat test

  0 passing (14ms)

✨  Done in 2.21s.

this is my new file:

// unit tests bas lal development chains
const { assert, expect } = require("chai")
const { getNamedAccounts, deployments, ethers } = require("hardhat")
const { developmentChains, networkConfig } = require("../../helper-hardhat-config")

!developmentChains.includes(network.name)
    ? describe.skip
    : describe("Raffle Unit Tests", async function () {
          let raffle, vrfCoordinatorV2Mock
          const chainId = network.Config.chainId
          beforeEach(async function () {
              const { deployer } = await getNamedAccounts()
              await deployments.fixture(["all"])
              raffle = await ethers.getContract("Raffle", deployer)
              vrfCoordinatorV2Mock = await ethers.getContract("VRFCoordinatorV2Mock", deployer)
          })
          describe("constructor", async function () {
              it("Initializes the raffle correctly", async function () {
                  //ideallly we make our tests have just 1 assert per "it"
                  const raffleState = await raffle.getRaffleState()
                  const interval = await raffle.getInterval()
                  assert.equal(raffleState.toString(), "0")
                  assert.equal(interval.toString(), networkConfig[chainId]["interval"])
                  //bethot .to string eza its gna be a big number
              })
          })
          describe("enterRaffle", async function () {
              it("reverts when your don't pay enough", async function () {
                  await expect(raffle.enterRaffle()).to.be.revertedWith(
                      "Raffle__SendMoreToEnterRaffle"
                  )
                  console.log("chris")
              })
          })
      })

[alymurtazamemon]

@chrismogab push the code on GitHub and paste the link here I will look into all issues.

[mghildiy]

So I think we still don''t know whether test has issues or some config is wrong/missing. So remove all tests from your test file, and keep a simple test which just check something easy:

it("just a simple sanity test", async function () {
    assert.equal(2, 2);
  });

If this runs fine, then means issue is in test code. It even this is not working then some config issues are there, and then we can concentrate there.

[NagoriMustakim]

Create a Folder "test" and inside it create another Folder "unit" and inside the unit folder create Raffle.test.js
paste this code there and let me know it working or not

// unit tests bas lal development chains
const { assert, expect } = require("chai")
const { getNamedAccounts, deployments, ethers } = require("hardhat")
const { developmentChains, networkConfig } = require("../../helper-hardhat-config")

!developmentChains.includes(network.name)
    ? describe.skip
    : describe("Raffle Unit Tests", async function () {
          let raffle, vrfCoordinatorV2Mock
          const chainId = network.Config.chainId
          beforeEach(async function () {
              const { deployer } = await getNamedAccounts()
              await deployments.fixture(["all"])
              raffle = await ethers.getContract("Raffle", deployer)
              vrfCoordinatorV2Mock = await ethers.getContract("VRFCoordinatorV2Mock", deployer)
          })
          describe("constructor", async function () {
              it("Initializes the raffle correctly", async function () {
                  //ideallly we make our tests have just 1 assert per "it"
                  const raffleState = await raffle.getRaffleState()
                  const interval = await raffle.getInterval()
                  assert.equal(raffleState.toString(), "0")
                  assert.equal(interval.toString(), networkConfig[chainId]["interval"])
                  //bethot .to string eza its gna be a big number
              })
          })
          describe("enterRaffle", async function () {
              it("reverts when your don't pay enough", async function () {
                  await expect(raffle.enterRaffle()).to.be.revertedWith(
                      "Raffle__SendMoreToEnterRaffle"
                  )
              })
          })
      })

[chrismogab]

tried that i still got 0 passing

[krakxn]

• const chainId = network.Config.chainId typo, should be network.config.chainId

• Both the getContract functions should be getContractAt

Hope this helps

[krakxn]

@chrismogab Do this please

[chrismogab]

man thanks so much that actually solved the problem but right after i ran it i got an error: Error: call revert exception [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (method="getRaffleState()", data="0x", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.6.4).
i dont know why i keep getting these errors when i am copying patricks code(like before in patricks code he only had getContract, not getContractAt)

[krakxn]

You can use getContract too - but after doing something like await xyzcontract.deployed().

By the way, is the original error answered? As the problem is now with getRaffleState(); if so, I would recommend creating a new discussion about that to keep this one organized for others to see.