Objective: To be able to run more than 10 browsers and using multiple machines(Server1,2).
Docker Swarm requires few ports to be open for it to work. These are : –
-TCP port 2377. This port is used for communication between the nodes of a Docker Swarm or cluster. It only needs to be opened on manager nodes.
-TCP and UDP port 7946 for communication among nodes (container network discovery).
-UDP port 4789 for overlay network traffic (container ingress networking).
First install docker on all 2 machines.eg Server 1,2
Then add the ubuntu user to the docker group, so we don’t need to use sudo everytime we use the docker command
sudo usermod-aG docker ubuntu
On Server 1
docker swarm init--advertise-addr=82.66.x.x-Here82.66.x.xisthe public IP of the machine.
Now docker swarm is ready and nodes can connect to it, ssh into the Server 2 grid machine and run the following command On Server 2
docker swarm join--token SWMTKN-1-..........
Run the following command to deploy docker swarm — https://goo.gl/Fsq6fu : –
docker stack deploy--compose-filegrid.yamlfoobar
To view the status of the docker swarm : –
docker stack psfoobar
To shut down docker swarm
docker stack rmfoobar
To debug a specific container
To leave docker swarm, type the following command both on manager node and worker node
Why we choose this.
Normal Jasmine reporter is very simple and not much screenshot friendly. This plugin has following features which makes it more suitable for Reporting for Protractor / Angular based Projects.
Get attached Screenshots
Selenium & Browser’s Logs (only for Chrome)
Full Stack Trace (with suspected line highlight)
Screenshot only on failed spec.
Filters (can display only Passed/Failed/Pending/Has Browser Logs)
Details (Browser/Session ID/OS)
Duration time for test cases (only Jasmine2)
Note – If you are using the jasmine 2(Jasmine 1.x: No longer supported), It can be integrated very easily with two steps.
As you all know that the General Data Protection Regulation (GDPR) is coming in Few days and We can’t ignore it.
General Data Protection Regulation (GDPR) is one regulation that any development teams can’t ignore. We have to be compliant with these regulations.
If you are collecting user information, any personal Information like name, email, phone and other in your databases and putting them in your staging environment for Testing purpose or Production like Test data. You need to read below point to save it for GDPR. It would be better to remove or delete/mask it completely.
What is GDPR?
The General Data Protection Regulation regulates how companies protect EU residents’ personal data. It goes into effect on May 25, 2018. For every breach after that point, companies could incur fines of up to 4 percent of the company’s annual global turnover or €20 million (whichever is greater). Wow.
How to stay away from GDPR, Testers point of view?
Don’t Use Production’s Copy of Test-data if it includes some Sensitive or personal information.
Use Mocked or Dummy data sometimes we can them synthetically generate the test data while Testing in Staging.
If you have used the Production’s data in Staging and it is breached make sure you convey to respective authority.
You can use extract and mask technique, which basically has Production like a database but full masked and does not make any sense in real life.
So In a nutshell, Make sure as a tester in your Testing Procedure is compliant too to GDPR along with your Company.
Thanks for reading! If you enjoyed it, hit that share button below. Would mean a lot to me and it helps other people see the story.