Installers
Note
Tester |
Test Date |
Scopy version |
Plugin version (N/A if not applicable) |
Comments |
---|---|---|---|---|
Test 1: Check Scopy AppImage x86_64
UID: TST.START.APPIMAGE.X86_64
Description: This test verifies if the Scopy AppImage starts correctly on an Linux Operating System with x86_64 architecture.
- Preconditions:
OS: Linux intel x86_64
libfuse2 is required in order to execute an AppImage, install it using sudo apt-get install
- Steps:
Download Scopy Linux AppImage x86_64 from the release page.
- Unzip the archive.
Expected result: a file named Scopy-x86_64.AppImage should be extracted.
Actual result:
Grant execution permission to the file using the terminal.
chmod +x Scopy-x86_64.AppImageTo start the application execute the .AppImage file.
./Scopy-x86_64.AppImageOr double-click from the GUI.
Expected result: A window containing the GUI of the application should open and if opened from the terminal, the logs generated by the application should be displayed inside the terminal. Inside the application, a window containing the license agreement should appear with 2 buttons “Exit” and “Continue”.
Actual result:
- Press “Exit”.
Expected result: Scopy should gracefully close.
Actual result:
Start again the application, just like in step 4.
- Press “Continue”.
Expected result: The window containing the license agreement should close and Scopy should be still running.
Actual result:
Tested OS:
Comments:
Result: PASS/FAIL
Test 2: Check Scopy AppImage arm32
UID: TST.START.APPIMAGE.X86_64
Description: This test verifies if the Scopy AppImage starts correctly on an Linux Operating System with arm32 architecture.
- Preconditions:
OS: Linux intel arm32
libfuse2 is required in order to execute an AppImage, install it using sudo apt-get install
- Steps:
Download Scopy Linux AppImage arm32 from the release page.
- Unzip the archive.
Expected result: a file named Scopy-armhf.AppImage should be extracted.
Actual result:
Grant execution permission to the file using the terminal.
chmod +x Scopy-armhf.AppImageTo start the application execute the .AppImage file.
./Scopy-armhf.AppImageOr double-click from the GUI.
Expected result: A window containing the GUI of the application should open and if opened from the terminal, the logs generated by the application should be displayed inside the terminal. Inside the application, a window containing the license agreement should appear with 2 buttons “Exit” and “Continue”.
Actual result:
- Press “Exit”.
Expected result: Scopy should gracefully close.
Actual result:
Start again the application, just like in step 4.
- Press “Continue”.
Expected result: The window containing the license agreement should close and Scopy should be still running.
Actual result:
Tested OS:
Comments:
Result: PASS/FAIL
Test 3: Check if Scopy AppImage arm64 opens correctly
UID: TST.START.APPIMAGE.X86_64
Description: This test verifies if the Scopy AppImage starts correctly on an Linux Operating System with arm64 architecture.
- Preconditions:
OS: Linux intel arm64
libfuse2 is required in order to execute an AppImage, install it using sudo apt-get install
- Steps:
Download Scopy Linux AppImage arm64 from the release page.
- Unzip the archive.
Expected result: a file named Scopy-arm64.AppImage should be extracted.
Actual result:
Grant execution permission to the file using the terminal.
chmod +x Scopy-arm64.AppImageTo start the application execute the .AppImage file.
./Scopy-arm64.AppImageOr double-click from the GUI.
Expected result: A window containing the GUI of the application should open and if opened from the terminal, the logs generated by the application should be displayed inside the terminal. Inside the application, a window containing the license agreement should appear with 2 buttons “Exit” and “Continue”.
Actual result:
- Press “Exit”.
Expected result: Scopy should gracefully close.
Actual result:
Start again the application, just like in step 4.
- Press “Continue”.
Expected result: The window containing the license agreement should close and Scopy should be still running.
Actual result:
Tested OS:
Comments:
Result: PASS/FAIL
Test 4: Check Scopy macOS
UID: TST.START.MACOS
- Precondition:
OS: macOS intel
Description: This test checks whether the Scopy macOS installer successfully installs the application and ensures it launches correctly on a macOS operating system with an x86_64 architecture.
- Steps:
Download Scopy macOS installer from the release page.
- Unzip the archive.
Expected result: A DMG file named Scopy-macos should be extracted. (the file name will also contain the macOS version and the commit hash)
Actual result:
- Double-click the file.
Expected result: A pop-up that contains the Scopy icon will appear
Actual result:
- Install the application by right clicking the file and click on Open.
Expected result: A error pop-up will appear.
Actual result:
- Click on Cancel and after that repeat the step 4, right click on the file, and click on Open.
Expected result: A warning pop-up will appear. Different than the first one by including an Open button.
Actual result:
- Click on Open
Expected result: After a while, a window with the GUI of the application should open. Inside the application, a window containing the license agreement should appear with 2 buttons “Exit” and “Continue”.
Actual result:
- Press “Exit”.
Expected result: Scopy should gracefully close.
Actual result:
Start again the application by right-clicking and click on Open.
- Press “Continue”.
Expected result: The window containing the license agreement should close and Scopy should be still running.
Actual result:
Tested OS:
Comments:
Result: PASS/FAIL
Test 5: Check Scopy Windows installer
UID: TST.START.WINDOWS
- Precondition:
OS: Windows
Description: This test checks whether the Scopy Windows installer successfully installs the application and ensures it launches correctly on a Windows operating system with an x86_64 architecture.
- Steps:
Download Scopy Windows installer from the release page.
- Double-click the installer.
Expected result: A window containing the installation wizard should open. It should contain a drop-down menu from which can be selected the language during the installation.
Actual result:
- Click on OK
Expected result: The installer continues with the License Agreement tab.
Actual result:
- Click on I accept the agreement and on Next.
Expected result: The installer continues with the location where the application will be installed.
Actual result:
- Select a location and click on Next.
Expected result: The installer continues with the list of components that will be installed.
Actual result:
- Click on Next.
Expected result: The installer continues with the Additional Tasks tab.
Actual result:
- Check the “Install drivers for ADALM2000 - Requires Administrative Rights” box and click on Next.
Expected result: The installer continues with the installation summary.
Actual result:
- Click on Install.
Expected result: The application should start installing. At the end of the installation, it should ask for Administrative Rights in order to install ADALM2000 drivers.
Actual result:
- Inside the newly opened window. Follow the ADALM2000 drivers installation by clicking Next and Finish.
Expected result: Both the application and the ADALM2000 drivers installed successfully. And optionally, you can check to restart the computer or not.
Actual result:
Click on Finish.
Tested OS:
Comments:
Result: PASS/FAIL