in lxtask show memory used by cache as free is already default

Bug #1374599 reported by Lyn Perrine
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Manual Tests
Fix Released
Undecided
Elfy

Bug Description

To reproduce follow the steps of testcase 1510 and when you get to Click view and select memory viewed by cache as free reported memory should decrase. However this is already selected by default So clicking on it again will cause memory usage to increase is intended. Also making it unselect it makes sure that showing cache as free and not showing cache as free both work in lxtask.
the version of lxtask I am using is

lxtask:
  Installed: 0.1.4-3.1ubuntu1
  Candidate: 0.1.4-3.1ubuntu1
  Version table:
 *** 0.1.4-3.1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
        100 /var/lib/dpkg/status

A version that changes the testcase that is correct for the new default is below
<dl>
    <dt>Click on <em>Menu</em> --> <em>System Tools</em> --> <em>Task Manager</em>.</dt>
        <dd>Task Manager session starts.</dd>
    <dt>Click on <em>More Details</em>.</dt>
        <dd>Additional information should appear. <em>You may have to resize the window</em>.</dd>
    <dt>Click <em>View</em> and select <em>Show root tasks</em>.</dt>
        <dd>Root tasks should now appear.</dd>
    <dt>Click <em>View</em> and select <em>Show other tasks</em>.</dt>
        <dd>Other tasks should now appear (e.g. whoopsie).</dd>
    <dt>Click <em>View</em> and unselect <em>Show memory used by cache as free</em>.</dt>
        <dd>Reported memory usage should increase.</dd>
    <dt>To check the readings against system, launch <em>LxTerminal</em> (Menu --> Accessories --> LxTerminal) and issue the command <em>top</em>. Please note that <em>top</em> reports in Kib, so there is a factor 1.024 difference between kB and Kib. </dt>
        <dd>A listing of running processes will appear in the terminal window. <strong> If this does not happen, see the test for LxTerminal to file a bug against it </strong>.</dd>
    <dt>Click on the title bar <em>Command</em>.</dt>
        <dd>The sort order should be changed in alpha-numeric sort order on each click.</dd>
    <dt> Repeat with <em>user</em>, <em>RSS</em>, <em>VMSize</em>, <em>PID</em>, <em>State</em>, <em>Prio</em> and <em>PPID</em>.</dt>
        <dd>The sort order is changed each time.</dd>
    <dt> Launch <em>LxTerminal</em> (Menu --> Accessories --> LxTerminal). </dt>
        <dd> LxTerminal Launches. <strong> If LxTerminal does NOT start, see the test for LxTerminal to file a bug against it</strong>.</dd>
    <dt>Type in <em>top</em> and press <em>Enter</em>.</dt>
        <dd>A listing of running processes will appear in the terminal window. <strong> If this does not happen, see the test for LxTerminal to file a bug against it </strong>.</dd>
    <dt>Click on the title bar <em>Command</em> in order to sort by command name and look through the listing for <em>top</em>, once found right click on it.</dt>
        <dd>A menu offering options should appear.</dd>
    <dt>Select <em> Kill</em></dt>
        <dd>A window will appear asking to confirm.</dd>
    <dt> Click on <em>OK</em>.</dt>
        <dd>Process <strong>top</strong> no longer appears as a running task. (It will also not be seen running in the LxTerminal window).</dd>
</dl>
<strong>
    If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
    If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>.
    Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result</strong>.

Related branches

Revision history for this message
Elfy (elfy) wrote :

It's easier to just have lines to change - it's even easier to review a MP ;)

Changed in ubuntu-manual-tests:
assignee: nobody → Elfy (elfy)
status: New → Fix Committed
Elfy (elfy)
Changed in ubuntu-manual-tests:
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:
http://packages.qa.ubuntu.com/qatracker/reports/bugs/1374599

tags: added: package-qa-testing
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.