3 added 194 characters in body
source | link

I am doing GUI tests for my network application and I'm wondering if I should stub out mock responses, or if it's OK to keep using the network for the GUI tests.

It seems to me the main benefits of stubbing the responses are:

  1. Speed
  2. Robustness - no false errors because of network problems

And the cons are:

  1. Server interaction (real world) - doesn't test this
  2. Time to implement and maintain mock up (for a large application)

Are the pros worth the cons? Are GUI tests about testing the actual application and if it runs for a real user connected to the server, or are they more similar to regular unit tests, but for the GUI - are they just trying to test the GUI and don't care about server interaction.

EDIT

This question specifically relates to GUI tests, not regular unit tests, and is questioning the value of stubbing mock responses in the GUI tests vs. using the server normally.

I am doing GUI tests for my network application and I'm wondering if I should stub out mock responses, or if it's OK to keep using the network for the GUI tests.

It seems to me the main benefits of stubbing the responses are:

  1. Speed
  2. Robustness - no false errors because of network problems

And the cons are:

  1. Server interaction (real world) - doesn't test this
  2. Time to implement and maintain mock up (for a large application)

Are the pros worth the cons? Are GUI tests about testing the actual application and if it runs for a real user connected to the server, or are they more similar to regular unit tests, but for the GUI - are they just trying to test the GUI and don't care about server interaction.

I am doing GUI tests for my network application and I'm wondering if I should stub out mock responses, or if it's OK to keep using the network for the GUI tests.

It seems to me the main benefits of stubbing the responses are:

  1. Speed
  2. Robustness - no false errors because of network problems

And the cons are:

  1. Server interaction (real world) - doesn't test this
  2. Time to implement and maintain mock up (for a large application)

Are the pros worth the cons? Are GUI tests about testing the actual application and if it runs for a real user connected to the server, or are they more similar to regular unit tests, but for the GUI - are they just trying to test the GUI and don't care about server interaction.

EDIT

This question specifically relates to GUI tests, not regular unit tests, and is questioning the value of stubbing mock responses in the GUI tests vs. using the server normally.

2 meta details removed
source | link

I am doing GUI tests for my network application and I'm wondering if I should stub out mock responses, or if it's OK to keep using the network for the GUI tests.

It seems to me the main benefits of stubbing the responses are:

  1. Speed
  2. Robustness - no false errors because of network problems

And the cons are:

  1. Server interaction (real world) - doesn't test this
  2. Time to implement and maintain mock up (for a large application)

Are the pros worth the cons? Are GUI tests about testing the actual application and if it runs for a real user connected to the server, or are they more similar to regular unit tests, but for the GUI - are they just trying to test the GUI and don't care about server interaction.

(I wasn't sure where to post this, or how to phrase it. Migrating to a different exchange or edits/suggestions to the post are greatly appreciated.)

I am doing GUI tests for my network application and I'm wondering if I should stub out mock responses, or if it's OK to keep using the network for the GUI tests.

It seems to me the main benefits of stubbing the responses are:

  1. Speed
  2. Robustness - no false errors because of network problems

And the cons are:

  1. Server interaction (real world) - doesn't test this
  2. Time to implement and maintain mock up (for a large application)

Are the pros worth the cons? Are GUI tests about testing the actual application and if it runs for a real user connected to the server, or are they more similar to regular unit tests, but for the GUI - are they just trying to test the GUI and don't care about server interaction.

(I wasn't sure where to post this, or how to phrase it. Migrating to a different exchange or edits/suggestions to the post are greatly appreciated.)

I am doing GUI tests for my network application and I'm wondering if I should stub out mock responses, or if it's OK to keep using the network for the GUI tests.

It seems to me the main benefits of stubbing the responses are:

  1. Speed
  2. Robustness - no false errors because of network problems

And the cons are:

  1. Server interaction (real world) - doesn't test this
  2. Time to implement and maintain mock up (for a large application)

Are the pros worth the cons? Are GUI tests about testing the actual application and if it runs for a real user connected to the server, or are they more similar to regular unit tests, but for the GUI - are they just trying to test the GUI and don't care about server interaction.

1
source | link

GUI Testing With Network

I am doing GUI tests for my network application and I'm wondering if I should stub out mock responses, or if it's OK to keep using the network for the GUI tests.

It seems to me the main benefits of stubbing the responses are:

  1. Speed
  2. Robustness - no false errors because of network problems

And the cons are:

  1. Server interaction (real world) - doesn't test this
  2. Time to implement and maintain mock up (for a large application)

Are the pros worth the cons? Are GUI tests about testing the actual application and if it runs for a real user connected to the server, or are they more similar to regular unit tests, but for the GUI - are they just trying to test the GUI and don't care about server interaction.

(I wasn't sure where to post this, or how to phrase it. Migrating to a different exchange or edits/suggestions to the post are greatly appreciated.)