Skip to content
This repository has been archived by the owner on Aug 15, 2018. It is now read-only.

Testing Plan

Deepanshu Gajbhiye edited this page Aug 4, 2018 · 3 revisions

Testing Plan

0 Things to be checked on each test case

In all the test cases described below the things that should be checked are almost the same. They are listed here:

  1. On the ltsp-server window make sure that you can access the internet. Create also a test user.
  2. On the ltsp-client window login with the test user and make sure that it works.
  3. On the ltsp-client window, after you login with the test user, make sure that you can connect to internet.
  4. On ltsp-server make sure that the packages defined on the list of PACKAGES on settings.sh are installed.
  5. On the ltsp-server window open epoptes and make sure that you can access the desktop of the test-client.

1 Testing internally

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.

1.1 Standalone mode

  1. Edit settings.sh and make sure that STANDALONE is set to "yes"`.
  2. 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.
  3. Perform all the checks described on the first section.
  4. 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).

1.2 Normal mode

  1. Edit settings.sh and make sure that STANDALONE is set to "no"`.
  2. 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.
  3. On the ltsp-server window make sure that you can access the internet (using dhcp-server as a gateway). Create also a test user.
  4. Perform all the checks described on the first section.
  5. 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).

2 Testing externally

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.

2.1 Standalone mode

Testing is done with the help of test.sh, following the same steps as for internal testing above

2.2 Normal mode

Testing is done with the help of test.sh, following the same steps as for internal testing above

3. Real testing on LAN

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.

3.1 Standalone mode

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).

  1. Open settings.sh
  2. Change the STANDALONE variable to yes
  3. Change the LAN_IP variable to whichever IP address you want for ltsp server and save it.
  4. Do a vagrant up from the terminal
  5. You will have ltsp-server setup in standalone mode
  6. Do a ./client.sh to start the virtual client or you can create one manually.
  7. 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.

3.2 Normal mode

This case can be tested only if there is already a dhcp/gateway server on the LAN.

  1. 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.
  2. Set the interface you want to use by changing LAN_IF and save it.
  3. Destroy the ltsp-server and then start it again: vagrant destroy ; vagrant up
  4. Start a ltsp client on the LAN, either directly or using the client.sh
  5. 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