Decodes the file's bytes with the declared encoding
All 2 scenarios hold
A table can live in a classpath resource file instead of the annotation: @TableTest(resource = "external.table", encoding = "UTF-8").
The first three rules below call the loading API with those same arguments. Their tables can therefore show which paths resolve, what text the file's bytes become, and how loading fails.
The rules after them are driven by the very files shown. Each row comes from a line of the file rather than from the annotation.
The last row of /subfolder/custom_encoding.table holds the six ISO-8859-1 letters ÉÜ¥ÆØÅ. Read in another encoding the same bytes decode to other characters, so the encoding belongs with the resource path.
expected outcome
broken scenario
| Scenario | Encoding | Characters in the last row's first cell? | Code points? |
|---|---|---|---|
| The encoding the file uses | ISO-8859-1 | 6 |
|
| Read as UTF-8 instead | UTF-8 | 5 |
|