SvenRoederer
commented
5 years ago https://github.com/freifunk-berlin/firmware/issues/667 also likes to have better testing-procedures
Open booo opened 9 years ago
SvenRoederer
commented
5 years ago https://github.com/freifunk-berlin/firmware/issues/667 also likes to have better testing-procedures
pmelange
commented
5 years ago Running the wizard, and making sure that the values in /etc/config are set properly, would also be an important test. This includes pulling in the defaults from /etc/config/freifunk and overriding them in the selected community profile (see #617).
xa-y-ax
commented
4 years ago SvenRoederer
commented
4 years ago I'd like also to mention https://github.com/freifunk-gluon/gluon-qemu-testlab (python scripts to run qemu and gluon based virtual mesh networks) - This might be a framework, that we can adapt to our needs or get some inspirations. An automated setup to test the network configuration (Firewall, policyrouting, basic IP-configuration) is an repetitive task which should be automated.
@kruszksa also mentioned the he once used something docker based for automated testing.
It's the second time I would like to push a release and we don't have agreed on some testing procedures. We should definitly change this! Some sketches for a testing szenario follow:
Internet <--> VPN03 <--OPENVPN--> gateway0 <--mesh (OLSR) --> node0
Configuration for the gateway:
Configuration for the node:
Tests:
I suggest we implement some automation with phantomjs or something the like and create some shell script that assist in testing stuff on the terminal level.