Previous Lecture

lect09

Next Lecture

lect09, Mon 02/12

Overview: Software Testing

Announcements

• H08 due next Wednesday (next Monday is Presidents’ Day holiday)
• Lab05 updates as follows:

Lab05 Updates:

• (35 pts) Review, assess, and summarize the feedback you received on your MVP evaluation and formulate an action plan going forward.
  • Feedback has been posted in your project Slack channel. Please review and organize (group). Then discuss action items and user stories in response and prioritize them.
  • Please create a team/MVP_FOLLOWUP.md file, where you document this process (e.g., with subheadings such as):
    • Feedback Grouped and Sorted
    • Response Actions
    • Next Steps
• (35 pts) You earn these team points for identifying at least one testing library to experiment with for your coding needs, and for implementing and documenting at least one unit test in your code base by Friday, EOD.
  • Please create a team/TESTING.md file, where you document the testing library/ies and approach/es you experiemnted with and the unit test(s) that you implemented in your codebase.
• (30 pts) You earn these individual points by doing and documenting at least one “Coding with AI” experiment by Friday, EOD.
  • This can take multiple forms: Using AI to prototype UI possibilities (e.g. using ChatGPT, Google Gemini, or Vercel v0.dev for React-based web pages), help with writing testing code (e.g. using Github Copilot or Codeium, generating documentation (e.g. using Github Copilot, Codeium, or similar plugins), designing UI art/elements using Dall-e, Gemini, or Adobe Firefly, researching scalability suggestions for your app, etc.
  • Please create a team/AI_CODING.md file, where each of the team members documents their individual AI coding experiments. List the AI tool you utilized, the outcomes you produced, and, importantly, reflections on
    • how useful this tool was / potentially could be for your coding effort going forward
    • what steps you needed to (or couldn’t) take to ensure that the AI output was correct, understandable, and fair use
• A new Slack channel help_ai was created to provide pointers to useful AI coding tools. In addition to documenting your efforts in your own team-internal team/AI_CODING.md file, please share pointers to the tools you were most excited about in there.

SW Testing Slides

• Overview of SW Testing
• Slides for high-level overview and motivation: Testing for the Skeptical Developer

SW Testing Pointers

• Overview of Javascript Testing, and just in case you are over your free Medium articles quota: PDF version
• A Beginner’s Guide to Unit-testing with Jest
• Python Testing Frameworks

• Comparing React testing libraries

• Possible Testing Libraries:
  • Jest
  • Jasmine
  • Component Testing with Cypress
  • Component Testing with Storybook
  • Mocha (and Chai and Sinon)
  • BDD Acceptance Testing with cucumber.js, blog example
• A new Slack channel help_swtesting was created to provide pointers to useful software testing tools and libraries. In addition to documenting your efforts in your own team-internal team/TESTING.md file, please share pointers to the tools you were most excited about in there.

Work in Breakout Groups

• Standup
• Organize and review MVP feedback, prepare action plan going forward
• Discuss AI experiment strategy
• Discuss SW Testing strategy