Why Specflow ? it helps the team to talke the same language across the board. This creates a frictionless experiece for the team to understand what product they are building and how to make a qulity delivery. specflow also helps documenting the entire SDLC what is hooks ? Hooks can be used to perform additional automation logic at specific times, such as any setup required prior to executing a scenario Context Injection This feature will be helpful while we try to share data between two binding classes(among different steps of same scenario) To use context injection we need to do the following 1 Create your POCOs representing the shared data 2 Define them as constructor parameters in every binding class you need them 3 save the constructor argument to instance field ,you can use them in the step definitions.
Posts
What is design pattern? Design Patterns represent the best practices used by experienced software developers. Design patterns are solutions to general problems that software developers faced during software development. Structural patterns and behavioral patterns. 设计模式是有经验的软件工程师的最佳实践。设计模式是大部分软件工程师所面临的大部分问题的解决方案。 Why do we need design pattern in our test suite? Code reusability. It allowing the tester to enhance reliability. Helping us to create a structured code that eases our process of automation. It helps in improving communication. 使用设计模式可以让增加code 的复用性。它可以帮助tester来增加他的可靠性。帮助我们来创建一个结构性的code来降低我们的自动化成本. What are the different design patterns for automated tests? page object pattern facade design pattern singleton design pattern fluent page object pattern strategy design pattern What is page object model (or POM)? Page Object Model (POM) is a design pattern, popularly used in test automation that creates Object Repository for web UI elements. The advantage of the mode...
What is CI, CD, CT? CI: enable developers to continuously integrate new and updated code into a shared, central code repository several time a day. CI continuously integrates code changes into the existing codebase to quickly identify and remediate any conflicts between different developers’ code changes. The CI server notifies the team of the integration result. There should generally be four outcomes: failed build, successful build, failed tests, successful tests. If there’s a failure, the team fixes the issue ASAP. CD: CD is the process of automating code delivery from continuous integration to production, where it is tested and prepared for release. The code is kept in an always releasable state to deploy it automatically to production at any given time based on the customer‘s needs CT: CT is the practice of automating and integrating tests into the software delivery chain and automatically executing those tests against each build of the codebase. CT brings ...