Charter 24 Explore textures API using different inputs to detect issues

Charter:

• Explore textures API using different inputs to detect issues

Testers:

• Benjamin Ell-Jones

Date:

• 05/08/2024

Duration:

• 45-90 mins

Scope:

• Test Textures API with postman using different inputs to seek any unexpected behaviour
• Use a heuristics cheat sheet to get inspiration for different inputs

References:

• Postman
• Textures API
• Ministry of Testing Test Heuristics Cheat Sheet

Test Approach:

• Use Postman to test a variety of parameters
• Turn off db container and trying to make a request to see if a 500 error code is returned

Notes:

Tried putting spaces in different places for example, before date, after date, throughout the date etc

Seeded database with leap day date to check that is still returned that bit of data

Tried a few always invalid days, they returned 404 rather than an error. Maybe we should disallow these? Seems to work fine for September 31st however

Does seem to reject completely, outlandishly invalid date numbers

Tested to see if removing base_time caused and error

Provided empty date, returned error

Checked to see if it errors if given a non leap year date. It does not give an error, it just returns no data (no data like this in database during test it probably should error before then).

Does seem to expect a specific date format and does not work with any other.

Checked to see if using Z instead of +00:00 works, it does.

Sent date to api as a string, does not work, as expected

Tried to disable the database and get a 500 error from the api, however this did not seem to work as postman request would not timeout and give any error, it would just keep going.

Conclusion

Seems to be fine, for the most part however, there are a few things to note, these may or may not require action:

• Checked to see if it errors if given a non leap year date. It does not give an error, it just returns no data (no data like this in database during test it probably should error before then).
• Tried a few always invalid days, they returned 404 rather than an error. Maybe we should disallow these? Seems to work fine for September 31st however, we get an error as we would expect.