Testing an Application
======================
## No Arguments
```
crashsim test "<command>"
```

This command would record command and test it with default set of checkers and mutators that would be useful on most applications.  The _UnusualFileType_ mutator, _CloseFails_ and _ReverseTime_ mutator's would probably be included in this set.

## Selecting an Operation
```
crashsim test --operation=<operation> "<command">
```
This command would record and test the command with a set of checkers and mutators that make sense for an application that performs the specified operation.  Maybe there's a _FileMove_ operation that uses the _UnusualFileType_ mutator and the _RenameFailsWithEXDEV_ mutator.

## Selecting a specific mutator
```
crashsim test --mutator=<mutator> "<command">
```

example: ```crashsim test "<command>:``


```
Possible Bug (syscall 120): Application did not divert when S_IFCHR was injected into fstat() st_mode field call
Possible Bug (syscall 124): Application did not divert when S_IFCHR was injected into lstat() st_mode field call
Possible Bug (syscall 150:  Application diverted when failing return value -1 with errno EIO was injected into close() call
Possible Bug (syscall 175): Application did not divert when time() call's result was decreased by 1000 seconds
...
```

Analyzing a Trace with a Checker
===============================

```
crashsim analyze --operation=<operation> --trace=<trace>

```
e.g. ```crashsim analyze --operation=FileMove --trace=mytrace.strace```


output
```
Analyzing FileMove operation started with rename() call on line 150
Possible Bug: Application truncates destination file before successfully opening source file
Bug: Application does not check file properties with fstat() after open()'ing it
Bug: Application failed to copy extended file attributes from source file to destination file
Bug: Application failed to copy permission from source file to destination file
Bug: Application does not close source file before exiting
```