sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Changed "Ptest" to "ptest" 

(From yocto-docs rev: b4e2139e1d3b0ff1857c6399f1ce767f3573b3f7)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-04-15 13:39:25 -07:00 committed by Richard Purdie
parent 1c597ac036
commit c11ea046b8
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -3481,7 +3481,7 @@
<para>
A Package Test (ptest) runs tests against packages built
by the OpenEmbedded build system on the target machine.
Minimally, a Ptest contains two things: a shell script that
Minimally, a ptest contains two things: a shell script that
starts the test (<filename>run-ptest</filename>),
and the actual test.
The shell script that starts the test must not contain
@ -3508,7 +3508,7 @@
<title>Getting Your Package Ready</title>
<para>
In order to run installed Ptests on target hardware,
In order to run installed ptests on target hardware,
you need to prepare the recipes that build the packages
you want to test.
Here is what you have to do for each recipe:
@ -3630,7 +3630,7 @@
<para>
The <filename>ptest-runner</filename> package installs a
shell script that loops through all installed Ptest test
shell script that loops through all installed ptest test
suites and runs them in sequence.
Consequently, you might want to add this package to
your image.