Development Team/Memory/Leak testing: Difference between revisions

(5 intermediate revisions by 4 users not shown)

Line 3:

== Install guppy ==

If you don't already have guppy on the XO you want to test, you'll have to download and install it. In [[Terminal]], as [[root]]:

If you don't already have guppy on the XO (or other computer running sugar) you want to test, you'll have to download and install it. In Terminal, as root:

<pre>

Line 26:

== Starting a heapy session ==

[[ssh into the XO]] from another computer. We'll call this the Monitor Computer, and it should be separate from the XOs you are testing. When we observe Sugar, it is best not use it for anything else than to execute the test case. From your Monitor computer, in the shell you're ssh'd into your XO with:

ssh into the XO (or othe rcomputer running sugar) from another computer. We'll call this the Monitor Computer, and it should be separate from the XOs or cumputers you are testing. When we observe Sugar, it is best not use it for anything else than to execute the test case. From your Monitor computer, in the shell you're ssh'd into your XO with:

<pre>

Line 43:

</code>

Then, on your XO, do whatever action you're testing memory leaks for. (For instance, start and then close an Activity.)

Then, on your XO (or computer with sugar), do whatever action you're testing memory leaks for. (For instance, start and then close an Activity.)

Go back to your monitor computer and type:

Line 104:

=== Without collaboration ===

If you run a test multiple times and get results with a lot of variance, it may be due to collaboration activity (especially if you're in a radio-noisy environment ~~with many XOs~~). You can solve this by disabling radio (in the Sugar Control Panel) and using an usb-to-ethernet dongle to give the XO a wired connection to ssh into.

If you run a test multiple times and get results with a lot of variance, it may be due to collaboration activity (especially if you're in a radio-noisy environment). You can solve this by disabling radio (in the Sugar Control Panel) and using an usb-to-ethernet dongle to give the XO or computer a wired connection to ssh into.

@@ Line 3: / Line 3: @@
 == Install guppy ==
-If you don't already have guppy on the XO you want to test, you'll have to download and install it. In [[Terminal]], as [[root]]:
+If you don't already have guppy on the XO (or other computer running sugar) you want to test, you'll have to download and install it. In Terminal, as root:
 <pre>
@@ Line 26: / Line 26: @@
 == Starting a heapy session ==
-[[ssh into the XO]] from another computer. We'll call this the Monitor Computer, and it should be separate from the XOs you are testing. When we observe Sugar, it is best not use it for anything else than to execute the test case. From your Monitor computer, in the shell you're ssh'd into your XO with:
+ssh into the XO (or othe rcomputer running sugar) from another computer. We'll call this the Monitor Computer, and it should be separate from the XOs or cumputers you are testing. When we observe Sugar, it is best not use it for anything else than to execute the test case. From your Monitor computer, in the shell you're ssh'd into your XO with:
 <pre>
@@ Line 43: / Line 43: @@
 </code>
-Then, on your XO, do whatever action you're testing memory leaks for. (For instance, start and then close an Activity.)
+Then, on your XO (or computer with sugar), do whatever action you're testing memory leaks for. (For instance, start and then close an Activity.)
 Go back to your monitor computer and type:
@@ Line 104: / Line 104: @@
 === Without collaboration ===
-If you run a test multiple times and get results with a lot of variance, it may be due to collaboration activity (especially if you're in a radio-noisy environment with many XOs). You can solve this by disabling radio (in the Sugar Control Panel) and using an usb-to-ethernet dongle to give the XO a wired connection to ssh into.
+If you run a test multiple times and get results with a lot of variance, it may be due to collaboration activity (especially if you're in a radio-noisy environment). You can solve this by disabling radio (in the Sugar Control Panel) and using an usb-to-ethernet dongle to give the XO or computer a wired connection to ssh into.