Week 13 Class 25 Thu Nov 21 Posted: Nov 21
Announcements
Reminder
This is a reminder that software engineering is about process, a process that leads to software that meets the actual requirements on time and within budget. Part of that overall process at a smaller level is workflow.
In every workflow, we want to validate that what we have is correct. This means that as we implement:
we want to validate each of these. Compiling and building are required to work on the code. Passing tests is automated, except for program behavior that we cannot easily test. E.g., output of error messages. Note that we do have to perform the tests. Following programming standards is not as easy to validate, so we expect the software engineer to follow these standards and reasonably attempt to verify this.
While we may have code locally with these problems, we must ensure everything is correct when we commit.
However, I often get:
I have no access to what you do locally as you implement. However, I, and your entire team, has access to what you commit.
So, in all cases, validate before you commit. And validate that the central repository at GitHub has the commits that you think you made.
Class
Exercise 65: Team Build Streaming
Build and run the current tests for the Streaming project. This must include the following:
cmake
make
make run
make test
To demonstrate this, you will record a terminal session using asciinema. Remember that
asciinema
is already installed in the GitHub Codespaces image.
A reminder on how to use asciinema
:
At the end of the terminal session, asciinema
will show a URL. Anybody can use this URL to view the session. This is what you will submit for the exercise to the link in the exercise title. The URL should not contain "connect" or be a local file. Test your URL in a browser; an incorrect URL will receive a 0 on the exercise.
Unless stated otherwise, all exercises are due by 3 pm on Fri Nov 22