- Table of Contents
- 1 Introduction
- 1.1 Overview
- 1.2 Revision History
- 1.3 References
- 1.4 Prerequisites
- 1.5 Equipment Required
- 1.6 Safety
- 1.7 Ongoing Maintenance
- 1.8 Bug Reporting Process
- 2 Test Matrix
- 3 Test Steps
- 3.1 Software Download and Install
- 3.2 Launch and Splash Screen
- 3.2.1 Start Menu
- 3.2.2 Launch
- 3.2.3 Splash Screen
- 3.2.4 Add Printer
- 3.2.5 Select Model
- 3.2.6 Machine Settings
- 3.3 Main Screen and 3D Preview
- 3.3.1 Top Level Menus
- 3.3.2 Toolbar
- 3.3.3 3D Preview
- 3.3.4 Prepare
- 3.3.5 Monitor
- 3.3.6 Load Model
- 3.3.7 Model Preview
- 3.3.8 Preview Toolbar
- 3.3.9 Zoom/Rotate
- 3.4 Slicing, Saving to G-code
- 3.5 Menu
- 3.6 Control Functions and Test Print
- 3.6.1 Print Monitor
- 3.6.2 Connect
- 3.6.3 Tab Window
- 3.6.4 Connection
- 3.6.5 Axes Moving
- 3.6.6 Hot End Temperature
- 3.6.7 Bed Temperature
- 3.6.8 Extruding
- 3.6.9 Retracting
- 3.6.10 Open Model File
- 3.6.11 Print
- 3.6.12 Verify Print
- 3.6.13 Remove Print
- 3.7 Software Uninstall and Shutdown
Date: 05 Mar 2018
Copyright 2017-2018 by Aleph Objects, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution 4.0 International Public License (CC BY-SA 4.0).
This document lists the test procedure steps for the “smoke test” for the Cura LulzBot Edition software used with the Lulzbot 3D printers.
The “smoke test” is a short (approximately 15 minutes per test configuration) go-no test that is performed on new builds of Cura on a regular basis. It does a basic sanity test to ensure that the build installs, launches, basic UX features work, and a short test print can be made.
|0.0.0||21 July 2017||Jeff Tranter||Initial draft started.|
|0.9.0||17 Aug 2017||Jeff Tranter||Ready for initial use.|
|0.9.1||03 Nov 2017||Jeff Tranter||Reflect name change from cura2 to cura-lulzbot|
|0.9.2||30 Nov 2017||Jeff Tranter||Minor updates|
|0.9.3||05 Mar 2018||Jeff Tranter||Updated to reflect Cura Lulzbot 3.2|
- LulzBot Mini Quick Start Guide, //https://download.lulzbot.com/Mini/1.04/documentation/quick_start_guide//
- LulaBot Mini User Manual, //https://download.lulzbot.com/Mini/1.04/documentation/manual//
- LulzBot TAZ Quick Start Guide, //https://download.lulzbot.com/TAZ/6.02/documentation/guide///
- LulzBot TAZ User Manual, //https://download.lulzbot.com/TAZ/6.02/documentation/guide///
- LB-TP-0002, Aleph Objects Cura LulzBot Functional Test Procedure
The tester requires a basic knowledge of how to operate the LulzBot 3D printer including hardware configuration, loading filament, removing print from the bed, cleaning the bed, and safety issues. Refer to the appropriate manuals listed under References for more details.
On the Mac platform you will need to change a setting to allow installing applications that did not come from the app store:
For macOS 10.11 (El Capitan):
- Launch System Preferences from the dock.
- Select Security & Privacy.
- Click on the lock icon and enter your password.
- Select Allow apps downloaded from: Anywhere
- Close the settings dialog.
For macOS 10.12 (Sierra) and 10.13 (High Sierra): You will need to first download and try to run the application before changing the settings:
- Launch System Preferences from the dock.
- Select Security & Privacy.
- Click on the lock icon and enter your password.
- In the General tab you should see a message such as “Cura was blocked from opening because it is not from an identified developer”. Click on “Open Anyway”. MacOS will then note the developer and add it to its internal list of identified developers. If you download a different app from the same developer, Sierra will look for the developer on the list and if it sees the developer, the new app will open.
For more information see:
On Debian Stretch, the sudo program may not have been installed during OS installation. If not, run these commands to install it and add the current user to the group allowed to run sudo (replace <username> with the name of the user account used for testing):
su (Enter root password when prompted)
apt-get install sudo
deluser <username> floppy (Works around 10 group limit per user)
adduser <username> sudo
The following hardware and software is required in order to perform the test procedure:
- A Lulzbot Mini or Taz 6 3D printer with USB cable.
- A desktop or laptop computer with display and mouse.
- The Cura software to be tested.
- Suitable filament (e.g. PLA).
- STL file for loading: rocktopus.stl
- STL file for test print: OpenHardwareKeychain.stl
- A known good 3D print of OpenHardwareKeychain.stl printed with the High speed profile.
The tester should have read and be familiar with the Start Here and User Manuals, including the safety instructions at the start of the User Manuals. Heed the warnings about possible electrical shock hazard, burn hazard, fire hazard, and pinch hazard. Do not leave the 3D printer operating or powered on when unattended.
On a weekly basis the following maintenance tasks and checks should be performed:
- Wipe clean the smooth rods.
- Clean print surface with isopropyl alcohol.
- Check that the hobbed bolt is clean of filament.
- Check tightness of belts.
- Clean hot end off any buildup of extruded material.
- Check if the nozzle wiping pad needs to be replaced.
- Clean bed leveling washers.
- Blow out any dust from the cooling fans and control box.
See Section 3, Maintaining Your Printer, of the User Manual.
Test failures should be reported on the Cura board at (//https://code.alephobjects.com/project/board/10///). Select “Create Tasks” and enter the information about the issue. Be sure to include the following:
- A meaningful title
- A description that includes the software version, hardware used, test that failed, expected result, observed result, and any other information that may be helpful.
- Enter “Cura 2” under Tags
Leave the Assigned To, Status, and Priority fields at their default values. The bug will be reviewed and assigned to a developer. Monitor the bug so that you respond to any questions that the developer may have about it, and retest it when a fix is made.
It may sometimes be useful to include log files when Cura crashes or produces an error. The log files can be found in these locations (the version number, 3.2 below, will vary):
Mac: /Users/<username>/Library/Application Support/cura-lulzbot/3.2/cura-lulzbot.log
The tests should be performed for the following combinations of 3D printer, computer operating system and version, and screen resolution.
|Printer Model||Computer||Operating System||Screen Resolution|
|Lulzbot Mini||PC||Debian (Stretch)||1920x1080|
|LulzBot Mini||PC||Debian (Stretch)||1152x864|
|LulzBot Mini||PC||Linux (Ubuntu Xenial 16.04)||1920x1080|
|LulzBot Mini||PC||Linux (Ubuntu Xenial 16.04)||1152x864|
|LulzBot Mini||PC||Linux (Ubuntu Artful 17.10)||1920x1080|
|LulzBot Mini||PC||Linux (Ubuntu Artful 17.10)||1152x864|
|LulzBot Mini||PC||Windows 7||1920x1080|
|LulzBot Mini||PC||Windows 7||1280x720|
|LulzBot Mini||PC||Windows 10||1920x1080|
|LulzBot Mini||PC||Windows 10||1366x768|
|LulzBot Mini||Mac Mini||MacOS 10.11 “El Capitan”||1366x768|
|LulzBot Mini||Mac Mini||MacOS 10.11 “El Capitan”||1920x1080|
|LulzBot Mini||iMac||MacOS 10.13 “High Sierra”||4096x2304|
|Lulzbot TAZ 6||PC||Debian (Stretch)||1920x1080|
|LulzBot TAZ 6||PC||Debian (Stretch)||1152x864|
|LulzBot TAZ 6||PC||Linux (Ubuntu Xenial 16.04)||1920x1080|
|LulzBot TAZ 6||PC||Linux (Ubuntu Xenial 16.04)||1152x864|
|LulzBot TAZ 6||PC||Linux (Ubuntu Artful 17.10)||1920x1080|
|LulzBot TAZ 6||PC||Linux (Ubuntu Artful 17.10)||1152x864|
|LulzBot TAZ 6||PC||Windows 7||1920x1080|
|LulzBot TAZ 6||PC||Windows 7||1280x720|
|LulzBot TAZ 6||PC||Windows 10||1920x1080|
|LulzBot TAZ 6||PC||Windows 10||1366x768|
|LulzBot TAZ 6||Mac Mini||MacOS 10.11 “El Capitan”||1366x768|
|LulzBot TAZ 6||Mac Mini||MacOS 10.11 “El Capitan”||1920x1080|
|LulzBot TAZ 6||iMac||MacOS 10.13 “High Sierra”||4096x2304|
The following additional information should be recorded as part of the test results:
- Test engineer
- Cura software version
- Print material (e.g. PLA)
- Extruder type and model
- Computer and display models
Ensure any previous version of Cura has been uninstalled and configuration files removed so that you can test an initial install.
Open a console and run the following commands:
sudo apt-get remove cura-lulzbot
rm -rf ~/.cache/cura-lulzbot ~/.config/cura-lulzbot ~/.local/share/cura-lulzbot
Run the Cura uninstaller (if not done already at the end of the previous test run) by running Add or remove programs, finding cura-lulzbot, and selecting Uninstall. Then, remove these folders using Windows Explorer:
\Program Files (x86)/cura-lulzbot 3.2
\Program Files/cura-lulzbot 3.2
Where username is the username you logged in under. You will normally only see one of the first two folders, depending on whether you are running the 32-bit or 64-bit version of Windows. The version (3.2 above) will vary depending on the version of Cura that is installed.
Uninstall Cura (if not already done at the end of the previous test run) by selecting from the Finder Go / Applications, click on Cura, then select File / Move to Trash.
Open Terminal and run the following command:
rm -rf ~/Library/Application\ Support/cura-lulzbot
Download and install the software.
Open a web browser and navigate to //http://devel.alephobjects.com/lulzbot/software/Cura2///
Select the “linux”, “mac”, or “windows” directory, as appropriate for the system under test.
Save the desired program (.exe, or .dmg) to the local hard disk in the downloads directory. For Linux, the software can be downloaded as part of the next step. Set up the /etc/apt/sources.list file as described in the README.debian file on the server.
Install the software using the platform-specific steps below.
Open a console, and run the following commands:
sudo apt-get update
sudo apt-get install cura-lulzbot
Check that the version listed (i.e. in the message “Preparing to unpack .../cura-lulzbot_3.2.9_amd64.deb”) is the expected one and that the command succeeds.
From the Windows Explorer, navigate to Downloads and double click on the downloaded file (e.g. ￼cura-lulzbot_3.2.9_win32.exe)
If Windows Defender complains about an unrecognized app, select “More info” and “Run anyway”.
Step through the installer, hitting Next, and accepting all defaults.
Ensure that the installer succeeds.
Click on Downloads in the dock at the lower right of the desktop.
Click on the file downloaded (e.g. cura-lulzbot_3.2.9.dmg). The downloaded dmg file will open and show an Applications folder and Cura file icon.
Drag the Cura icon onto the Applications folder icon.
Ensure the copying of the file succeeds.
Confirm that Cura shows up under the start/launch menu.
On Windows, from the Start menu it should appear under cura-lulzbot 3.2.9 (the version number will vary).
On Mac, from the Finder select Go / Applications, and confirm that Cura appears in the Applications folder.
On Ubuntu Linux running the Unity desktop, if you click on the search icon at the top left and type in Cura, you should see it listed under Applications. While it is running you will see it in the sidebar. Under the KDE Plasma or Gnome desktops it should appear in the Launcher button under Applications / Graphics / 3D Printing Software.
Connect the printer to the computer using a USB cable and power it on. Launch the application (from the start menu, or on Mac from the Applications folder). On Mac, the first time you launch a new version, you will probably see the message “Cura is an application downloaded from the Internet. Are you sure you want to open it?”. If so, select Open.
Verify that the Cura LulzBot Edition custom splash screen appears. Verify that the software version in the splash screen is correct and that it correctly indicates Alpha, Beta, or release version.
Verify that on this first launch the User Agreement dialog comes up. Click on the “I understand and agree” button to dismiss it.
Then verify that on this first launch you are prompted to Add Printer and that the models are correct for LulzBot.
Select the LulzBot Hibiscus, Mini, or TAZ model, as appropriate for the hardware that you are testing with. Click on the “Add Printer” button.
Verify Add Printer / Machine Settings dialog appears. Click on “Finish”.
Check that the top level menus appear: File, Edit, View, etc. (they will be checking in detail later).
Check that the green toolbar on the left is shown with icons for open file, move, scale, etc.
Check that a 3D preview appears with printer bed. Verify it rotates with keyboard cursor keys and when moving the mouse with the right button held down (if present). Confirm that the preview zooms in and out using the mouse scroll wheel (if present).
Check that the Prepare tab appears at the upper left and the prepare pane appears on the right side.
Click on the Monitor tab on the upper left. Confirm that the prepare pane changes to show the monitor pane.
Click to select the prepare pane. Load a model by clicking on the Open File icon at the top left of the 3D preview pane and navigating to rocktotpus.stl
Verify that the model appears in the 3D preview.
Click on the model in 3D preview. Verify that the actions in the left toolbar become active.
Click on the Move, Scale, and Rotate tool buttons and confirm that they operate.
Verify that slicing completes (as show at the bottom of the prepare pane) and the estimated time, filament length, and weight are shown at the bottom right of the main view. The text ”Slicing…” in the prepare pane should change to “Ready to Print via USB” and the bottom right of the preview pane should show information similar to (the actual numbers will vary):
73.0 x 74.2 x 19.2 mm
00h 51min 0.85m / ~10g
Confirm that you can save G-code to a file by making sure that the combo box at the bottom of the prepare pane is set to Save to File, clicking on Save to File, and saving the G-code file using the Save to File dialog.
Verify that the following menus appear (you don’t need to test the functions of the menus, only that they appear. Not all menu entries will be enabled.):
cura-lulzbot (Mac only)
Save Selection to File
Reload All Models
Quit (not on Mac)
Select All Models
Arrange All Models
Delete Selected Models
Clear Build Plate
Reset All Model Positions
Reset All Model Transformations
Left Side View
Right Side View
Configure setting visibility… (not on Mac)
Extensions (the order of the sub-menus below may vary between platforms)
Model Subdivider Plugin (Experimental)
Preferences (not on Mac)
Show Configuration Folder
Show Online Documentation
Report a Bug
About... (not on Mac)
Select monitor pane (using the tab button at the upper left) and confirm that the print monitor functions appear.
Click on Connect, Verify that within a few seconds it reports that the printer is connected and the hot end and build plate temperatures start to appear on the graph.
Verify that the monitor tab window scrolls properly to the top and bottom using the scrollbar on the right. At high screen resolutions the window may fit entirely on the screen and no scrollbar will be shown.
Verify that you can click on Disconnect and Connect, and that the printer is reported as disconnecting and connecting. Verify that clicking on Console opens a console window and G-code commands are displayed.
Verify moving in the X, Y, and Z axes and moving to Home positions using the appropriate X/Y, X, Home X, and Home Y buttons.
Set a hot end temperature by entering a value in the Select Temperature field (e.g. 205), clicking on Heat extruder, and verifying that the extruder reaches the selected temperature.
Set a bed temperature by entering a value in the Select Temperature field (e.g. 60), clicking on Heat bed, and verify that the bed reaches the selected temperature.
Extrude some material by clicking on Extrude several times (make sure the hot end is at a suitable temperature, e.g. 205° for PLA).
Retract the filament by clicking on Retract and verifying that the filament is retracted (make sure that the hot end is still hot as in the previous step).
Click on the Pepare tab. Open the model file OpenHardwareKeychain.stl and verify that a 3D preview is shown.
Ensure that the High Speed profile is selected, and then select Print. Confirm that the Monitor tab is opened.
Verify the following states of printing:
- the bed and hot end heat up
- the nozzle is wiped
- bed levelling is performed
- the model prints correctly, including skirt
- the unit waits for cool down and then moves to the home position to allow removal of the print.
Remove the 3D print (using a knife or other suitable tool) and confirm that it printed correctly as compared to a previous known good print of the same model using the High speed profile.
Close the Cura application by selecting (on Windows and Linux) File / Quit or (on Mac) Cura / Quit Cura.
Turn off the printer using the power switch and disconnect the USB cable from the computer.
Uninstall the software and remove configuration files, following the instructions in section 3.1.1.
UPDATE on on Operating Systems being used for smoke testing:
Mac OS X (El Capitan)
Mac OS X (High Sierra)
Mac OS X (Mojave)
Also 2 additional testing steps have been added to smoke test procedure:
Testing "Home All" function
Testing Pausing and resuming prints