Add the final quiz....finally

Author: elPiablo

pages/lessons/projects/4.mdx

@@ -22,7 +22,7 @@ Here you'll:
 - Walk away with many practical tests for smart contracts
 - Nibble on some food for thought about test-driven development
 
-<SideDrawer buttonText="Warm-up Questions" title="Some previous knowledge, some prediction">
+<SideDrawer buttonText="Warm-up Questions" title="Check out Your Previous Knowledge">
       <Question question="lesson-4/1-intro/Q1" />
       <Question question="lesson-4/1-intro/Q2" />
       <Question question="lesson-4/1-intro/Q3" />
@@ -61,13 +61,10 @@ you have all the Hardhat dependencies installed.
 Otherwise let's create a new Hardhat project and copy in the contract which
 we'll be testing.
 
-{/* DO WE NEED TO MAKE SURE WE HAVE THE MOST RECENT VERSION OF NPM? LET'S SEE IF THERE'S IMPROVEMENT */}
-
 To create a new project, please refer to _Lesson 3 - Tier NFTs_ and search for
 the “First things first 👷‍♂️" section to get your project going. Follow the steps
 until "Let’s start coding”, then open up your code editor.
 
-{/* AND DO WE NEED TO ENSURE LEARNERS ACTUALLY FINISH ALL THE STEPS IN LESSON 3 FOR hardhat configurations, deployment variables, etc */}
 
 _If you are using VSCode, type `code .` in your terminal to open VSCode._
 
@@ -945,17 +942,19 @@ With TDD:
   Bolting on tests after the fact can be painful and boring, and you lose the
   potential code improvements you can make when you test as you go.
 
-<br/>
+<br/><br/>
 <Quiz quiz="lesson-4-quiz" />
-<br/>
+<br/><br/>
 
 Go forth, test, and prosper knowing you have confidence in the code you're
 deploying into the world.
 
 import { ContributorFooter } from '../../../components/mdx/ContributorFooter'
 
+
 <ContributorFooter
   authors={['brianfive']}
   reviewers={['piablo', 'georgemac510']}
-  contributors={[]}
+  contributors={[]} 
 />
+

utils/quizzes/lesson-4-quiz.json

@@ -1,6 +1,25 @@
 {
   "title": "Quiz: Lesson 4",
   "questions": [
+    {
+      "question": "Choose those which automated testing of smart contracts can help achieve?",
+      "options": [
+        {
+          "answer": "Faster development and deployment process."
+        },
+        {
+          "answer": "Finding every possible bug and vulnerability."
+        },
+        {
+          "answer": "Improving the overall code quality.",
+          "correct": true
+        },
+        {
+          "answer": "Ensuring the smart contract is free of errors.",
+          "correct": true
+        }
+      ]
+    },
     {
       "question": "Which testing approach is recommended for ensuring a secure smart contract?",
       "options": [
@@ -20,58 +39,174 @@
       ]
     },
     {
-      "question": "What can automated testing of smart contracts help achieve?",
+      "question": "Which three variables did we define with the 'let' keyword to use in our test suite?",
       "options": [
         {
-          "answer": "Faster development and deployment process."
+          "answer": "tokenTier, tierID, onlyOwner."
         },
         {
-          "answer": "Finding every possible bug and vulnerability."
+          "answer": "symbol, collection, provider."
         },
         {
-          "answer": "Improving the overall code quality.",
+          "answer": "otherUser, contract, owner.",
           "correct": true
+        }
+      ]
+    },
+    {
+      "question": "During testing, which role does the 'beforeEach' function serve in the test suite?",
+      "options": [
+        {
+          "answer": "It deploys a new instance of the contract before executing each test case."
         },
         {
-          "answer": "Ensuring the smart contract is free of errors.",
+          "answer": "It sets up the testing environment, and initializes contract variables once before all test cases.",
+          "correct": true
+        },
+        {
+          "answer": "It performs cleanup tasks after each test case is executed."
+        },
+        {
+          "answer": "It executes the contract's constructor function before running any tests."
+        }
+      ]
+    },
+    {
+      "question": "In the context of our testing, what role does 'describe' play?",
+      "options": [
+        {
+          "answer": "It describes the purpose of the smart contract."
+        },
+        {
+          "answer": "It organises and groups related tests together.",
+          "correct": true
+        },
+        {
+          "answer": "It handles asynchronous operations in the test suite."
+        }
+      ]
+    },
+    {
+      "question": "The role of the 'it' function in a test suite is to:",
+      "options": [
+        {
+          "answer": "organise and group related tests together."
+        },
+        {
+          "answer": "irritate the knights formerly known as The Knights of Ni"
+        },
+        {
+          "answer": "define an individual test case or scenario.",
           "correct": true
+        },
+        {
+          "answer": "handle asynchronous operations in the test suite."
         }
       ]
     },
     {
-      "question": "Which best describes 'gas' in the context of smart contracts?",
+      "question": "How is 'expect' used to verify test results?",
       "options": [
         {
-          "answer": "The cost of deploying a smart contract on the blockchain."
+          "answer": "It waits for the test cases for the entire suite of tests."
         },
         {
-          "answer": "The unit of currency used in smart contract transactions."
+          "answer": "It groups multiple tests together under one description."
         },
         {
-          "answer": "A measure of the computational effort required to execute a transaction or contract.",
+          "answer": "It waits for an asynchronous call to complete, and returns the result."
+        },
+        {
+          "answer": "It compares the actual result with the anticipated outcome to check if they match.",
+          "correct": true
+        }
+      ]
+    },
+    {
+      "question": "In the 'withdraw()' tests, what do the 'await contract.mint()' calls before each test ensure?",
+      "options": [
+        {
+          "answer": "The contract owner's wallet balance is increased.",
           "correct": true
         },
         {
-          "answer": "The reward given to validators for running a validator node."
+          "answer": "The 'withdraw()' function can be executed successfully."
+        },
+        {
+          "answer": "The contract has enough Ether to allow withdrawal."
+        },
+        {
+          "answer": "The contract has at least one minted TierNFT.",
+          "correct": true
         }
       ]
     },
     {
-      "question": "What are some potential risks of deploying a smart contract without proper testing?",
+      "question": "What is the purpose of refactoring the original 'tokenURI()' method into helper functions?",
       "options": [
         {
-          "answer": "Loss of funds",
+          "answer": "To optimize contract performance."
+        },
+        {
+          "answer": "To maintain backward compatibility."
+        },
+        {
+          "answer": "To make the tokenURI() method more testable and maintainable.",
           "correct": true
+        }
+      ]
+    },
+    {
+      "question": "Why is it beneficial to have tests for the helper functions?",
+      "options": [
+        {
+          "answer": "To receive gas refunds"
+        },
+        {
+          "answer": "To decrease the number of transactions"
+        },
+        {
+          "answer": "To ensure the correctness and reliability of the smart contract's behavior.",
+          "correct": true
+        },
+        {
+          "answer": "To optimize the contract deployment process"
+        }
+      ]
+    },
+    {
+      "question": "Why is it essential to test the original 'tokenURI()' method before and after refactoring?",
+      "options": [
+        {
+          "answer": "To verify that the helper functions are working correctly"
+        },
+        {
+          "answer": "To ensure that the refactoring did not introduce bugs or alter functionality",
+          "correct": true
+        },
+        {
+          "answer": "To test cross-browser compatibility"
+        },
+        {
+          "answer": "To measure performance improvements"
+        }
+      ]
+    },
+    {
+      "question": "Why is it essential to ensure that tests fail before they pass?",
+      "options": [
+        {
+          "answer": "To verify that the test environment is set up correctly."
         },
         {
-          "answer": "Security vulnerabilities",
+          "answer": "To identify potential bugs in the smart contract code.",
           "correct": true
         },
         {
-          "answer": "Lengthy deployment process"
+          "answer": "To make the process of writing tests faster and more efficient."
         },
         {
-          "answer": "Inefficient gas usage"
+          "answer": "To confirm that the contract owner can withdraw funds."
         }
       ]
     }