Testcase 1591 blueman, some issues

Bug #1776740 reported by Willem Hobers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Manual Tests
Triaged
Undecided
Unassigned

Bug Description

General remark: most parts of the test are not mandatory. Some one without any bluetooth devices, will only do the first two steps and then skip the rest – and report the test a success. We should perhaps add a note that people should leave a comment on which parts they skipped?

“Change the name to "blueman_test". Click on close.
The box for the name is called “Friendly Name”

“The window closes. You changed the name of the computer's Bluetooth adapter.”
We haven’t really checked if indeed the name change persists. Perhaps add a way to find out if it did indeed change?

“The test requires a Bluetooth device with search functionality for other Bluetooth devices, e.g. a mobile phone. If you do not have one, skip the test.”
In other test cases this kind of directions are mostly not part of the numbered list I believe.
These kind of directions appear, also as part of the numbered list, at several places in this test case.

“Click on "forward".”
The button is “next”, at my end.

“Search for your input device and select it. Click on "Forward".”
The button is “next”, at my end

“Select "Proceed without pairing" and click on "Forward".”
The button is “next”, at my end

“Select "input device" and click on "Forward".”
The button is “next”, at my end

(I’ll just add that there’s “forward” throughout the test case, but the button seems to be called “next”.)

“Search for your input device and select it. Click on "Forward".
A window with pairing options appears.”
I don’t think so. I tried this with a phone – the question I got was “Connect to: Audio Source, Netwrork Access Point, Don’t connect”.

I chose Audio Source to see if I could proceed with the test case.

“Select "Use random Passkey" and click on "Forward".
A random passkey is generated and shown in the assistant.
Accept the connection in your storage device and enter the passkey.
The device is added to your computer. The "Connect" window appears.”

This didn’t work as described here. The passkey was generated and all I had to do was accept or deny. I did not have to put in the number by hand.

Haven’t been able to check this part of the test, because things work differently for me (I don't have a BT mouse or keyboard):
“Select "serial port" and click on "Forward".
A window appears showing "Device added successfully."
Click on "close" and open the context menu again. Click on "Browse file on devices".
A window appears with a list of available Bluetooth devices.
Select your storage device and click on "OK". Accept the connection on your device.
The file manager is opening, showing the available data on the device.”

Revision history for this message
Kev Bowring (flocculant) wrote : Re: [Bug 1776740] [NEW] Testcase 1591 blueman, some issues

On 13/06/18 19:32, Willem Hobers wrote:
> Public bug reported:
>
> General remark: most parts of the test are not mandatory. Some one
> without any bluetooth devices, will only do the first two steps and then
> skip the rest – and report the test a success. We should perhaps add a
> note that people should leave a comment on which parts they skipped?
>
> “Change the name to "blueman_test". Click on close.
> The box for the name is called “Friendly Name”
>
> “The window closes. You changed the name of the computer's Bluetooth adapter.”
> We haven’t really checked if indeed the name change persists. Perhaps add a way to find out if it did indeed change?
>
> “The test requires a Bluetooth device with search functionality for other Bluetooth devices, e.g. a mobile phone. If you do not have one, skip the test.”
> In other test cases this kind of directions are mostly not part of the numbered list I believe.
> These kind of directions appear, also as part of the numbered list, at several places in this test case.
>
> “Click on "forward".”
> The button is “next”, at my end.
>
> “Search for your input device and select it. Click on "Forward".”
> The button is “next”, at my end
>
> “Select "Proceed without pairing" and click on "Forward".”
> The button is “next”, at my end
>
> “Select "input device" and click on "Forward".”
> The button is “next”, at my end
>
> (I’ll just add that there’s “forward” throughout the test case, but the
> button seems to be called “next”.)
>
> “Search for your input device and select it. Click on "Forward".
> A window with pairing options appears.”
> I don’t think so. I tried this with a phone – the question I got was “Connect to: Audio Source, Netwrork Access Point, Don’t connect”.
>
> I chose Audio Source to see if I could proceed with the test case.
>
> “Select "Use random Passkey" and click on "Forward".
> A random passkey is generated and shown in the assistant.
> Accept the connection in your storage device and enter the passkey.
> The device is added to your computer. The "Connect" window appears.”
>
> This didn’t work as described here. The passkey was generated and all I
> had to do was accept or deny. I did not have to put in the number by
> hand.
>
> Haven’t been able to check this part of the test, because things work differently for me (I don't have a BT mouse or keyboard):
> “Select "serial port" and click on "Forward".
> A window appears showing "Device added successfully."
> Click on "close" and open the context menu again. Click on "Browse file on devices".
> A window appears with a list of available Bluetooth devices.
> Select your storage device and click on "OK". Accept the connection on your device.
> The file manager is opening, showing the available data on the device.”
>
> ** Affects: ubuntu-manual-tests
> Importance: Undecided
> Status: New
>
I'm inclined towards removing any refs to parts being optional, make all
parts of the test required.

The testcase itself in the testsuite is optional in it's entirety
(http://packages.qa.ubuntu.com/qatracker/milestones/391/builds/173777/testcases)

Changed in ubuntu-manual-tests:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.