action #1309

Create Perl sandbox for the tests (Safe module)

Added by aplanas about 6 years ago. Updated 6 months ago.

Status:ResolvedStart date:27/01/2014
Priority:NormalDue date:
Assignee:okurz% Done:


Category:Feature requests
Target version:QA - future


If we accept test programs from external contributors we need a way to sandbox the code, and avoid unwanted side effect, like accessing the full system from the test.

An alternative for this is the creation of a DSL language to write the test.


#1 Updated by aplanas about 6 years ago

  • Subject changed from Create Perl sandbox for the tests (Safe module to Create Perl sandbox for the tests (Safe module)

#2 Updated by ancorgs almost 6 years ago

  • Target version set to future

#3 Updated by coolo over 5 years ago

  • Category set to 138

#4 Updated by RBrownSUSE over 4 years ago

  • Category changed from 138 to Feature requests

#5 Updated by okurz about 4 years ago

How about a slight alternative to this to check for system access in a test, e.g. if certain calls are made, the tests of PRs fail?

#6 Updated by okurz over 3 years ago

  • Status changed from New to Rejected

no one cares

#7 Updated by oholecek over 3 years ago

  • Status changed from Rejected to New

Not that no one cares. This is still a valid and important topic and after my testapi decouple is (finally) done this will be much easier to accomplish.

#8 Updated by szarate over 3 years ago

A possible integration of Devel::REPL could help... and as for the DSL, we could use gherkin format maybe (GoS?)...

#9 Updated by oholecek over 3 years ago

Since my work on testapi involve doing testapi calls through socket my idea for this is to execute tests in complete container based sandbox - limited fs, net?, hw resources access and so on. Just passing the socket should be enough to interact with testapi and thus SUT. Fot this there is still TODO how QAM interacts with backend directly in some of their tests.

Since testapi will be accessible through socket we can create binding in any language we want quite easily. But that's for different issue and time.

#10 Updated by okurz over 1 year ago

  • Target version changed from future to future

#11 Updated by okurz 6 months ago

  • Status changed from New to Resolved
  • Assignee set to okurz

I consider this sufficiently covered with our use of apparmor.

Also available in: Atom PDF