CSU Monterey Bay Learning Journal

This week's reading from Software Engineering at Google covered large tests. The main takeaway is that larger tests trade speed and simplicity for fidelity. Unlike unit tests, they test how the system actually behaves in conditions closer to production, which means they catch things unit tests simply cannot. The tradeoff is that they are slower, more expensive to run, and harder to maintain. What stuck with me was that larger tests still use mocks in some cases, and that Google does not rely on full automation scripts for everything. Two key ingredients for large tests to work well are realistic seed data and production data, which makes sense because a test is only as useful as how closely it mirrors real usage.

What project milestones did you accomplish this week? This week I finished 2 certificates and put in over 40 combined hours into the Google Cybersecurity course prior to that. I am on track to finish the Google Cybersecurity certificate by end of this week. What is your plan for next week? Next week I plan to continue studying for the AWS quiz and keep that momentum going. What challenges, if any, are you currently facing in project development? Do you need instructor assistance? No challenges at the moment and no instructor assistance needed.