# Frequently Asked Questions
# Where are the ports used by Hypertest?
In the directory where Hypertest is installed, there is a
ht-ports-info.json file that contains the 3 ports:
- Logger Port: the port to which traffic is redirected
- HT Port: HT Port is the Dashboard port.
- Webhook port: not to be confused with the webhook in
WEBHOOK_BASE_URLin config params.
# What are "Primary" and "Candidate" versions?
The terms "Primary" and "Candidate" refer to two instances of your application that are different in terms of code commits i.e. Primary version would contain the code that is in production while the candidate version will contain the code that is supposed to go into production.
# Why do I need two different versions of my application deployed?
Hypertest works by performing a comparative analysis between the two versions of your application that are provided to it. Therefore, if identical application instances are provided to Hypertest, there won't be anything to compare.
# Do I have Hypertest run in a production environment? If not where does it run?
Hypertest does not need to be run in the production environment. The environment should be the one that receives the most traffic besides production will do. Just ensure that both the Primary and Candidate are in the same environment.
# Is it required to have both versions connected to the same database?
As of the time of this writing, it is absolutely necessary for both the applications to be connected to the same database.
# Is using nginx absolutely necessary?
No, any of the mirroring method will suffice, along with any other method that can redirect traffic to Hypertest.
# Why do the Primary and Candidate versions need to be in the same environment?
Having both instances in the same environment ensures that there are no differences on responses that are caused by different environment variables.
# Why do the Primary and Candidate versions need to be connected to the same database?
Using the same database ensures that both the application instances receive the same requests.
# Can Hypertest tell me how much of my application is covered?
Amount of coverage is unique to every test because the traffic varies. The amount of APIs covered can be found on the API coverage button while starting a new test, as well as within the test on the dashboard. However, to enable this feature you need to provide with OAS_DOC_PATH configuration parameter.
# Tests taking too long?
If your tests have a lot of requests in them, it is a good idea to increase the number of request runners via the "MAX_RUNNER_INSTANCES" parameter under "Configuration".