Skip to content
Snippets Groups Projects
Select Git revision
0 results

test.py

Blame
  • Forked from Reform / reform-boundary-uboot
    Loading
    • Stephen Warren's avatar
      d201506c
      test/py: Implement pytest infrastructure · d201506c
      Stephen Warren authored
      This tool aims to test U-Boot by executing U-Boot shell commands using the
      console interface. A single top-level script exists to execute or attach
      to the U-Boot console, run the entire script of tests against it, and
      summarize the results. Advantages of this approach are:
      
      - Testing is performed in the same way a user or script would interact
        with U-Boot; there can be no disconnect.
      - There is no need to write or embed test-related code into U-Boot itself.
        It is asserted that writing test-related code in Python is simpler and
        more flexible that writing it all in C.
      - It is reasonably simple to interact with U-Boot in this way.
      
      A few simple tests are provided as examples. Soon, we should convert as
      many as possible of the other tests in test/* and test/cmd_ut.c too.
      
      The hook scripts, relay control utilities, and udev rules I use for my
      own HW setup are published at https://github.com/swarren/uboot-test-hooks
      
      .
      
      See README.md for more details!
      
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Tested-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Tested-by: default avatarSimon Glass <sjg@chromium.org>
      Acked-by: Simon Glass <sjg@chromium.org> #v3
      d201506c
      History
      test/py: Implement pytest infrastructure
      Stephen Warren authored
      This tool aims to test U-Boot by executing U-Boot shell commands using the
      console interface. A single top-level script exists to execute or attach
      to the U-Boot console, run the entire script of tests against it, and
      summarize the results. Advantages of this approach are:
      
      - Testing is performed in the same way a user or script would interact
        with U-Boot; there can be no disconnect.
      - There is no need to write or embed test-related code into U-Boot itself.
        It is asserted that writing test-related code in Python is simpler and
        more flexible that writing it all in C.
      - It is reasonably simple to interact with U-Boot in this way.
      
      A few simple tests are provided as examples. Soon, we should convert as
      many as possible of the other tests in test/* and test/cmd_ut.c too.
      
      The hook scripts, relay control utilities, and udev rules I use for my
      own HW setup are published at https://github.com/swarren/uboot-test-hooks
      
      .
      
      See README.md for more details!
      
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Tested-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Tested-by: default avatarSimon Glass <sjg@chromium.org>
      Acked-by: Simon Glass <sjg@chromium.org> #v3