Hot answers tagged

3

There are several tools available over the web but my favourite one is Octopus Deploy, because after a relative simple configuration it can deploy your build, setting up automatically your testing environment. The configuration can be done through a user friendly interface and, it's important at least for me, it's free for a limited number of "tentacles" ...


3

Generally you should think of tests as doing Setup Execution Given X, When Y happens, Then expect Z Teardown This actually occurs at two (or more) levels: Entire test suite Certain files, constants, database commands, etc. need to be run before the entire test suite. Often there is no 'tear-down' in this area. Each test Each test should also have ...


2

Maybe setting up a VM of your environment is a solution you can look into. So as part of running your tests, you spin up a VM (which has everything where it should be) then run your suite of tests within it.


2

I prefer to use separate tools for deployment/configuration and running tests, because a tool that focuses on one thing will do better than a tool that tries to do everything. There are innumerable tools for automating deployments, where a deployment includes installing binaries and configuration files. Some popular ones include Puppet and Ansible. For ...


1

What do you look for in a staging environment as a QA professional[?] If at all possible your 'staging' environment will be analogous to your Production environments. The web server would be hosted by the same provider and using the same Apache or IIS version. The SQL server would be the same too. You might request a nightly replication so you have ...



Only top voted, non community-wiki answers of a minimum length are eligible