Jumpscale Testing

[rkhamis]

This storycard covers the most important topics to be tested in jumpscale

To be developed on branch [development_jumpscale_testing]

• Installations

  • in system installation
  • docker installation
  • need to find a service that allows us to automate tests on OSX

• Security Layer

  • NACL and configmanager

    • with sshkey
    • without sshkey

  • functionality

  • should be secure, meaning data that is encrypted should be verified to be encrypted unless being retrieved through the nacl module

  • should be able to set new config

  • should be able to get config

  • should be able to delete config

  • should be able to recover config if provided with seed

  • should be able to export data

  • should be able to import data

  • Core

  • baseclasses (see:https://github.com/threefoldtech/jumpscaleX/blob/development_jumpscale/docs/Internals/baseclasses/readme.md)

  • Data Layer

  • schemas

    • already we have some tests, but need to be extended with more scenarios

  • BCDB

    • already we have some tests, but need to be extended with more scenarios
    • performance tests

• SALs

  • behavioral testing

  • start with:

    • fs
    • rsync
    • process

  • Tools (not high priority)

  • behavioral/unit testing

  • TFChain

  • more tests for reservation flow

  • Clients

  • some will be mocked, some not.

  • start with:

    • Servers

  • some will be mocked, some not.

  • start with:

    • digitalocean
    • github
    • ssh
    • sshkey
    • zdb
    • zero_hub
    • zero_os

  • Servers:

  • start with:

    • tmux
    • corex
    • startcmd
    • zdb

  • Builders

  • we already have the tests

  • DigitalMe

  • server rack

  • Actors

    • Behavioral. Scenario could be:
      • create a test actor with schema in and schema out
      • load test actor
      • use redis protocl to verify
    • jsclient (see: https://github.com/threefoldtech/digitalmeX/blob/development/docs/webserver/websocket-gedis.md)
    • gundbjs integration

[rkhamis]

Architecture to run tests:

Trigger on PR is exactly the same but without the builder tests.