fsdfsdfdsfsfsd

Specification by Example to proces pracy z wymaganiami angażujący zarówno biznes jak i zespół wytwórczy. Pomaga zbudować właściwy produkt, który rzeczywiście rozwiązuje problemy biznesowe i przynosi zwrot z inwestycji.

Course intended for:

The training is dedicated to all those involved in the process of software development, both with regard to the business aspects (product defining) and development as such. During the second day of training, technical aspects, crucial for the work of programmers, testers and architects, will be discussed.

Persons responsible for the business side of software development are encouraged to attend the first day of training, for which there are no preliminary requirements. The programmers, testers and architects are encouraged to attend the full, two-day training.

The presented training price is applicable to the full version of two days. The cost of participation in the first day only is net PLN 900 per person.

Course objective:

The training objective is to acquire the competences allowing for safe delivery of high quality software, bringing high value to business thanks to application of the Specification by Example process.

Course strengths:

Thanks to the numerous workshops offered, the participants will be able to try out the techniques being discussed in practice. Thus, they will be able to apply these in practice immediately.

Requirements:

Participants of the second day of training are expected to have good programming skills in one of the following languages: Java, C#, Ruby. There are no prerequisites for participation in the first day of training.

Course parameters:

2 days x 8h (7h net) Group size: no more than 16 participants.

Course curriculum

  1. What is Specification by Example, what problems it saves and how it can help you

  2. Components of the Specification by Example process

  3. Benefits from specification - examples

  4. Syntax of Gherkin language. Development of examples of Given/When/Then for the purpose of their further automation

  5. What should be present in the examples and what should be withdrawn to make the examples understandable for everyone

  6. How to organize a workshop of requirements, during which the participants will identify examples for user stories

  7. Costs and benefits of example automation

  8. Organization and development of structure of automated examples – the way to warrant constant validity of the documentation

  9. The role of developers, testers, business analysts in the Specification by Example process

  10. Correlations between user stories, acceptance criteria and scenarios

  11. Correlations between the requirements, examples and tests

  12. How to automate a scenario using Cucumber/Cucumber-JVM/SpecFlow (depending on the programming language selected)

  13. How to create a transparent, easy to maintain test set

  14. Development of hte automation layer architecture

  15. Role of the domain language (DSL) in the automation process

  16. Strengths and weaknesses of automation at various levels of abstraction

  17. Web application automation using Selenium WebDriver

  18. How to commence scenario automation in an existing project

Any questions?

* Required.


Contact
Phone +48 22 2035600
Fax +48 22 2035601
Email