Opened 12 years ago

Last modified 8 years ago

#954 new task

IZ13: qlogin qsh tests needed

Reported by: joga Owned by:
Priority: normal Milestone:
Component: testsuite Version: current
Severity: Keywords: tests
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=13]

        Issue #:      13              Platform:     All           Reporter: joga (joga)
       Component:     testsuite          OS:        All
     Subcomponent:    tests           Version:      current          CC:    None defined
        Status:       NEW             Priority:     P3
      Resolution:                    Issue type:    TASK
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
          URL:
       * Summary:     qlogin qsh tests needed
   Status whiteboard:
      Attachments:

     Issue 13 blocks:
   Votes for issue 13:     Vote for this issue


   Opened: Fri Nov 10 01:44:00 -0700 2006 
------------------------


This was IZ 155 in project gridengine.

create qlogin and qsh connection to each exec host

------- Additional comments from crei Wed Feb 20 08:46:21 -0800 2002 -------

this is an enhancement

------- Additional comments from joga Thu Jul 18 23:13:58 -0800 2002 -------

Needed for qsh:
- testing the passing of parameters to the xterm executed (syntax qsh
--  <xterm options>, e.g. qsh -- -e <script>

------- Additional comments from joga Tue Sep 10 03:46:08 -0800 2002 -------

Additional tests needed for qsh:
- no DISPLAY environment variable set (must give error message)
- empty DISPLAY environment variable set (must give error message)
- local DISPLAY variable set (e.g. :0.0) (must give error message:
something like "empty environment variable DISPLAY ..." in 5.3, a more
concrete error message in maintrunc systems).

The same tests have to be done, if DISPLAY is passed via -v option and
the -display option.

Additional (more theoretic) test case:
Submit a qsh -now no -h and change DISPLAY with qalter. Same rules
have to apply as named above.

Change History (0)

Note: See TracTickets for help on using tickets.