summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMarcin Juszkiewicz <hrw@openembedded.org>2007-04-05 18:20:42 +0000
committerMarcin Juszkiewicz <hrw@openembedded.org>2007-04-05 18:20:42 +0000
commit328eff19a08bd399c6a833d213862039b4432b05 (patch)
treee20fa9422b90a51da620e168dba7f32764bba5c9 /doc
downloadoetest-328eff19a08bd399c6a833d213862039b4432b05.tar.gz
oetest-328eff19a08bd399c6a833d213862039b4432b05.tar.bz2
oetest-328eff19a08bd399c6a833d213862039b4432b05.zip
import of bitbake-qa bittest util which can be used as:
- source availability checker - source mirror populate tool - and few others branch is named 'oetest' because this tool will be renamed to 'oetest' as it is useful only with OE metadata
Diffstat (limited to 'doc')
-rw-r--r--doc/.mtn2git_empty0
-rw-r--r--doc/ADD_YOUR_CHECK7
-rw-r--r--doc/README24
3 files changed, 31 insertions, 0 deletions
diff --git a/doc/.mtn2git_empty b/doc/.mtn2git_empty
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/doc/.mtn2git_empty
diff --git a/doc/ADD_YOUR_CHECK b/doc/ADD_YOUR_CHECK
new file mode 100644
index 0000000..d2408dd
--- /dev/null
+++ b/doc/ADD_YOUR_CHECK
@@ -0,0 +1,7 @@
+To create your own check
+ - Copy the example directory which is inside modules
+ - Give your module a name
+ - Add the name of your directory to __all_tests__ in
+ lib/bittest/__init__.py
+
+Now have fun to write a clever test!
diff --git a/doc/README b/doc/README
new file mode 100644
index 0000000..642628e
--- /dev/null
+++ b/doc/README
@@ -0,0 +1,24 @@
+Bitbake QA will hold Quality Assurance Resources:
+ The primary user will be OpenEmbedded but it is useful
+for any other user bitbake as well.
+
+layout of the bitbake_qa module:
+conf/
+ It contains example configurations used to run tests
+with specified parameters (for overrides)
+
+doc/
+ This directory
+
+modules/module_name/
+ QA modules doing the actual tests
+
+
+I hope to offer the following tests soon:
+
+source_checker - It will check if the sources can still be fetched
+ and generates reports
+patch_checker - It will check if the patches still applies
+doc_checker - It will check if all variables have a documentation
+content_checker - It will check for common misusage in variables
+depends_checker - Check if native packages RDEPEND on non-native packages