Page tree
Skip to end of metadata
Go to start of metadata

The user interface (UI), in the industrial design field of human–computer interaction, is the space where interactions between humans and machines occur. The goal of this interaction is to allow effective operation and control of the machine from the human end, whilst the machine simultaneously feeds back information that aids the operators' decision-making process.

Generally, the goal of user interface design is to produce a user interface which makes it easy (self-explanatory), efficient, and enjoyable (user-friendly) to operate a machine in the way which produces the desired result. This generally means that the operator needs to provide minimal input to achieve the desired output, and also that the machine minimizes undesired outputs to the human.

 from wikipedia

Introduction

Bottlenecks user interfaces are for testing purpose. 

Command Line Interface

A commande line interface (CLI) is designed to help testers/developers make use of Bottlenecks software.

Design Rationale

  • Be simple and concise, to make it easy to use;
  • Be complete, to cover Bottlenecks scope;
  • Be natural and alignment with OpenStack CLI, to make users the least effort understand.

Main Concepts

  • Test case: a fine-grain test to measure the performance for certain testing scenario;
  • Test story: a list of test cases that to be executed for testing automatin and identifying bottlenecks;
  • Test suite: top category for certain testing methodology base on which test cases and test stories are devoloped. 

Commands

CommandActionStatus
Usage Help
bottlenecks helpShow Bottlenecks CLI usageSoon
bottlenecks -v|–versionShow version numberSoon
Test Suite Commands
bottlenecks testsuite listList all test suitesSoon
bottlenecks testsuite show <SUITE_NAME>Describe a specific test suiteSoon
 
bottlenecks teststory list [--suite=SUITE_NAME]List all test stories, optional for a specific test suiteSoon
bottlenecks teststory show <STORY_NAME>Describe a specific test storySoon
bottlenecks teststory create <STORY_NAME> <SUITE_NAME> <tc_1[, tc_x]> [--description="Description..."]Create a test story by combining a set of existing test casesSoon
bottlenecks teststory delete <STORY_NAME>Delete a specific test storySoon
bottlenecks teststory run <STORY_NAME>Run a specific test storyCompleted
bottlenecks teststory report <STORY_NAME> [<STORY_TAG>]Show results for a completed storySoon
Test Case Commands
bottlenecks testcase list [--suite=SUITE_NAME] [--story=STORY_NAME]List all test cases, optional for a specific test suite or test storySoon
bottlenecks testcase show  <CASE_NAME>Describe a specific test caseSoon
bottlenecks testcase create <CASE_NAME> <SUITE_NAME> <--file=file_path>Create a test case by a yaml file or key-value pairsSoon
bottlenecks testcase update  <CASE_NAME> <--file=file_path>Update a test case by a yaml file or key-value pairsSoon
bottlenecks testcase delete  <CASE_NAME>Delete a specific test caseSoon
bottlenecks testcase run  <CASE_NAME>Run a specific test caseCompleted
bottlenecks testcase report  <CASE_NAME> [<CASE_TAG>]Show results for a completed test caseSoon
Monitoring Commands
   
   

Resful API

 

 


Page viewed 301 times

  • No labels