Good Testing Practices

Asked

Viewed 885 times

1

What are the best practices when it comes to software testing regarding file entry and output? Is there any effective way adopted in the market? It is good to come with some prior knowledge, or it is better to do the test taking the role of the user himself, without knowing how the system will react?

testing

  • This includes automated testing?

  • Clarissa Lippi try to clarify what you want with the question, I leave an alternative: "What are the types of software tests that can be done regarding the input and output of files?". If that’s really your question.

1 answer

3

There are several types of testing you can do:

  • Unit test: Testing at a component or class level. It is the test whose objective is a "piece of code". Example: Test your write methods and recover a file.
  • Performance test: Checks whether the response time is the desired one for the application’s time of use. Example: Test whether the response time while recording and recovering a file is satisfactory.
  • Cargo Test: Checks the operation of the application with the use of a large number of simultaneous users. Example: Test performance when multiple users record and/or recover files simultaneously.
  • Volume Test: Test the amount of data involved (can be a small, medium, large, or very large file).
  • Functional test: Test functional requirements, functions and use cases. Example: Test whether the application does what it should do when the user writes/recovers the file.
  • Interface Test: Checks whether the navigability and objectives of the screen where the user will record/recover a file on the system, work as specified and best suit the user.

Another issue that may be important is the security to save those files. Example: Test access in case user needs to save/recover this file in an X directory.

Browser other questions tagged testing

You are not signed in. Login or sign up in order to post.