We use JUnit and Jest to perform the bulk of our automated test scenarios, with additional work with Apache JMeter for performance testing - for example, the Atlassian Data Center compliance testing is performed with JMeter. Jest provides testing for the React interfaces, which make up the backend of our App offerings. JUnit is used for Unit Testing our Server-based Apps. Mocha is another tool we use.
We use Microsoft Teams as our primary workplace collaboration tool. It enables our team to work remotely and still collaborate on projects - with integration to JIRA and Confluence, the tool enables us to create War Rooms when problems occur and also provides information-sharing capabilities. Replaced HipChat.
IntelliJ IDEA and Visual Studio Code are our primary Integrated Development Environments (IDEs). We generally work in Visual Studio Code when the codebase is relatively small and with the more feature complete IntelliJ IDEA when we need more advanced functionality - especially when working with Java Apps.
Docker is used to package up our applications with all of the parts they need, such as libraries and other dependencies, and enable us to ship it all out as one package. Our repositories hosted in AWS CodeCommit are automatically built by AWS CodeBuild on changes (resulting from Pull Requests being approved) and these are stored in the the EC2 Container Registry (ECR) before being approved for deployment to the Amazon EC2 Container Service in a zero-downtime, staged upgrade. We also provide development instances of our Apps, which are also hosted in Docker containers.
We use Amazon SES to provide the email services of our Cloud Apps - it provides a robust, stable service that we interface with to provide our customers' with timely notifications on actions - for example - in Approvals for Confluence we email the approvers when their approval is requested.