JFH17 Issues Found
Put notes about issues found here.
Answer: put each issue in it's own 2nd-level section (sections names start and end with '=')
Just describe the issue, and put relevant information. If it's significant, consider creating an issue on in the Fuego Issues List
Description: It is difficult for a new user to determine what icons or test items to click on to achieve any specific task.
If you click on something, will it trigger an action or just show some data?
- On the test page with a view tab selected, if you click on the name - what happens?
- If I hover on the status icon, it shows a text description of the status, but clicking on it does nothing.
- If I hover on the clock icon on the right end of the line, it says schedule a build, but without hovering the icon has no meaning to me.
- Hovering on the name doesn't show any text, but does expose a down arrow. Clicking on the down arrow then provides a menu.
Back to Japan Fuego Hackathon 2017
Following error occurs when following the quick start guide at step 3 of http://fuegotest.org/wiki/Fuego_Quickstart_Guide#Download,_build,_start_and_access
This was on the raspberry pi 3, used at the class.
Should investigate socat, or some way of keeping using a single ssh connection for multiple commands.
ssh allows you to change encryption method, which may take less time.
We should see how many ssh connections we establish during a test and see if it can be reduced.
It means to select tests from the pre-existing Fuego tests, to add to the Jenkins interface, but this is a concept that is unknown to new users.
The wording needs to be changed here.
- (container prompt)$ ftc add-nodes myboard docker
- (container prompt)$ ftc add-jobs -b docker -p testplan_docker
But the guide explained how to add board and toolchain. User is confused to prepare virtual/phiscal board to try to execute test on Fuego.
When presenting this to new users, to explain how to write a test, it's a bit embarrassing having to explain what this is.
Note: this is used in log_compare, and in the location for the test in test_deploy and test_run.
We should change it, but we probably need to leave TESTDIR, as it's used internally practically everywhere. So, we should probably leave TESTDIR in place, and add a TEST_NAME or similar variable, and start using that in all the fuego_test.sh scripts in the repository.
For backwards compatibility with existing tests, we should probably migrate to a new function that doesn't use this parameter.