Difference between revisions of "Integrated test tools and an IDE for Testers"
From CitconWiki
Jump to navigationJump to searchJulianharty (talk | contribs) (Notes for the session on creating an IDE for testers) |
Julianharty (talk | contribs) (formatted content and added link for the HTML CodeSniffer utility) |
||
| Line 1: | Line 1: | ||
Suggested features / capabilities | Suggested features / capabilities | ||
| − | + | * testcases | |
| − | + | * scripted instructions | |
| − | + | * coded instructions | |
| − | + | * recording | |
| − | + | * discovery/inspection | |
| − | + | * reporting | |
| − | + | * bug tracking | |
| − | + | * test runs / test suite | |
| − | + | * import existing (similar) test cases | |
| − | + | * CI integration | |
| − | + | * debugging | |
| − | + | * backed by a version control system | |
| − | + | * IDE autocompletion | |
| − | + | * multiple ways to present stuff - visual, text, ... | |
| − | + | * auto-suggest of test ideas e.g. for security tests taken from owasp.org | |
Who are the target users: | Who are the target users: | ||
| − | + | * Powerusers? | |
| − | + | * Non-technical testers | |
Opensource, reducing barriers to entry | Opensource, reducing barriers to entry | ||
Hover over capability to see the UI of the app at each step of the test case | Hover over capability to see the UI of the app at each step of the test case | ||
| − | + | * See HTML Code Sniffer for an example of good UI that indicates where problems are visually displayed. http://squizlabs.github.com/HTML_CodeSniffer/ | |
Visual Components - drag and drop to create test cases - see the Visual Studio Workflow tool | Visual Components - drag and drop to create test cases - see the Visual Studio Workflow tool | ||
Latest revision as of 00:58, 21 October 2012
Suggested features / capabilities
- testcases
- scripted instructions
- coded instructions
- recording
- discovery/inspection
- reporting
- bug tracking
- test runs / test suite
- import existing (similar) test cases
- CI integration
- debugging
- backed by a version control system
- IDE autocompletion
- multiple ways to present stuff - visual, text, ...
- auto-suggest of test ideas e.g. for security tests taken from owasp.org
Who are the target users:
- Powerusers?
- Non-technical testers
Opensource, reducing barriers to entry
Hover over capability to see the UI of the app at each step of the test case
- See HTML Code Sniffer for an example of good UI that indicates where problems are visually displayed. http://squizlabs.github.com/HTML_CodeSniffer/
Visual Components - drag and drop to create test cases - see the Visual Studio Workflow tool
RubyMine recommended as a great IDE for Ruby code and writing Cucumber tests Cubittest - front end for Selenium has visual presentation Encrunch? a tool in the latest visual studio beta that runs tests all the time in memory without needing to save them
