Difference between revisions of "QA/BVT"
Phoenixwang (talk | contribs) |
Phoenixwang (talk | contribs) |
||
Line 41: | Line 41: | ||
result.html: Test result in HTML. Collect all case's result, to report as HTML. | result.html: Test result in HTML. Collect all case's result, to report as HTML. | ||
screenshot/: Screenshot pictures when test assert is failed. | screenshot/: Screenshot pictures when test assert is failed. | ||
− | ==Process | + | |
− | 1 | + | ==FAQ== |
− | 2 | + | |
+ | {{Template:Documentation/Note| '''What is openoffice.home?'''<br /> | ||
+ | The default installation directory of Apache OpenOffice:<br/> | ||
+ | Mac OS X: "''/Applications/OpenOffice.org.app/Contents"''<br /> | ||
+ | Linux: "''/opt/openoffice.org3''"<br /> | ||
+ | Windows: "''C:/Program Files/OpenOffice.org 3''"<br /> | ||
+ | Windows 64b: "''C:/Program Files (x86)/OpenOffice.org 3''" | ||
+ | }} | ||
+ | {{Template:Documentation/Note| '''Can I do other operations when BVT is running'''<br /> | ||
+ | For BVT cases wrote via GUI(Graphical User Interface) not UNO interface, little display offset may impact test result. So not do other operations when BVT is running. | ||
+ | |||
+ | }} | ||
+ | |||
+ | =Process= | ||
+ | 1)Create task on Bugzilla to track BVT execution task. [[https://issues.apache.org/ooo/ Bugzilla]]<br/> | ||
+ | 2)Track your execution task on [[http://wiki.openoffice.org/w/index.php?title=QA/BVT_Report BVT Report ]]<br/> | ||
* Platform: Platform which you can run BVT.<br/> | * Platform: Platform which you can run BVT.<br/> | ||
* Volunteer: Volunteer's name to take this execution task.<br/> | * Volunteer: Volunteer's name to take this execution task.<br/> | ||
Line 101: | Line 116: | ||
| | | | ||
|} | |} | ||
− | 3 | + | 3)Update your execution result on "Status" column, and add detail HTML result in new link(Record link on [[http://wiki.openoffice.org/w/index.php?title=QA/BVT_Report BVT Report ]] ).<br/> |
− | 4 | + | 4)If have fail/error case, you need check it manually. To confirm it's exact a bug. (For some BVT cases write via GUI(Graphical User Interface), it have some offset).<br/> |
In this step, you need study to read cases. [[http://wiki.openoffice.org/wiki/QA/dev_gui_testing Dev GUI Test]] [[http://wiki.openoffice.org/wiki/QA/vclauto/A_step_by_step_example A step by step example]]<br/> | In this step, you need study to read cases. [[http://wiki.openoffice.org/wiki/QA/dev_gui_testing Dev GUI Test]] [[http://wiki.openoffice.org/wiki/QA/vclauto/A_step_by_step_example A step by step example]]<br/> | ||
− | 5 | + | 5)If there is a defect, you can open it on [[https://issues.apache.org/ooo/ Bugzilla]],select specific edit as it's catagory<br/> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=Reference= | =Reference= | ||
− | + | *[http://wiki.openoffice.org/wiki/QA/test_automation_guide Test Automation Guide] | |
− | + | *[http://wiki.openoffice.org/wiki/QA/BVT_Report BVT Report] |
Revision as of 09:37, 28 March 2013
Introduction
Build Verification Testing, BVT for short, is a set of tests that run on new build to verify that whether the build is testable or not. It is done prior to its release to test team for further testing. This testing is done for Build Validation and Build Acceptance.
Prerequisites
Platform
Test machine with OS in below list: WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac
Environment tools
- SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode.
http://tortoisesvn.net/downloads.html
- JDK: JDK 1.5, JDK 1.6 or above.
- Ant: Apache Ant 1.8.2 or above.
- JUnit: JUnit 4.10 or above. For lazy people, if internet is available, it can be automatically installed during testing.
Soft Skills
Basic skills about Windows Command line, Linux/Mac Terminal
How to run BVT
Getting the source code
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test
Run testing
As a normal user, how to run testing against an installed OpenOffice?
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run". e.g. Run all test classes under package bvt
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tp bvt
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc bvt.gui.BasicFunctionTest
Where to get the testing result?
By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/result.html" in your browser to see the testing report.
Special stuff in the output directory.
result.xml: Test result in XML. Every case's detail result, may include case error stack. result.html: Test result in HTML. Collect all case's result, to report as HTML. screenshot/: Screenshot pictures when test assert is failed.
FAQ
Template:Documentation/Note Template:Documentation/Note
Process
1)Create task on Bugzilla to track BVT execution task. [Bugzilla]
2)Track your execution task on [BVT Report ]
- Platform: Platform which you can run BVT.
- Volunteer: Volunteer's name to take this execution task.
- Revision: build version of AOO4.0
- Status: Pass/Fail
- Task ID:Task ID in Bugzilla.
Revision | Platform | Volunteer | Status | Task ID |
---|---|---|---|---|
WindowsXP | ||||
Windows7 32bit | ||||
Windows7 64bit | ||||
Ubuntu | ||||
Suse | ||||
Redhat | ||||
Mac |
3)Update your execution result on "Status" column, and add detail HTML result in new link(Record link on [BVT Report ] ).
4)If have fail/error case, you need check it manually. To confirm it's exact a bug. (For some BVT cases write via GUI(Graphical User Interface), it have some offset).
In this step, you need study to read cases. [Dev GUI Test] [A step by step example]
5)If there is a defect, you can open it on [Bugzilla],select specific edit as it's catagory