. t Fizz rule in DB test

Co-Authored-By: Nitsan Avni <nitsanav@gmail.com>
Co-Authored-By: Joel Silberman <42779942+jcs-instructor@users.noreply.github.com>
Co-Authored-By: 4dsherwood <4dsherwood@users.noreply.github.com>
Co-Authored-By: Kevin Maes <kevin@kevinmaes.com>
Co-Authored-By: Matt <matthew.anderson11@gmail.com>

Author: 5 people

katas/fizzbuzz/test_fizzbuzz.py

@@ -13,3 +13,15 @@ def test_example_using_mock_db(mock_mongo_client):
     result = collection.find_one({"name": "John"})
 
     assert result["age"] == 30
+
+def test_have_fizz_buzz_specs_in_DB(mock_mongo_client):
+    db = mock_mongo_client.mydatabase
+    collection = db.ourcollection
+
+    # input: 9
+    # output: fizz
+    # denominator: 3
+    collection.insert_one({"word": "Fizz", "denominator": 3})
+    result = collection.find_one({"word": "Fizz"})
+
+    assert result["denominator"] == 3

session-notes/session-notes-2024-04-18.md

@@ -78,6 +78,27 @@ Joel
 
 ### Mid-Session Retro 2 (1 minute per person - what liked/disliked & propose changes)
 
+Joel
+- Enjoyed it! Interesting conversation, and getting on same page, uncharted territory
+- Liked: taking a dummy test -> changing the fields -> just worked
+- Still interested to see how this goes
+
+Diana
+- Working well
+- Appreciate talking through the different representations, talking about it made it clearer to see the differences
+- As Typist did not see it clearly
+- Tests helped reveal that
+- Excited about using a DB
+- propose to commit soon
+
+Nitsan
+- Very interesting - PO discussion; where is the responsibility of who?
+- Representing something in DB but usually isn't something a PO cares about
+- Up to tech and non-tech people to have an understanding of the domain
+- Nice to have DB represent domain to avoid confusion; so not solely a tech concern
+- Not sure what answer is; instinct: PO shouldn't tell tech what the internals should be, but good to be part of discussion
+
+
 ### Final Retro
 
 ### How we spent our time today: