anirudhp status report 26th April

This week my main goal was to exhaustively test for correctness and functionality(which we discussed with Prof. Gloria to be the main objective of our testing). In order to do this, I took two paths:

  1. Assuming that the system itself works given that there are no underlying assumptions. So the only location of bugs could be in multi-client.
  2. User testing with other ECE majors, both inside and outside capstone. Specific testing to find the potential edge cases that we could have missed.

The objective of testing (1) was to specifically move the flag reading and writing behaviour on the second client to specific blocks of time and see if correctness was maintianed.

I simply created a list of all flags that were being set and then tested every intermediary time step by ramping up the refresh speed and using if statements to target those specific time windows.

While this did not yield any errors, it did verify that there are absolutely no scenarios that the system would yield a wrong or incorrect output for.

Over next week, we will be wrapping up the final documentation for the project and releasing the client side code as a unified image. We are well ahead of schedule.

Leave a Reply

Your email address will not be published. Required fields are marked *