Difference between revisions of "QA/BVT"
Phoenixwang (Talk | contribs) (Created page with " Framework How to run BVT BVT report BVT case description How to dev new cases Revision Platfrom Volunteer Status Task-id") |
Phoenixwang (Talk | contribs) |
||
Line 3: | Line 3: | ||
How to run BVT | How to run BVT | ||
− | + | [[http://wiki.openoffice.org/wiki/QA/test_automation_guide]] | |
+ | Run BVT test via Command | ||
BVT report | BVT report | ||
+ | |||
BVT case description | BVT case description | ||
Line 11: | Line 13: | ||
Revision Platfrom Volunteer Status Task-id | Revision Platfrom Volunteer Status Task-id | ||
+ | |||
+ | |||
+ | |||
+ | == Getting started with command line == | ||
+ | |||
+ | === Prerequisites === | ||
+ | *JDK: [http://java.sun.com/j2se/1.5/ JDK 1.5], [http://java.sun.com/javase/6/ JDK 1.6] or above.<br /> | ||
+ | *Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above. | ||
+ | *JUnit: [https://github.com/KentBeck/junit/downloads JUnit 4.10] or above. For lazy people, if internet is available, it can be automatically installed during testing. | ||
+ | |||
+ | === Run testing === | ||
+ | '''As a developer, how to run testing against an OpenOffice built by me?''' <br /> | ||
+ | It's easy for developers to run testing after building OpenOffice. One thing you need to do is to make sure you run the commands in the build environment. The script will automatically install your build and then start testing. e.g. | ||
+ | <source lang="bash"> | ||
+ | cd main | ||
+ | source MacOSXX86Env.Set.sh | ||
+ | cd ../test && ant | ||
+ | </source> | ||
+ | |||
+ | '''As a normal user, how to run testing against an installed OpenOffice?'''<br /> | ||
+ | Firstly compile the project with the command under test module. | ||
+ | <source lang="bash"> | ||
+ | ant -Dopenoffice.home="OpenOffice installation directory" compile | ||
+ | </source> | ||
+ | Then start testing with the command "run". | ||
+ | e.g. Run all test classes under package bvt | ||
+ | <source lang="bash"> | ||
+ | run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tp bvt | ||
+ | </source> | ||
+ | e.g. Run the given test classes | ||
+ | <source lang="bash"> | ||
+ | run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc bvt.gui.BasicFunctionTest | ||
+ | </source> | ||
+ | |||
+ | ''' 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.<br /> | ||
+ | [[File:test_automation_report.png]]<br /> | ||
+ | |||
+ | Special stuff in the output directory. | ||
+ | result.xml: Test result in HTML. | ||
+ | result.html: Test result in XML. | ||
+ | screenshot/: Screenshot pictures when test assert is failed. |
Revision as of 08:13, 26 March 2013
Framework
How to run BVT [[1]] Run BVT test via Command BVT report
BVT case description
How to dev new cases
Revision Platfrom Volunteer Status Task-id
Getting started with command line
Prerequisites
- 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.
Run testing
As a developer, how to run testing against an OpenOffice built by me?
It's easy for developers to run testing after building OpenOffice. One thing you need to do is to make sure you run the commands in the build environment. The script will automatically install your build and then start testing. e.g.
cd main source MacOSXX86Env.Set.sh cd ../test && ant
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.
File:Test automation report.png
Special stuff in the output directory.
result.xml: Test result in HTML. result.html: Test result in XML. screenshot/: Screenshot pictures when test assert is failed.