CHEATCODES:-
------------------------------------------------------------------------------

 🧪 Testing

* `forge test` → Run tests (fast + parallelized).
* `setUp()` → Runs before every test (fresh state).
* `beforeTest()/beforeTestSetup()` → Setup code for specific tests.
* `assertEq`, `assertTrue`, etc. → Assertions.
* `vm.expectRevert` → Catch reverts.
* `vm.expectEmit` → Check for emitted events.
* **Fuzz Testing** → Auto-generate random inputs.
* **Invariant Testing** → Ensure rules always hold (`assert` properties across fuzz loops).

---

⚡ Cheatcodes (vm.)

* `vm.warp` → Change block timestamp.
* `vm.roll` → Change block number.
* `vm.prank` / `vm.startPrank` / `vm.stopPrank` → Impersonate accounts.
* `vm.deal` → Give ETH to any address.
* `vm.mockCall` / `vm.expectCall` → Mock/verify contract calls.
* `vm.snapshot` / `vm.revertTo` → Save/restore EVM state.
* `vm.fee` / `vm.txGasPrice` → Manipulate gas-related values.
* `vm.env*` → Load env vars (like private keys).

---

🖥️ Scripts & Deployments

* `forge script` → Run Solidity deployment scripts.
* `--broadcast` → Actually send transactions.
* `--verify` → Auto-verify contracts on Etherscan.
* Multi-chain ready → Just switch `--rpc-url`.

---

 🌍 Forking

* `vm.createFork`, `vm.selectFork` → Fork mainnet/testnet.
* `vm.makePersistent` → Keep state between forks.
* Common use: Test Uniswap, Aave, Compound logic on **real blockchain state**.

---

 🔍 Debugging

* `forge test -vvvv` → Detailed logs (tx traces, storage, logs).
* `console.log` / `console2.log` → Print variables while testing.
* `cast` → Inspect chain state (`cast call`, `cast send`, `cast block`, etc.).

---

 🛠️ Developer Utilities

* **Gas Snapshots** → `forge snapshot` compares gas usage across commits.
* **CI Friendly** → Works fast in GitHub Actions / pipelines.
* **FFI (Foreign Function Interface)** → Run external scripts from Solidity (advanced).
* **Configurable via foundry.toml** → Networks, remappings, compiler settings.

---

 🧾 TL;DR – Most Used Daily

1. `forge test` (with fuzz + invariants).
2. `vm.prank`, `vm.warp`, `vm.expectRevert`.
3. Forking with `vm.createFork` for DeFi contracts.
4. Scripts: `forge script ... --broadcast`.
5. Debugging: `forge test -vvvv`, `console.log`.
6. Deploy + Verify in one command.
7. Gas snapshots for optimizations.

🎮 Cheatcodes in Foundry — 🎮

Cheatcodes are special functions provided by Foundry’s vm (Virtual Machine) object that allow you to manipulate the testing environment in ways that are impossible on a real blockchain. They are your "superpowers" for writing powerful, flexible, and realistic tests.

⚠️ Important Note: Cheatcodes are only available in tests and scripts. They are disabled on real networks. They are not "cheating" in a bad sense — they are essential tools for robust testing.

📚 1. What are Cheatcodes?

Cheatcodes are functions from the Vm interface (usually accessed via the global vm variable in your test contracts) that let you:

• Manipulate time and block numbers.
• Change account balances and storage slots.
• Impersonate any account (even if you don’t have its private key).
• Fork any blockchain (mainnet, testnet) into your local test environment.
• Call external programs (like curl or node) from within your Solidity test.
• And much more!

You get access to vm by inheriting from the Test contract in your test file:

import "forge-std/Test.sol";

contract MyTest is Test {
    // You can now use vm.<cheatcodeName>()
}

🕰️ 2. Environment Manipulation Cheatcodes

These cheatcodes let you control the blockchain's "state" during your tests.

A. vm.warp(uint256 timestamp)