It is relevent as of right now (as it does indeed test whether or not the parsing works), but I don’t know for how much longer it will be relevent considering most structopt based parse-schemes (like those we have in other crates) don’t have need of it. Here’s a quote from the other thread I just posted in:
I imagine there’s a few reasons we ignore some tests, but I think, in this case, it’s because it’s hard to maintain and/or was only intended to be temporary until we could get a better solution going (Anecdotally, this test does break relatively often tbh). But maybe somebody has a better answer than my somewhat hand-wavy one…