Merge pull request #208 from Developer-DAO/quiz-lesson-4

Lesson 4. Enhance intro; add mini-quizzes; final quiz

Author: elPiablo

pages/lessons/projects/4.mdx

@@ -0,0 +1,19 @@
+{
+  "question": "Choose the reasons for using automated tests:",
+  "options": [
+    {
+      "answer": "Warns of regressions if we upgrade code later",
+      "correct": true
+    },
+    {
+      "answer": "So we don’t have to use manual tests"
+    },
+    {
+      "answer": "Build confidence in each component of our code",
+      "correct": true
+    },
+    {
+      "answer": "All of the above"
+    }
+  ]
+}

utils/questions/lesson-4/1-intro/Q1.json

@@ -0,0 +1,18 @@
+{
+  "question": "What is the role of a testnet in smart contract development?",
+  "options": [
+    {
+      "answer": "It helps to deploy smart contracts to the Ethereum mainnet."
+    },
+    {
+      "answer": "To airdrop free Ether to devs, because testing gives the ecosystem a good name."
+    },
+    {
+      "answer": "It's used to interact with smart contracts using real Ether."
+    },
+    {
+      "answer": "It's a network that is used for testing smart contracts.",
+      "correct": true
+    }
+  ]
+}

utils/questions/lesson-4/1-intro/Q2.json

@@ -0,0 +1,18 @@
+{
+  "question": "What is the purpose of the 'require' statement in Solidity?",
+  "options": [
+    {
+      "answer": "For specifying the visibility of a variable or function."
+    },
+    {
+      "answer": "To be able to easily define a new modifier in the contract whenever we need it."
+    },
+    {
+      "answer": "For declaring a new function in the contract."
+    },
+    {
+      "answer": "To perform a conditional check, and revert the transaction if it fails.",
+      "correct": true
+    }
+  ]
+}

utils/questions/lesson-4/1-intro/Q3.json

@@ -0,0 +1,18 @@
+{
+  "question": "When writing unit tests for a smart contract, what should we be testing?",
+  "options": [
+    {
+      "answer": "Functionality that only involves external contracts"
+    },
+    {
+      "answer": "Only private functions that aren't externally accessible"
+    },
+    {
+      "answer": "All functions and possible edge cases that the contract may encounter",
+      "correct": true
+    },
+    {
+      "answer": "Just the constructor function to ensure the contract gets deployed properly"
+    }
+  ]
+}

utils/questions/lesson-4/1-intro/Q4.json

@@ -0,0 +1,18 @@
+{
+  "question": "What do you imagine one of the first steps is in this lesson?",
+  "options": [
+    {
+      "answer": "To add your private key to the .gitignore file"
+    },
+    {
+      "answer": "To harmonise Solidity versions across the project",
+      "correct": true
+    },
+    {
+      "answer": "To make sure to add an extra line of code to the contract to signal to Hardhat that we can test it"
+    },
+    {
+      "answer": "To create a console.log line to the contract code so we can see the output of the tests"
+    }
+  ]
+}

utils/questions/lesson-4/1-intro/Q5.json

@@ -0,0 +1,21 @@
+{
+  "question": "Which of the following can we achieve with automated testing?",
+  "options": [
+    {
+      "answer": "Prove code actually works"
+    },
+    {
+      "answer": "Help write more modular code"
+    },
+    {
+      "answer": "Ensure a fixed bug stays fixed"
+    },
+    {
+      "answer": "All of the above",
+      "correct": true
+    },
+    {
+      "answer": "Only a) and c)"
+    }
+  ]
+}

utils/questions/lesson-4/2-get-set-up/Q1.json

@@ -0,0 +1,18 @@
+{
+  "question": "How does the tokenURI function generate the token metadata?",
+  "options": [
+    {
+      "answer": "By reading from an external file"
+    },
+    {
+      "answer": "By using a predefined JSON template"
+    },
+    {
+      "answer": "By dynamically generating SVG image and JSON data",
+      "correct": true
+    },
+    {
+      "answer": "By querying an off-chain API"
+    }
+  ]
+}

utils/questions/lesson-4/2-get-set-up/Q2.json

@@ -0,0 +1,18 @@
+{
+  "question": "What should be added to the scripts section of package.json to run tests using Hardhat?",
+  "options": [
+    {
+      "answer": "\"scripts\": { \"test\": \"hardhat test\" }"
+    },
+    {
+      "answer": "\"scripts\": { \"runTests\": \"hardhat test\" }"
+    },
+    {
+      "answer": " \"scripts\": { \"test\": \"hardhat test --network hardhat\" }",
+      "correct": true
+    },
+    {
+      "answer": "\"scripts\": { \"runTests\": \"hardhat test --network hardhat\" }"
+    }
+  ]
+}

utils/questions/lesson-4/2-get-set-up/Q3.json

@@ -0,0 +1,18 @@
+{
+  "question": "Why should we verify the Solidity version in the hardhat.config.js file?",
+  "options": [
+    {
+      "answer": "So it can check for any updates to the Solidity version"
+    },
+    {
+      "answer": "To ensure compatibility with the contract being tested.",
+      "correct": true
+    },
+    {
+      "answer": "a) and b)"
+    },
+    {
+      "answer": "neither a) nor b)"
+    }
+  ]
+}