Search Results Heading

MBRLSearchResults

mbrl.module.common.modules.added.book.to.shelf
Title added to your shelf!
View what I already have on My Shelf.
Oops! Something went wrong.
Oops! Something went wrong.
While trying to add the title to your shelf something went wrong :( Kindly try again later!
Are you sure you want to remove the book from the shelf?
Oops! Something went wrong.
Oops! Something went wrong.
While trying to remove the title from your shelf something went wrong :( Kindly try again later!
    Done
    Filters
    Reset
  • Discipline
      Discipline
      Clear All
      Discipline
  • Is Peer Reviewed
      Is Peer Reviewed
      Clear All
      Is Peer Reviewed
  • Item Type
      Item Type
      Clear All
      Item Type
  • Subject
      Subject
      Clear All
      Subject
  • Year
      Year
      Clear All
      From:
      -
      To:
  • More Filters
4 result(s) for "Rick Mugridge"
Sort by:
EvolvingWeb-Based Test Automation into Agile Business Specifications
Usually, test automation scripts for a web application directly mirror the actions that the tester carries out in the browser, but they tend to be verbose and repetitive, making them expensive to maintain and ineffective in an agile setting. Our research has focussed on providing tool-support for business-level, example-based specifications that are mapped to the browser level for automatic verification. We provide refactoring support for the evolution of existing browser-level tests into business-level specifications. As resulting business rule tables may be incomplete, redundant or contradictory, our tool provides feedback on coverage.
Managing Agile Project Requirements with Storytest-Driven Development
Storytest-driven development is a complementary form of test-driven development (TDD) applied to overall system development. Using FitLibrary eases storytest-driven development, which brings together requirements and automated testing ideas and practices to support agile software development. Storytest-driven development helps bridge the gap between what organizations really need from a system and the system that developers actually deliver. This bridge builds on several factors. Storytest-driven development builds on and reuses ideas from previous requirements approaches, turning some of them \"inside out.\" Storytests don't express class diagrams and use cases directly, for example, but they're likely to emerge; making such connections explicit is a fruitful area of future work. Another promising research area is to bring a stronger task-oriented (usability) perspective to storytests.
Evolving Web-Based Test Automation into Agile Business Specifications
Usually, test automation scripts for a web application directly mirror the actions that the tester carries out in the browser, but they tend to be verbose and repetitive, making them expensive to maintain and ineffective in an agile setting. Our research has focussed on providing tool-support for business-level, example-based specifications that are mapped to the browser level for automatic verification. We provide refactoring support for the evolution of existing browser-level tests into business-level specifications. As resulting business rule tables may be incomplete, redundant or contradictory, our tool provides feedback on coverage.