Project

General

Profile

action #67393

coordination #36712: [saga] Use YaST specific framework for GUI testing

[functional][y] Selection of rows does not work as expected when set in JSON in different order than are displayed

Added by JERiveraMoya about 1 year ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2020-05-28
Due date:
% Done:

0%

Estimated time:

Description

Selection of rows does not work as expected when rows are displayed in different order that are represented in JSON, or at least that it is my assumption.
I could see this happen in yast2 partitioner in the first table that is displayed for the partition of one disk.
So when trying to select /dev/vda3 (not even adding the column index) it is selecting /dev/vda2 and viceversa on the server side.

curl -X POST "http://localhost:9998/widgets?id=%22Y2Partitioner%3A%3AWi
dgets%3A%3AConfigurableBlkDevicesTable%22&action=select&value=/dev/vda2"

curl -X POST "http://localhost:9998/widgets?id=%22Y2Partitioner%3A%3AWi
dgets%3A%3AConfigurableBlkDevicesTable%22&action=select&value=/dev/vda3"
  {
    "alignment" : 
    [
      "left",
      "right",
      "center",
      "center",
      "left",
      "left",
      "left"
    ],
    "class" : "YTable",
    "columns" : 7,
    "hasMultiSelection" : false,
    "header" : 
    [
      "Device",
      "Size",
      "F",
      "Enc",
      "Type",
      "Label",
      "Mount Point"
    ],
    "hstretch" : true,
    "icon_base_path" : "",
    "id" : "\"Y2Partitioner::Widgets::ConfigurableBlkDevicesTable\"",
    "immediate_mode" : true,
    "items" : 
    [
      {
        "icons" : 
        [
          "",
          "",
          "",
          "",
          "drive-harddisk",
          "",
          ""
        ],
        "labels" : 
        [
          "/dev/vda",
          "30.00 GiB",
          "",
          "",
          "Disk",
          "",
          ""
        ]
      },
      {
        "icons" : 
        [
          "",
          "",
          "",
          "",
          "drive-partition",
          "",
          ""
        ],
        "labels" : 
        [
          "/dev/vda1",
          "8.00 MiB",
          "",
          "",
          "BIOS Boot Partition",
          "",
          ""
        ]
      },
      {
        "icons" : 
        [
          "",
          "",
          "",
          "",
          "drive-partition",
          "",
          ""
        ],
        "labels" : 
        [
          "/dev/vda3",
          "2.00 GiB",
          "",
          "",
          "Swap Partition",
          "",
          "swap"
        ]
      },
      {
        "icons" : 
        [
          "",
          "",
          "",
          "",
          "drive-partition",
          "",
          ""
        ],
        "labels" : 
        [
          "/dev/vda2",
          "27.99 GiB",
          "",
          "",
          "BtrFS Partition",
          "",
          "/"
        ],
        "selected" : true
      }
    ],
    "items_count" : 4,
    "keep_sorting" : false,
    "notify" : true,
    "vstretch" : true
  }

History

#1 Updated by JERiveraMoya about 1 year ago

  • Description updated (diff)

#2 Updated by riafarov about 1 year ago

  • Assignee set to riafarov
  • Target version set to future

So issue is not generic and seems not to work in some cases like expert partitioner, even though it works in yast2 host just fine.
It's not related to the order in json and in UI as those work independently and are consistent.

Also available in: Atom PDF