-
Notifications
You must be signed in to change notification settings - Fork 394
Remote Containers Smoke Test
Christof Marti edited this page May 28, 2019
·
6 revisions
Instructions on how to smoke-test the Remote Containers extension before a release.
- Open an empty folder.
- Create a
Dockerfile:
FROM node:lts- Run the
Reopen Folder in Containercommand. - Pick
From 'Dockerfile'. - Wait for container to start and Code to connect to it.
- Create a
server.js:
require('http')
.createServer((req, res) => {
res.end('Hello!');
})
.listen(0);- Check IntelliSense and hovers work.
- Place a breakpoint and F5.
- Run the
Forward Port from Container...command to forward the port and open the browser on it. - Check breakpoint is hit.
- Add
RUN touch /foobarto the end of theDockerfile. - Reload window, check it reconnects to the container and
/foobardoes not exist. - Run the
Rebuild Containercommand, check it reconnects to a container and/foobardoes exist.
- Open an empty folder.
- Run the
Reopen Folder in Containercommand. - Pick
Node.js & Mongo DB. - Wait for containers to start and Code to connect to one.
- Verify the ESLint extension is installed.
- Add
RUN touch /foobarto the end of theDockerfile. - Reload window, check it reconnects to the container and
/foobardoes not exist. - Run the
Rebuild Containercommand, check it reconnects to a container and/foobardoes exist.
- Open empty local window.
- Install Docker extension.
- Run
docker run -d debian sleep infinityform the terminal. - In the Docker viewlet right-click the
debiancontainer and runAttach Visual Studio Code. - In the new window open some folder in the container and check the window reconnects to the container with that folder open.
Project Management
Help
Smoke Tests