Projects/Nepomuk/TestEnvironment: Difference between revisions

    From KDE TechBase
    (Created page with "Testing changes in Nepomuk can be a little hard cause it often requires the entire Nepomuk stack to be running. This includes all the Nepomuk Services along with the virtuoso ...")
     
    (Prepare for translation)
    Line 1: Line 1:
    Testing changes in Nepomuk can be a little hard cause 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.
    <languages />
    <translate>
     
    == 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.
    That is where the Nepomuk Test Environment comes in.
    Line 5: Line 10:
    It is currently present in nepomuk-core.
    It is currently present in nepomuk-core.


    = Usage =
    == Usage ==
    <syntaxhighlight lang="bash">
    <syntaxhighlight lang="bash">
    $ cd nepomuk-core/autotests/lib/tools/
    $ cd nepomuk-core/autotests/lib/tools/
    Line 15: Line 20:
    $ source nepomuk-sandbox-end.sh
    $ source nepomuk-sandbox-end.sh
    </syntaxhighlight>
    </syntaxhighlight>
    [[Category:Documentation]]
    [[Category:Development]]
    [[Category:Tutorials]]
    </translate>

    Revision as of 10:14, 14 December 2012


    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.

    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