Differences

This shows you the differences between two versions of the page.

--- services:labtest:start [2026/08/21 14:19] – jas
+++ services:labtest:start [2026/08/21 15:30] (current) – jas
@@ Line 188: / Line 188: @@
 There are various subcommands in Labtest Assistant - app, eecsvm, lock, ltinit, restrict, and submit, which will be described below.
+===== Labtest Applications Help =====
-===== App Dock Help =====
 <code>
@@ Line 997: / Line 996: @@
 Now if you test your labtest in ltcloud, the user will only be able to access the Firefox web browser.
-If you want additional software to be accessible in labtest, it must use a GUI.  You add to the lock file lines of the following format:
+If you want additional software to be accessible in labtest, create a file in the labtest folder called "apps" (eg. /eecs/dept/www/course/9999/labtest/default/apps).  The file contains a list of ".desktop" files available on the system for Applications that you wish to be included in the app dock at the bottom of the screen. A .desktop file is a plain text configuration file used in Linux and Unix-like operating systems to create application shortcuts, define program launchers, and integrate software into a desktop environment's application menu.
-  <app name>,<OPTIONAL app arguments>,<OPTIONAL app display name>
+These applications are ALWAYS included no matter what your settings: Firefox, Logout, and LTRestore
-For example, if you want Eclipse to be available in lock mode, you would add to the lock file:
+In labtest lock mode, no additional applications are added by default unless you add them to the app file.
-  eclipse
+**DISCLAIMER: Not all applications are suitable for labtest lock mode.  For example, VSCode requires access to the terminal for compiling and debugging code. Consult with tech when adding new applications in lock mode. **
-By default, there are no optional arguments, and if no alternate display name is mentioned, then it will appear in the menu with the same name as the command name, but with the first letter capitalized ("Eclipse").
+In regular labtest mode, these other applications are added by default:
-If you want to add Matlab:
+org.gnome.Ptyxis (this is the terminal)
+eclipse
+org.gnome.Nautilus (this is the file manager)
-  matlab,-desktop
+If you want to add an app, you need to find the desktop file for the app.  Desktop files are located in /eecs/local/share/applications/*.desktop.
-In order to run "Matlab", we have to pass "-desktop".  It would appear in the menu as "Matlab".
+If you add an app, but still want some of the defaults to appear, you have to add the defaults back as well.  For example, if you want to add IntelliJ, but you want to continue with the existing defaults, then create the "app" file containing:
-On the other hand, if you wanted to include Visual Studio Code, you would add:
+idea <- that's intellij
+org.gnome.Ptyxis (this is the terminal)
-  code,,Visual Studio Code
+eclipse
+org.gnome.Nautilus (this is the file manager)
-Now, "Visual Studio Code" will be displayed in the menu, but it will execute the command "code".
-In labtest lock mode, the window environment is a little different in order to support the locked down nature of the environment.
-When labtest mode is started, a web browser will appear with the labtest start page.  Additional software will be available by right clicking the desktop, or by clicking on the "Apps & Logout" menu in the bottom left corner of the desktop.
-Please ensure that you're careful when allowing access to software in lock mode.  Giving access to additional software may have unintended side effects.  For example, if you allow access to Eclipse, then students can compile and run code which can give access to system resources that would otherwise not be available.  Access to a terminal is still blocked.
+** Please ensure that you're careful when allowing access to software in lock mode.  Giving access to additional software may have unintended side effects.  For example, if you allow access to Eclipse, then students can compile and run code which can give access to system resources that would otherwise not be available.  Access to a terminal is still blocked. **
 ====== Accessing External Hosts In Labtest (optional) ======
@@ Line 1623: / Line 1619: @@
 Sometimes, during labtest mode, you may require a student to move from one machine to another machine.  This may be because the student is in the wrong area of the lab, or because there is some failure on the machine (eg. monitor).  Labtest home directories are stored on the local machine, and not a network drive.  Moving a student to another machine without some mechanism to copy student files from one machine to the other would mean starting with a brand new home directory, no files, and an unhappy student!
-When a student moves from one machine to the another, and logs in, the system will check if the student has files from another machine stored in the labtest save cache.  If they do, the student will see the following message: "Welcome!  It seems you have worked on this labtest on another machine.  You may ask one of the test supervisors for approval to transfer your work to this machine, or, hit Cancel to start again.".  At this point, if the student hits "Cancel", then they are logged in with a new environment without restoring their files.  If they want to restore their files from another machine, they need either **your** or your TAs approval!
+When a student moves from one machine to the another, files are not copied automatically.  Once the student logs in, they should click on the "LTRestore" icon which is located on the dock at the bottom of the screen.  The student will see the following message: "This app allows a labtest administrator to restore your work fro ma previous session. Do you need to restore work from a previous session?".  If they click "Yes", then either the faculty or the TA (who has been specified in the admin list for the labtest) must authenticate.
 To restore a students files from another machine, you will need to enter 3 pieces of information -- Labtest Admin (userid), Password, and Restore Machine.  Select the labtest admin from the dropdown list.  The labtest admins are specified by you when you request labtest mode.  The admins are also displayed in the pcmode schedule.  It's important that you check the list of admins before every labtest because neither the lab monitor nor tech staff will be able to restore a students files.   After selecting your name from the admin list, enter your system password.   Next, under "Restore Machine", a dropdown box lists all the machines where the student has been.  Select a machine from which you wish to restore the students files, and click "OK".