Difference between revisions of "QA/BVT"

From Apache OpenOffice Wiki
< QA
Jump to: navigation, search
Line 6: Line 6:
 
}}
 
}}
  
=How to run BVT=
+
= Prerequisites =
==Install SVN Client==
+
==Platform==
On Windows:
+
Test machine with OS in below list:
Download and Install TortoiseSVN as SVN Client to checkout sourcecode.<br/>
+
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.<br/>
 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html]<br/>
 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html]<br/>
 
 
== Getting the source code ==
 
Anyone can checkout source code from our Subversion repository. Run the following command.
 
<source lang="bash">
 
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test
 
</source>
 
If you are not familiar with Subversion, see our [http://incubator.apache.org/openofficeorg/svn-basics.html Subversion Basics] for more information.
 
 
== 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 />
 
*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.
 
*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.
 
*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.
 +
==Soft Skills==
 +
Basic skills about Windows Command line, Linux/Mac Terminal
  
=== 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>
 
  
 +
=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?'''<br />
 
'''As a normal user, how to run testing against an installed OpenOffice?'''<br />
 
Firstly compile the project with the command under test module.
 
Firstly compile the project with the command under test module.
<source lang="bash">
+
ant -Dopenoffice.home="OpenOffice installation directory" compile
ant -Dopenoffice.home="OpenOffice installation directory" compile
+
</source>
+
 
Then start testing with the command "run".  
 
Then start testing with the command "run".  
 
e.g. Run all test classes under package bvt
 
e.g. Run all test classes under package bvt
<source lang="bash">
+
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tp bvt
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tp bvt
+
</source>
+
 
e.g. Run the given test classes
 
e.g. Run the given test classes
<source lang="bash">
+
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc bvt.gui.BasicFunctionTest
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc bvt.gui.BasicFunctionTest
+
 
</source>
+
 
 
''' Where to get the testing result? '''
 
''' Where to get the testing result? '''
  
Line 69: Line 55:
 
}}
 
}}
  
{{Template:Documentation/Note| '''Download source code on Windows?'''<br />
 
Download and Install TortoiseSVN as SVN Client to checkout sourcecode.<br/>
 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html]
 
}}
 
  
==Reference==
+
=Reference=
 
:[http://wiki.openoffice.org/wiki/QA/test_automation_guide Test Automation Guide]
 
:[http://wiki.openoffice.org/wiki/QA/test_automation_guide Test Automation Guide]
 
:[http://wiki.openoffice.org/wiki/QA/BVT_Report BVT Report]
 
:[http://wiki.openoffice.org/wiki/QA/BVT_Report BVT Report]

Revision as of 08:13, 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.

Template:Documentation/Tip

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

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 HTML. 
result.html: Test result in XML.
screenshot/: Screenshot pictures when test assert is failed.

FAQ

Template:Documentation/Note


Reference

Test Automation Guide
BVT Report
Personal tools