Interface testing is actually difficult to define, I understand that interface testing is not a white box test, but also for the Heihe test. Later, with our development chat, he said that the interface test is actually a part of the white box.
Later, with one Ali Big data chat, he said the interface test belongs to (black box test) Functional testing, OK, no matter what test. Interface is generally to look at the input and output, if it is a simple interface test, no
Data depends on the situation is relatively simple, as for the data can be batch from the configuration file or Excel to take the line, loop call, but remember to return the results of the validation of the accuracy, so the data to be grouped, such as
A batch of data belongs to the correct data, a batch of data belonging to the exception, how to subdivide the data group, depends on the return status of your interface. If it is a more complex interface, such as a refund that was previously mentioned, to
There's a lot of data to rely on, and if it's me, I'll do it----
1. Create data through the interface, but conditional, if you call a few interfaces to create the data you want, then this way is nothing but a very
Fast, and dynamic parameterization, how much, a cycle of things. If it's a complicated situation, unless the company gives you a lot of manpower and resources to write scripts, otherwise, there really is no need to engage
2. Database read, but conditional, if your interface is experience to regression test, then you can write a number of SQL random query out of the eligible records, but generally I rarely use JDBC, is to write a page, direct query, back to the foreground, such as if
Other people need other data, I just need to maintain a simple platform, it can randomly query out any of the data I want, this interface is more convenient
3. Data import into the library----to ensure a clean system, the data needed to write to the library, and then the data has been exported as SQL, if you want to run SQL file directly, the data you want to have, the interface can be arbitrarily called, but this also has a certain problem, often to
Maintenance of SQL, the solution is to deploy another set of clean test environment, change the application configuration to the new library, general development are maintenance applications, rarely change the library, I think of these, we can according to their own needs dynamic adjustment, but the basic is so