sockets - Test harness software for networking failures -


During integration testing it is important to ensure that to ensure the different types of low-level networking failure It is necessary that these components are handled properly.

  • Connection refused
  • Never send any data with Remote and SEN / ACK Remote and Answers
  • Remote and only sends reset packets
  • The connection is established, but does not accept remote and packet, which causes endless re-launch

further .

This would be useful for simulating such failures for integration testing with web services, database calls etc.

Is this device a specific device (i.e. socket-level failures)? For example, there is a possibility that it will be a useless server that exhibits different types of failures on different ports.

Edit: After some additional research, it seems that it is possible to handle such a thing by using a firewall. For example, iptables has some options Which allows you to match packets (either randomly based on some configurable probability or on the basis of each NNT-packet) and then release them. So I am thinking that we can establish our "dirty server" with the firewall rules configured on a port-by-port basis so that we can check our apps. I would be interested to hear ideas about this approach.

Take a look at this.


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -