Confirmed users
3,816
edits
QA/Community/Test Writing Workshop: Difference between revisions
Jump to navigation
Jump to search
→Some thoughts on the rough schedule above
No edit summary |
|||
| Line 74: | Line 74: | ||
** Talk about what to test a front end for when looking for security bugs, crashers etc. | ** Talk about what to test a front end for when looking for security bugs, crashers etc. | ||
By breaking up each section into concrete subsections, it gets a little easier to see what we would be filming, and it will help us to capture small, reusable bits of demonstrations which work better than long videos of entire presentations. Also, short subsections like this will help to encourage more participation and interaction among the audience. | |||
So, a possible one-day schedule could look something like this: | So, a possible one-day schedule could look something like this: | ||
| Line 92: | Line 92: | ||
* TODO: Issues with which to do first. On one level, starting with Front End testing and moving to back end testing seems like the natural progression, but I think that starting with back end testing and moving to front end testing is an easier progression to learn because the tests themselves and the technologies are build on each other better that way (INMO). | * TODO: Issues with which to do first. On one level, starting with Front End testing and moving to back end testing seems like the natural progression, but I think that starting with back end testing and moving to front end testing is an easier progression to learn because the tests themselves and the technologies are build on each other better that way (INMO). | ||
== Sign Up Here If You Are Interested == | == Sign Up Here If You Are Interested == | ||
{| border="1" cellpadding="2" | {| border="1" cellpadding="2" | ||