Tag Info

New answers tagged

1

There must be some communication across the network between client and server. A Visual Studio Web Performance Test can be used to simulate one end of that communication and so apply load to the other end. A common performance test simulates many clients to see how the server behaves. To do this you need to generate the same communications as the client ...


1

I can see a few directions you could take with this situation: Break it up: You could build load tests for each phase - that is, you have one test that registers a user, has an administrator open the task list, modify the record, and send the email. The next test opens the link (since you know the format of the email and the link this is doable), adds ...


3

Like any other form of automated test, it depends on how you're invoking them and the environment you need to run. If you need a UI user session (which is the common setup) then you're probably not going to be packaging them with the unit tests. Some of the factors to consider are: CodedUI tests are slower than unit tests because they interact with the ...


3

If you have to support multiple versions for your software product I would keep the tests with in the same repository. Then the tests will version with the application itself. Which will make you able to run the tests for older versions with ease. Also you will want your developers to run and maintain the tests. For example when they need to change the ID ...


0

I've never done that, but, from my understanding, they are tests so they should go to where the unit tests are. Now, this might depend also how the tests can be run. My UI tests need to run on a PC/VM with a working UI user session, so there's no need/use in putting it together with the unit tests because these run on a CI server with no UI session ...



Top 50 recent answers are included