Llewellyn/exa
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/exa.git synced 2024-11-14 16:34:06 +00:00
Code Issues Projects Releases Wiki Activity
31043462af
exa/xtests/details-view-dates.toml

94 lines
3.0 KiB
TOML
Raw Normal View History

More date-related xtests • Displaying accessed and modified dates • Displaying dates in the distant past and far future (#557)
2020-10-17 20:26:24 +00:00
# various date fields
[[cmd]]
name = "‘exa -lh’ produces a table using the modified time field"
shell = "exa -lh /testcases/dates"
stdout = { file = "outputs/dates_long_time_modified.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'header', 'time' ]
[[cmd]]
name = "‘exa -lh --time=modified’ produces a table using the modified time field"
shell = "exa -lh --time=modified /testcases/dates"
stdout = { file = "outputs/dates_long_time_modified.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'header', 'time' ]
[[cmd]]
name = "‘exa -lh --time=accessed’ produces a table using the accessed time field"
shell = "exa -lh --time=accessed /testcases/dates"
stdout = { file = "outputs/dates_long_time_accessed.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'header', 'time' ]
# distant past and far future dates
[[cmd]]
name = "‘exa -l’ handles dates far past and future dates"
shell = "exa -l /testcases/far-dates"
stdout = { file = "outputs/far_dates_long.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'time' ]
Use Specsheet for the extended tests This commit changes the way the extended test suite is run. Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems: • It stops at the first failure, so if one test fails, you have no idea how many actually failed. • It also didn't actually show you the diff if one was different, it just checked it. • It combined stdout and stderr, and didn't test the exit status of exa. • All the output file names were just whatever I felt like calling the file at the time. • There is no way to only run a few of the tests — you have to run the whole thing each time. • There's no feel-good overall view where you see how many tests are passing. I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time. The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files. So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
# alternate date formats
[[cmd]]
name = "‘exa -l --time-style=long-iso’ produces a table using the long-iso date format"
shell = "exa -l --time-style=long-iso /testcases/dates"
stdout = { file = "outputs/dates_long_timestyle_longiso.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'time-style' ]
[[cmd]]
name = "‘exa -l --time-style=full-iso’ produces a table using the full-iso date format"
shell = "exa -l --time-style=full-iso /testcases/dates"
stdout = { file = "outputs/dates_long_timestyle_fulliso.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'time-style' ]
[[cmd]]
name = "‘exa -l --time-style=iso’ produces a table using the iso date format"
shell = "exa -l --time-style=iso /testcases/dates"
stdout = { file = "outputs/dates_long_timestyle_iso.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'time-style' ]
# locales
[[cmd]]
name = "‘exa -l’ using a locale with 4-character-long month abbreviations (‘ja_JP’) sizes the date column correctly"
shell = "exa -l /testcases/dates"
Add a test checking that date of the current year follows locale
2021-04-09 16:46:10 +00:00
environment = { LC_TIME = "ja_JP.UTF-8", LANG = "ja_JP.UTF-8" }
Use Specsheet for the extended tests This commit changes the way the extended test suite is run. Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems: • It stops at the first failure, so if one test fails, you have no idea how many actually failed. • It also didn't actually show you the diff if one was different, it just checked it. • It combined stdout and stderr, and didn't test the exit status of exa. • All the output file names were just whatever I felt like calling the file at the time. • There is no way to only run a few of the tests — you have to run the whole thing each time. • There's no feel-good overall view where you see how many tests are passing. I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time. The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files. So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
stdout = { file = "outputs/dates_long_localejp.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'locales' ]
[[cmd]]
name = "‘exa -l’ using a locale with 5-character-long month abbreviations (‘fr_FR’) sizes the date column correctly"
shell = "exa -l /testcases/dates"
Add a test checking that date of the current year follows locale
2021-04-09 16:46:10 +00:00
environment = { LC_TIME = "fr_FR.UTF-8", LANG = "fr_FR.UTF-8" }
Use Specsheet for the extended tests This commit changes the way the extended test suite is run. Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems: • It stops at the first failure, so if one test fails, you have no idea how many actually failed. • It also didn't actually show you the diff if one was different, it just checked it. • It combined stdout and stderr, and didn't test the exit status of exa. • All the output file names were just whatever I felt like calling the file at the time. • There is no way to only run a few of the tests — you have to run the whole thing each time. • There's no feel-good overall view where you see how many tests are passing. I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time. The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files. So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2020-10-17 19:39:44 +00:00
stdout = { file = "outputs/dates_long_localefr.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'locales' ]
Add a test checking that date of the current year follows locale
2021-04-09 16:46:10 +00:00
[[cmd]]
name = "‘exa -l’ using a locale (‘fr_FR’) display dates of the current year with localized month name"
shell = "exa -l /testcases/files"
environment = { LC_TIME = "fr_FR.UTF-8", LANG = "fr_FR.UTF-8" }
stdout = { file = "outputs/dates_long_currentyear_localefr.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'long', 'locales' ]
Reference in New Issue Copy Permalink