To provide clarity in addressing your inquiries, I will assign labels to each of the commands you mentioned:
- Executing tests:
npm test
- Starting Selenium:
npm start selenium
- Running your app:
npm start app
Questions/Answers:
When running locally, these commands require 3 terminals simultaneously - is there a way to achieve this on CircleCI?
Absolutely. Simply initiate a process with the background parameter set to true
For instance, starting Selenium in the background can be done as follows:
- run:
name: Start Selenium in background
command: |
npm start selenium
background: true
Before utilizing a process but after initiating it, ensure that the process is ready and running on the designated port.
- run:
name: Waiting for Selenium server to be ready
command: |
for i in `seq 1 10`;
do
nc -z localhost 4444 && echo Success && exit 0
echo -n .
sleep 1
done
echo Failed waiting for Selenium && exit
Note that by replacing 4444 in the above command, you can wait for a process on a different port.
How do I determine when p4444 and p80 are prepared for testing, or how can they be terminated once the tests are completed?
Your CircleCi instructions might resemble the following:
- run:
name: Start Selenium in background
command: |
npm start selenium
background: true
- run:
name: Start App in background
command: |
npm start app
background: true
- run:
name: Waiting for Selenium server to be ready
command: |
for i in `seq 1 10`;
do
nc -z localhost 4444 && echo Success && exit 0
echo -n .
sleep 1
done
echo Failed waiting for Selenium && exit
- run:
name: Waiting for App server to be ready
command: |
for i in `seq 1 10`;
do
nc -z localhost 80 && echo Success && exit 0
echo -n .
sleep 1
done
echo Failed waiting for Selenium && exit
- run:
name: Run Tests
command: |
npm test
You raised a separate concern about halting the processes on ports 4444 and 80 once the tests conclude. Generally, this isn't necessary as upon finishing the test job, the container will be removed and the auxiliary applications will cease operation.
However, if you wish to halt those processes to proceed with additional job steps, you can execute kill commands (further details available upon request).
Is my issue attributed to Docker or CircleCI?
It appears to be more of a challenge in comprehending how to execute a sequence of commands within CircleCi.
By adhering to the aforementioned steps, you should be able to accomplish your objectives successfully.