Set up Testing for a Static Application

  • In Applications from the left menu bar, click Add new application

  • Enter Application Name

  • Enter Description

  • Choose Team

  • Enter an estimate Number of Users

  • Choose Internal or not

  • Choose Authenticated or not

  • Leave Down Time Cost Per Day and Restoration Cost as defaults

  • Click Save



Your new Application should now be on the Applications list.


Static Application test 1

  • Click Add Version on your new Application to add a version pipeline

Static Application test 2

  • Enter Version Name

  • Choose Source Code Origin

  • Go to your project (if project is in GitHub, see image for how to copy the URL)

Static Application test 3

  • Paste URL into Git Address

  • Leave Branch Name as default

  • Under SCM Authentication, choose your Authentication Type (if private repository, select ‘Username and Password’ option)
    1. For Username, enter your email address you use on GitHub
    2. For Password, enter your GitHub token

  • Click Test to make sure we are able to access the code line

  • Click Save and Continue
  • Your Application is now set up!
  • Find your Application in the table, expand to see the Version you've just created.
  • Click the Test Now button, find the Uleska Code Scan toolkit, and click Start Scan


When the test is finished, you will see a green tick

  • Click Show Results button to view results

Static Application test 7

  • To view False Positives or Duplicates, click on Bulk Operations

Static Application test 9