Add quiz + mini-quiz placeholders + file structure

elPiablo · elPiablo · commit 8e9e5b92d94c · 2023-07-05T02:01:38.000+02:00
diff --git a/pages/lessons/projects/4.mdx b/pages/lessons/projects/4.mdx
@@ -22,6 +22,17 @@ 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">
+      <Question question="lesson-4/1-intro/Q1" />
+      <Question question="lesson-4/1-intro/Q2" />
+      <Question question="lesson-4/1-intro/Q3" />
+      <Question question="lesson-4/1-intro/Q4" />
+      <Question question="lesson-4/1-intro/Q5" />
+</SideDrawer> 
+
+PART 1
+
+
 ## Why automated testing?
 
 Testing can:
@@ -199,6 +210,14 @@ module.exports = {
   solidity: '0.8.12',
 }
 ```
+<SideDrawer buttonText="Checkpoint Questions" title="Setting up our Environment">
+      <Question question="lesson-4/2-get-set-up/Q1" />
+      <Question question="lesson-4/2-get-set-up/Q2" />
+      <Question question="lesson-4/2-get-set-up/Q3" />
+      <Question question="lesson-4/2-get-set-up/Q4" />
+      <Question question="lesson-4/2-get-set-up/Q5" />
+</SideDrawer> 
+PART 2
 
 ## What do we want to test on our TierNFT contract?
 
@@ -397,6 +416,16 @@ failure looks like:
       +Anita
 ```
 
+<SideDrawer buttonText="Checkpoint Questions" title="General Testing Concepts">
+      <Question question="lesson-4/3-general-concepts/Q1" />
+      <Question question="lesson-4/3-general-concepts/Q2" />
+      <Question question="lesson-4/3-general-concepts/Q3" />
+      <Question question="lesson-4/3-general-concepts/Q4" />
+      <Question question="lesson-4/3-general-concepts/Q5" />
+</SideDrawer> 
+
+PART 3
+
 ### Let's add tests for mint()
 
 Now is time to add tests for our `mint()` method. We'll group these new tests
@@ -572,6 +601,16 @@ of additional highlights:
   breaks our rule of one expect per test, but as long as the test is kept
   simple, we can choose what makes sense for what we're trying to test.
 
+<SideDrawer buttonText="Checkpoint Questions" title="Mint and Withdraw">
+      <Question question="lesson-4/4-mint-withdraw/Q1" />
+      <Question question="lesson-4/4-mint-withdraw/Q2" />
+      <Question question="lesson-4/4-mint-withdraw/Q3" />
+      <Question question="lesson-4/4-mint-withdraw/Q4" />
+      <Question question="lesson-4/4-mint-withdraw/Q5" />
+</SideDrawer> 
+
+PART 4
+
 ### Testing tokenURI()
 
 Here's where things get even more interesting!
@@ -856,6 +895,16 @@ while refactoring to make sure we didn't break things along the way, and it's
 helpful at the end to ensure the `tokenURI()` method continues to work without
 fail when code changes.
 
+<SideDrawer buttonText="Checkpoint Questions" title="Testing the SVG">
+      <Question question="lesson-4/5-SVG-test/Q1" />
+      <Question question="lesson-4/5-SVG-test/Q2" />
+      <Question question="lesson-4/5-SVG-test/Q3" />
+      <Question question="lesson-4/5-SVG-test/Q4" />
+      <Question question="lesson-4/5-SVG-test/Q5" />
+</SideDrawer> 
+
+OUTRO
+
 ## Food for Thought
 
 With all the helpfulness of tests, why didn't we start with them before we wrote
@@ -889,6 +938,10 @@ 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/>
+<Quiz quiz="lesson-4-quiz" />
+<br/>
+
 Go forth, test, and prosper knowing you have confidence in the code you're
 deploying into the world.
 
diff --git a/utils/questions/lesson-4/1-intro/Q1.json b/utils/questions/lesson-4/1-intro/Q1.json
@@ -0,0 +1,23 @@
+{
+  "question": "Choose what NFTs can do? Multiple answers possible.",
+  "options": [
+    {
+      "answer": "Give access to a DAO",
+      "correct": true
+    },
+    {
+      "answer": "Do the dishes"
+    },
+    {
+      "answer": "Represent a concert ticket",
+      "correct": true
+    },
+    {
+      "answer": "Point to storage of an album",
+      "correct": true
+    },
+    {
+      "answer": "Replicate one NFT with another"
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/1-intro/Q2.json b/utils/questions/lesson-4/1-intro/Q2.json
@@ -0,0 +1,18 @@
+{
+  "question": "What is Hardhat? ",
+  "options": [
+    {
+      "answer": "A set of tools that includes a local mini blockchain that can run on your machine",
+      "correct": true
+    },
+    {
+      "answer": "A code editor in the browser "
+    },
+    {
+      "answer": "A security patch for most Linux operating systems"
+    },
+    {
+      "answer": "Safety apparel for space travel "
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/1-intro/Q3.json b/utils/questions/lesson-4/1-intro/Q3.json
@@ -0,0 +1,18 @@
+{
+  "question": "In Solidity, what does the ^ symbol represent when specifying the compiler version?",
+  "options": [
+    {
+      "answer": "It denotes an exclusive compiler version"
+    },
+    {
+      "answer": "It indicates a fallback function"
+    },
+    {
+      "answer": "It signifies a dangerous computation"
+    },
+    {
+      "answer": " It specifies a compatible range of compiler versions",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/1-intro/Q4.json b/utils/questions/lesson-4/1-intro/Q4.json
@@ -0,0 +1,18 @@
+{
+  "question": "Which address does the msg.sender variable represent in Solidity?",
+  "options": [
+    {
+      "answer": "The contract owner"
+    },
+    {
+      "answer": "The Ethereum smart contract"
+    },
+    {
+      "answer": "The Ethereum network"
+    },
+    {
+      "answer": "The caller of the current function",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/1-intro/Q5.json b/utils/questions/lesson-4/1-intro/Q5.json
@@ -0,0 +1,15 @@
+{
+  "question": "What is npm? ",
+  "options": [
+    {
+      "answer": "A Node.js module that provides a blockchain for running smart contracts"
+    },
+    {
+      "answer": "A package manager from Node.js ",
+      "correct": true
+    },
+    {
+      "answer": "A framework for building web applications "
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/2-get-set-up/Q1.json b/utils/questions/lesson-4/2-get-set-up/Q1.json
@@ -0,0 +1,18 @@
+{
+  "question": "Which of the following can we achieve with automated testing?",
+  "options": [
+    {
+      "answer": "bla bla bla."
+    },
+    {
+      "answer": "Create a project."
+    },
+    {
+      "answer": "Create a smart contract using a code editor."
+    },
+    {
+      "answer": "All of the above",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/2-get-set-up/Q2.json b/utils/questions/lesson-4/2-get-set-up/Q2.json
@@ -0,0 +1,15 @@
+{
+  "question": "When setting up dependencies, what is relevant to our testing environment? ",
+  "options": [
+    {
+      "answer": "bla bla bla."
+    },
+    {
+      "answer": "It tells npm to save the dependencies in a development environment.",
+      "correct": true
+    },
+    {
+      "answer": "It tells npm to save the dependencies in a production environment"
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/2-get-set-up/Q3.json b/utils/questions/lesson-4/2-get-set-up/Q3.json
@@ -0,0 +1,18 @@
+{
+  "question": "What is the benefit of using Open Zeppelin contracts in smart contract development?",
+  "options": [
+    {
+      "answer": "They reduce the amount of code we write"
+    },
+    {
+      "answer": "They provide rigorously audited and safe contracts"
+    },
+    {
+      "answer": "They allow for easier human collaboration and technical interoperability"
+    },
+    {
+      "answer": "All of the above",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/2-get-set-up/Q4.json b/utils/questions/lesson-4/2-get-set-up/Q4.json
@@ -0,0 +1,15 @@
+{
+  "question": "We will cover this later, but what do you think the purpose of the .gitignore file created by Hardhat is?",
+  "options": [
+    {
+      "answer": "To hide your project's dependencies."
+    },
+    {
+      "answer": "To store your project's source code in a private Github repository."
+    },
+    {
+      "answer": "To ensure that certain files not tracked by Git remain untracked",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/2-get-set-up/Q5.json b/utils/questions/lesson-4/2-get-set-up/Q5.json
@@ -0,0 +1,18 @@
+{
+  "question": "What do you think the 'code .' command in your console is going to do? ",
+  "options": [
+    {
+      "answer": "Create an empty file named ProjectNFT.sol. "
+    },
+    {
+      "answer": "Open your code editor",
+      "correct": true
+    },
+    {
+      "answer": "Copy the code of your new contract"
+    },
+    {
+      "answer": "Compile your new contract"
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/3-general-concepts/Q1.json b/utils/questions/lesson-4/3-general-concepts/Q1.json
@@ -0,0 +1,18 @@
+{
+  "question": "Why do we want our ProjectNFT contract to import ERC721.sol from OpenZeppelin? ",
+  "options": [
+    {
+      "answer": "To declare a smart contract in Solidity"
+    },
+    {
+      "answer": "Because Led Zeppelin's discography has automatic customs clearance"
+    },
+    {
+      "answer": "To keep track of the total supply of NFTs "
+    },
+    {
+      "answer": "To inherit the properties of ERC721 into the ProjectNFT contract ",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/3-general-concepts/Q2.json b/utils/questions/lesson-4/3-general-concepts/Q2.json
@@ -0,0 +1,18 @@
+{
+  "question": "What does the totalSupply variable do?",
+  "options": [
+    {
+      "answer": "Tells us we can't mint any more NFTs"
+    },
+    {
+      "answer": "Stores the current number of minted NFTs",
+      "correct": true
+    },
+    {
+      "answer": "Identifies each new NFT created"
+    },
+    {
+      "answer": "It keeps track of the number of functions in the contract"
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/3-general-concepts/Q3.json b/utils/questions/lesson-4/3-general-concepts/Q3.json
@@ -0,0 +1,15 @@
+{
+  "question": "What does the constructor function do in the contract? ",
+  "options": [
+    {
+      "answer": "Defines the copyright license "
+    },
+    {
+      "answer": "Declares the version of Solidity being used"
+    },
+    {
+      "answer": "Assigns a name and symbol to the NFT being created",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/3-general-concepts/Q4.json b/utils/questions/lesson-4/3-general-concepts/Q4.json
@@ -0,0 +1,15 @@
+{
+  "question": "Open Zeppelin contracts have evolved over time by.....",
+  "options": [
+    {
+      "answer": "becoming more basic and focused on specific functionalities"
+    },
+    {
+      "answer": "becoming less modular"
+    },
+    {
+      "answer": "opening up more possibilities and become richer in functionality",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/3-general-concepts/Q5.json b/utils/questions/lesson-4/3-general-concepts/Q5.json
@@ -0,0 +1,12 @@
+{
+  "question": "ETH is an ERC token",
+  "options": [
+    {
+      "answer": "True"
+    },
+    {
+      "answer": "False",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/4-mint-withdraw/Q1.json b/utils/questions/lesson-4/4-mint-withdraw/Q1.json
@@ -0,0 +1,15 @@
+{
+  "question": "What is a tokenURI?",
+  "options": [
+    {
+      "answer": "A function that creates a unique NFT token ID"
+    },
+    {
+      "answer": "A web address that points to an NFT's content and information",
+      "correct": true
+    },
+    {
+      "answer": "A web address that points to the NFT's blockchain."
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/4-mint-withdraw/Q2.json b/utils/questions/lesson-4/4-mint-withdraw/Q2.json
@@ -0,0 +1,18 @@
+{
+  "question": "What does the override modifier do?",
+  "options": [
+    {
+      "answer": "It indicates that this function creates a different experience"
+    },
+    {
+      "answer": "It adds a state variable to the contract"
+    },
+    {
+      "answer": "It lets a variable convert to a more human readable name"
+    },
+    {
+      "answer": "It lets a function replace one inside the inherited contract",
+      "correct": true
+    }
+  ]
+}
diff --git a/utils/questions/lesson-4/4-mint-withdraw/Q3.json b/utils/questions/lesson-4/4-mint-withdraw/Q3.json
diff --git a/utils/questions/lesson-4/4-mint-withdraw/Q4.json b/utils/questions/lesson-4/4-mint-withdraw/Q4.json
diff --git a/utils/questions/lesson-4/4-mint-withdraw/Q5.json b/utils/questions/lesson-4/4-mint-withdraw/Q5.json
diff --git a/utils/questions/lesson-4/5-SVG-test/Q1.json b/utils/questions/lesson-4/5-SVG-test/Q1.json
diff --git a/utils/questions/lesson-4/5-SVG-test/Q2.json b/utils/questions/lesson-4/5-SVG-test/Q2.json
diff --git a/utils/questions/lesson-4/5-SVG-test/Q3.json b/utils/questions/lesson-4/5-SVG-test/Q3.json
diff --git a/utils/questions/lesson-4/5-SVG-test/Q4.json b/utils/questions/lesson-4/5-SVG-test/Q4.json
diff --git a/utils/questions/lesson-4/5-SVG-test/Q5.json b/utils/questions/lesson-4/5-SVG-test/Q5.json
diff --git a/utils/quizzes/lesson-4-quiz.json b/utils/quizzes/lesson-4-quiz.json
