Difference between revisions of "Projects/Nepomuk/TestEnvironment"

Jump to: navigation, search
(Marked this version for translation)
 
Line 2: Line 2:
 
<translate>
 
<translate>
  
== Testing ==
+
== Testing == <!--T:1-->
  
 +
<!--T:2-->
 
Testing changes in '''Nepomuk''' can be a little hard because it often requires the entire Nepomuk stack to be running. This includes all the Nepomuk Services along with the virtuoso database. Additionally, one often might want to test some risky changes, and not mess around with your own precious database. In those cases, it would be nice to have a virtual Nepomuk environment to run these tests on.
 
Testing changes in '''Nepomuk''' can be a little hard because it often requires the entire Nepomuk stack to be running. This includes all the Nepomuk Services along with the virtuoso database. Additionally, one often might want to test some risky changes, and not mess around with your own precious database. In those cases, it would be nice to have a virtual Nepomuk environment to run these tests on.
  
 +
<!--T:3-->
 
That is where the Nepomuk Test Environment comes in.
 
That is where the Nepomuk Test Environment comes in.
  
 +
<!--T:4-->
 
It is currently present in nepomuk-core.
 
It is currently present in nepomuk-core.
  
== Usage ==
+
== Usage == <!--T:5-->
  
 +
<!--T:6-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
$ cd nepomuk-core/autotests/lib/tools/
 
$ cd nepomuk-core/autotests/lib/tools/
Line 22: Line 26:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 +
<!--T:7-->
 
[[Category:Documentation]]
 
[[Category:Documentation]]
 
[[Category:Development]]
 
[[Category:Development]]
 
[[Category:Tutorials]]
 
[[Category:Tutorials]]
 
</translate>
 
</translate>

Latest revision as of 11:08, 24 December 2012

Other languages:English 100%

[edit] Testing

Testing changes in Nepomuk can be a little hard because it often requires the entire Nepomuk stack to be running. This includes all the Nepomuk Services along with the virtuoso database. Additionally, one often might want to test some risky changes, and not mess around with your own precious database. In those cases, it would be nice to have a virtual Nepomuk environment to run these tests on.

That is where the Nepomuk Test Environment comes in.

It is currently present in nepomuk-core.

[edit] Usage

$ cd nepomuk-core/autotests/lib/tools/
$ cb # Change to the build directory
$ source nepomuk-sandbox-begin.sh
$
$ # A mock KDE Nepomuk session will be started
$ # Here you can run whatever tests you want
$ source nepomuk-sandbox-end.sh

This page was last modified on 24 December 2012, at 11:08. This page has been accessed 1,305 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal