Initial unit tests based on GoogleTest and GoogleMock#802
Conversation
|
@akuker It would be great if automatic nightly builds were working, because as part of the automation unit tests could be run, and we could eventually have code coverage metrics. There is a ticket for this if I remember correctly. It's exactly the kind of tickets where I think resolving it is more imporant than adding tickets for new features without somebody willing to start working on them. |
Definitely. We have #300 to track it. The way the Web UI is designed, it might make sense to do headless browser testing with protobuf mocks. I have experience with the pytest test runner so unless I find something more modern that's probably what I'll use. Then probably use the Selenium Webdriver library to automate the web front end. |
src/raspberrypi/Makefile
Outdated
| $(BINDIR)/$(SCSIMON): $(OBJ_SCSIMON) | $(BINDIR) | ||
| $(CXX) $(CXXFLAGS) -o $@ $(OBJ_SCSIMON) -lpthread | ||
|
|
||
| $(BINDIR)/$(RASCSI_TEST): $(OBJ_RASCSI_TEST) | $(BINDIR) |
There was a problem hiding this comment.
this needs $(SRC_PROTOBUF) added to the list of dependencies. otherwise, you need to do "make all" before you can "make test"
Agree that getting automated tests going is important. I've been putting my effort towards #335 - both a hardware and software solution. Once this is complete, I'll dive into the automated tests. Getting the tests to run automatically shouldn't be a big deal, so I'll see if I can sneak that in. |
See the related ticker for details.