Ladder Trader Beta Testing

Beta Test Guide

Welcome to the EAS Ladder Trader beta testing team! Thank you for helping us improve our software. If you've never tested a software product before, don't worry—this guide will walk you through everything you need to know to get started. Your feedback is crucial for making sure our product is the best it can be, so let's dive in!

Testing requires tracking of issues in a logical and organized way. We have created a form to make recording and reporting of issues easier and more efficient. This is a Google form and will require that you log into your Google account to use it. If you do not want to use the form, you can send us a support ticket for each item you find and we'll record the bug for you. 

Beta Testing Form

Your form entries will be recorded on a Google sheet. You may access the Google sheet from the link below to see if a bug or issue you have found has already been recorded. If you are not sure if your issue is exactly the same as one already recorded, please add your issue to the list. We will sort them internally and attempt to recreate the issue. 

List of reported issues

Step 1: Install the Software

1. Download the software from the link provided in your invitation email. or HERE.
2. Follow these installation instructions: https://app.screencast.com/iXnraTwH5aE0W
   1. Close NinjaTrader
   2. Double click on the downloaded installation file.
   3. The installer will run. There is no indication that the installation is complete. It only takes a couple of seconds after you click the ok button to install.
3. If you encounter any issues while installing, take a screenshot or note the error message, and let us know by reporting it (see Step 4).

Step 2: Explore the Software

1. Familiarize yourself with the Ladder Traders main features. Use it as you would normally, even if you are not sure how everything works at first. Much of the available features should work very similarly to, or exactly like, NinjaTraders Static SuperDOM.
2. Test specific features listed in the testing tasks. Focus on the areas we need feedback on, but feel free to explore other parts too.

Example tasks:

• Create a new account.
• Navigate through different menus and settings.
• Try to perform specific actions (e.g., creating a document, using search, or customizing settings).

Step 3: Look for Bugs or Issues

1. While using the software, keep an eye out for anything that doesn’t seem to work correctly. A bug is any unexpected behavior like errors, crashes, or features not working as intended.
2. Some common issues to look out for:
   • Crashes: Does the software stop working unexpectedly?
   • User Interface Issues: Are buttons misaligned? Text hard to read?
   • Performance Problems: Is the software slow, laggy, or unresponsive at times?
   • Feature Malfunctions: Do certain functions not work as described or not at all?

Step 4: Report Bugs and Feedback

1. Reporting Bugs:
   • Use the built-in feedback tool (if available) or the provided form to submit issues.
   • Include as much detail as possible:
     • Description: Explain what happened.
     • Steps to reproduce: Describe how you encountered the issue so we can replicate it (e.g., “I clicked on the 'Save' button, and the software crashed”).
     • Screenshots or videos: These help us understand the issue better.
     • Device info: Tell us about your device (e.g., Windows or Mac, model, software version).
2. Provide Feedback:
   • If you like or dislike something, tell us why.
   • Suggest features you think would improve the product or mention areas that feel confusing or incomplete.

Step 5: Complete Testing Tasks

We may provide you with specific tasks to test, such as "Try logging in from a different device" or "Test the export feature." Please focus on these tasks during your testing and share your feedback based on your experience.

Step 6: Stay Updated

We'll send regular updates about new features or fixes that need testing. Please keep an eye on your email or communication channel for any instructions or changes.

Beta Testing Etiquette

• Be patient: Since this is a beta version, expect that there will be bugs and unfinished features.
• Be honest: Your feedback is valuable, whether it's positive or negative. We need both to improve the software.
• Be thorough: Don’t rush through the testing. Take your time to explore and provide detailed feedback.

Step 7: Wrap-Up

Once the testing period ends, we’ll ask you to complete a final survey to summarize your overall experience. Your insights will help us prioritize the most important improvements before the final release.

Support

If you run into any major problems that prevent you from continuing, please reach out to our support team via the contact information provided in your invitation email.

Thank you again for your time and contribution. Your feedback will help us deliver a polished and user-friendly product!

 BEGIN TESTING