UnstableChanges

Summary

  1. Add onfailure (details)
  2. powershell experiment with xml (details)
  3. more powershell (details)
  4. get-content command is lower case. (details)
  5. spelling (details)
  6. actually print the failing test names (details)
  7. try to add failure message (details)
  8. print the entire failure node. (details)
The file was modifiedappveyor.yml (diff)
Commit 7375471084138139d57fa8fdc3d81f57bd41a3c8 by noreply
powershell experiment with xml
The file was modifiedappveyor.yml (diff)
The file was modifiedappveyor.yml (diff)
Commit c16c6f97302b6ef03ce9e7ce298b5cbd9c2d7d70 by noreply
get-content command is lower case.
The file was modifiedappveyor.yml (diff)
The file was modifiedappveyor.yml (diff)
Commit f166b1b97f2a6c0747c3a0560a3a69b5d9496a63 by noreply
actually print the failing test names
Still need to extract the failure causes, but this is better than
printing the causes without the test names (which is what the previous
version did).
The file was modifiedappveyor.yml (diff)
Commit 4f0a597fd3a858a8128e880032beb2318b0c1f91 by noreply
try to add failure message
this doesn't work when multiple failures are reported for a single test
case...
The file was modifiedappveyor.yml (diff)
Commit b7fda6f41867093f726f19c7a44eb0979377b737 by noreply
print the entire failure node.
includes at least part of the message in output.
The file was modifiedappveyor.yml (diff)