nsfarm issueshttps://gitlab.nic.cz/turris/nsfarm/-/issues2021-11-08T15:18:31+01:00https://gitlab.nic.cz/turris/nsfarm/-/issues/36Static leases2021-11-08T15:18:31+01:00Karel KociStatic leasesTest and verify the functionality of static leases. This is an extension to DHCP tests.Test and verify the functionality of static leases. This is an extension to DHCP tests.https://gitlab.nic.cz/turris/nsfarm/-/issues/35Basic firewall testing2022-03-15T14:38:49+01:00Karel KociBasic firewall testingWe should test firewall.
* [ ] Zone separation and forwarding
* [ ] Port forwarding
* [ ] Block and accept network rule
* [ ] MasquaradeWe should test firewall.
* [ ] Zone separation and forwarding
* [ ] Port forwarding
* [ ] Block and accept network rule
* [ ] Masquaradehttps://gitlab.nic.cz/turris/nsfarm/-/issues/32Click through reForis2021-09-07T14:26:39+02:00Karel KociClick through reForisWe should go through all the reForis pages and make sure that they work. This can be a sequence of openning the index, navigating to the tested page and checking some content.We should go through all the reForis pages and make sure that they work. This can be a sequence of openning the index, navigating to the tested page and checking some content.https://gitlab.nic.cz/turris/nsfarm/-/issues/10PPPOE uplink tests2021-10-13T09:52:53+02:00Karel KociPPPOE uplink tests* [x] allow pass-trough of `/dev/ppp` device to container
* [x] prepare ISP container with PPPOE server
* [ ] write fixture to configure appropriate PPPOE WAN settings for common Internet tests* [x] allow pass-trough of `/dev/ppp` device to container
* [x] prepare ISP container with PPPOE server
* [ ] write fixture to configure appropriate PPPOE WAN settings for common Internet testshttps://gitlab.nic.cz/turris/nsfarm/-/issues/8Instances locking and possible queuing2022-06-06T14:26:26+02:00Karel KociInstances locking and possible queuingThere is a need to lock different instances of nsfarm on same host to not influence them self. This is because they are for example exclusively using shared medium or loads non-exclusive shared medium.
The same code can also be used to ...There is a need to lock different instances of nsfarm on same host to not influence them self. This is because they are for example exclusively using shared medium or loads non-exclusive shared medium.
The same code can also be used to wait for target to be released by some other instance instead of failing. That should be handy when we have multiple users on same server developing nsfarm as well as build system running tests on new builds.
* [x] Implement general instance locking for resource
* [x] ~~Investigate non-blocking locking (like if you can't lock this return to this fixture later and try to lock it again instead of blocking)~~ (probably is not possible)
With implementation done we should integrate it to
* [x] Network performance tests (to have only one instance loading shared Ethernet connection)
* [x] ~~Access to Wi-Fi cards~~ (no wifi yet)
* [x] Test framework initialization with target blocked by some other instance.