test apps in stepstone - dsandeep97/BiologyAnimation GitHub Wiki

  1. Download an app capable of establishing an FTP connection such as WinSCP or FileZilla . I used WinSCP, so this tutorial may have steps that won’t match exactly with other clients.
  2. Use the following credentials: Server/Host: futuredogter.com Username: lawano1 Password : H-8Uqp5Z In WinSCP, establishing a new session should look something like this:
  3. Once you are connected, you should see a directory that looks something similar to this but it should always contain a futuredogter.com directory. Now, navigate to the following path: futuredogter.com/stepstone/workArea/NIH-SEPA-1/activityLib/sample1
  4. This directory should contain three subdirectories titled “apps”, “json”, and “media”. Whenever you want to test out your standalone mini-app, upload the entire app contents into the /apps directory as a subdirectory. 16 Be sure your specific app folder contains an index.html file at the root as well as any necessary JavaScript, CSS, and even other HTML files. It has been advised by Daniel that you shouldn’t try to pull scripts externally, meaning any scripts you need to include for your app should be downloaded and included in your app’s folder.
  5. Once you’ve uploaded your app’s folder into the /apps directory, go into the /json directory. You should see multiple JSON files, one of which is titled draggybox40.json. To view your app in a StepStone testing environment, open draggybox40.json , and edit the launched app to be the title of your app’s folder. Remember, this folder must have an index.html file at the root.
  6. Now you’re ready to view your app in the testing environment. Visit the following link: http://www.futuredogter.com/stepstone/playerShell.php?org=CET&sys=public.Late 17 st&pool=TAMU-CET-1&resourceloc=www.futuredogter.com&resourceavatar=NIH-S EPA-1&resource=sample1&ppj=1_1_40
  7. At that link, you should see your app embedded into the frame. You can disregard the titles and whatnot, as your app has no control over the page and is only responsible for itself. You can use this testing environment to repeatedly launch your app and make small adjustments so that Daniel doesn’t have to reapply your app to production numerous times. Note that we had some loading and responsiveness issues in this environment when switching launched apps, so be sure to clear your browser’s cache if you experience these types of issues.