-
Notifications
You must be signed in to change notification settings - Fork 6
Testing Plan
In all the test cases described below the things that should be checked are almost the same. They are listed here:
- On the ltsp-server window make sure that you can access the internet. Create also a test user.
- On the ltsp-client window login with the test user and make sure that it works.
- On the ltsp-client window, after you login with the test user, make sure that you can connect to internet.
- On ltsp-server make sure that the packages defined on the list of PACKAGES on
settings.sh
are installed. - On the ltsp-server window open
epoptes
and make sure that you can access the desktop of the test-client.
Internal testing is done with the help of a virtual network interface, called 'ltsp-test-if', which is created before testing starts and is destroyed after testing ends.
Before testing starts edit settings.sh
and make sure that LAN_IF is set to ltsp-test-if
.
- Edit
settings.sh
and make sure that STANDALONE is set to "yes"`. - Start testing with
./test.sh start
. (This should make sure to destroy dhcp-server, ltsp-server and ltsp-client, and then to start ltsp-server and after that start ltsp-client). A window for the ltsp-server and a window for the ltsp-client should be created. - Perform all the checks described on the first section.
- Stop testing with
./test.sh stop
. (This should halt and destroy ltsp-client and ltsp-server, as well as remove the virtual network interface 'ltsp-test-if' that was used for testing).
- Edit
settings.sh
and make sure that STANDALONE is set to "no"`. - Start testing with
./test.sh start
. (This should make sure to destroy dhcp-server, ltsp-server and ltsp-client, and then to start dhcp-server, ltsp-server, and ltsp-client). A window for the dhcp-server, and ltsp-server, and ltsp-client should be created. - On the ltsp-server window make sure that you can access the internet (using dhcp-server as a gateway). Create also a test user.
- Perform all the checks described on the first section.
- Stop testing with
./test.sh stop
. (This should halt and destroy dhcp-server, ltsp-client and ltsp-server, as well as remove the virtual network interface 'ltsp-test-if' that was used for testing).
External testing is done using a real ethernet (LAN) interface for bridging. For this to work, this interface should be connected with a cable to switch/hub, and the interface must be up (enabled/activated).
Before testing starts edit settings.sh
and make sure that LAN_IF is set to name of the interface that will be used for testing.
Testing is done with the help of test.sh
, following the same steps as for internal testing above
Testing is done with the help of test.sh
, following the same steps as for internal testing above
In this case the client and the dhcp server will be real ones, on a real LAN.
Edit settings.sh
and make sure that LAN_IF is set to the network interface that is connected to the LAN.
This case can be tested only if there is no dhcp/gateway server on the LAN and the server can connect to internet through another interface (for example WiFi interface).
- Open
settings.sh
- Change the
STANDALONE
variable toyes
- Change the
LAN_IP
variable to whichever IP address you want for ltsp server and save it. - Do a
vagrant up
from the terminal - You will have ltsp-server setup in standalone mode
- Do a
./client.sh
to start the virtual client or you can create one manually. - Perform all the checks described on the first section.
Note: Before starting a virtual ltsp-client on the LAN, we should edit the corresponding settings.sh
and make sure that LAN_IF has the name of the interface that is actually connected to the LAN.
This case can be tested only if there is already a dhcp/gateway server on the LAN.
- Edit
settings.sh
and make sure that STANDALONE is set to "no". Also make sure that LAN_IP is in the range of the LAN to which we are connected. - Set the interface you want to use by changing
LAN_IF
and save it. - Destroy the ltsp-server and then start it again:
vagrant destroy ; vagrant up
- Start a ltsp client on the LAN, either directly or using the
client.sh
- Perform all the checks described on the first section.
Note: The same thing as in the standalone case applies for starting a virtual ltsp-client on the LAN