Like SpecFlow
•Download as PPTX, PDF•
0 likes•21 views
This document discusses SpecFlow and an alternative called BDDfy that aims to provide similar behavior-driven development capabilities without requiring a new language or tool. It provides examples of writing tests using BDDfy including defining scenarios with given, when, then steps and executing them. The document asks questions about SpecFlow usage and seeks discussion on the pros and cons of BDDfy as an alternative for writing readable, data-driven tests without major changes to an existing codebase or tooling.
Report
Share
Report
Share
Recommended
Testing and symfony2
Tomasz Łopusiewicz - Testowanie i Symfony2
Prezentacja z Uszanowanka Programowanka #9 - uszanowanko.pl
W trakcie prezentacji przyjrzymy się kilku narzędziom oraz różnym podejściom w testowaniu aplikacji webowych opartych o Symfony2. Przeanalizujemy także kiedy warto warto skupić się na testowalności kodu pomijając przy tym wygodę i funkcje frameworka.
TDD in PHP - Memphis PHP 2011-08-25
The document is a presentation about test-driven development (TDD) in PHP. It introduces TDD and the speaker, defines the TDD process, lists benefits and drawbacks, and demonstrates a live coding example of using TDD to build a calculator and tutor class. The example shows writing tests first, then code to pass the tests, and refactoring with confidence due to the tests. The goals are to provide a practical TDD example and demonstrate how TDD impacts design decisions.
Documenting Code - Patterns and Anti-patterns - NLPW 2016
How do we document code? A good solution is to create self-explanatory code; this somewhat eliminates the need to document the code. We still need some very basic documentation. Code comments are one form of documentation, that is often misused. This talk is about self-explanatory code, the documentation we need and code comment patterns and anti-patterns.
Illustrated Code (ASE 2021)
Illustrated Code: Building Software in a Literate Way
Andreas Zeller, CISPA Helmholtz Center for Information Security
Notebooks – rich, interactive documents that join together code, documentation, and outputs – are all the rage with data scientists. But can they be used for actual software development? In this talk, I share experiences from authoring two interactive textbooks – fuzzingbook.org and debuggingbook.org – and show how notebooks not only serve for exploring and explaining code and data, but also how they can be used as software modules, integrating self-checking documentation, tests, and tutorials all in one place. The resulting software focuses on the essential, is well-documented, highly maintainable, easily extensible, and has a much higher shelf life than the "duct tape and wire” prototypes frequently found in research and beyond.
Test Driven Development
Test-driven development (TDD) is an agile software development process where test cases are developed before code. The TDD process involves writing a test, watching it fail, writing code to pass the test, and refactoring code as needed. TDD encourages dividing work into small pieces and promotes high-quality code by requiring tests to pass before adding new features. While TDD requires more initial time writing tests, it can reduce debugging time and defects in the long run.
AspectMock
AspectMock is a PHP library that allows mocking of any method call, including static and private methods, without requiring code refactoring. It uses aspect-oriented programming to intercept method calls and return mock values. To use it, install via Composer, create a custom autoloader for tests, and define the class and methods to mock along with their return values. AspectMock makes it easy to mock code as written without dependency injection refactoring required by other mocking tools.
Agile JavaScript Testing
Cover the advantages of test driven development, the reasons for pushing it all the way to the browser level, and then explore the options for testing JavaScript, look at some examples, and then integrate the tests into our existing development workflow.
Reduce Reuse Refactor
This document discusses strategies for refactoring legacy code to improve its design and maintainability. It defines refactoring as changing code structure without altering functionality. The key steps outlined are to first add new functionality, then refactor, then add more functionality. Code "smells" that indicate areas for refactoring include duplicate code, long methods, large classes, and more. Tools can help detect smells. Technical debt should be paid off incrementally by refactoring in small batches while ensuring tests pass. Specific refactoring techniques include autoloading, consolidating classes, removing globals, replacing instantiation with factories, extracting logic, and more. Testing is important throughout the refactoring process.
Recommended
Testing and symfony2
Tomasz Łopusiewicz - Testowanie i Symfony2
Prezentacja z Uszanowanka Programowanka #9 - uszanowanko.pl
W trakcie prezentacji przyjrzymy się kilku narzędziom oraz różnym podejściom w testowaniu aplikacji webowych opartych o Symfony2. Przeanalizujemy także kiedy warto warto skupić się na testowalności kodu pomijając przy tym wygodę i funkcje frameworka.
TDD in PHP - Memphis PHP 2011-08-25
The document is a presentation about test-driven development (TDD) in PHP. It introduces TDD and the speaker, defines the TDD process, lists benefits and drawbacks, and demonstrates a live coding example of using TDD to build a calculator and tutor class. The example shows writing tests first, then code to pass the tests, and refactoring with confidence due to the tests. The goals are to provide a practical TDD example and demonstrate how TDD impacts design decisions.
Documenting Code - Patterns and Anti-patterns - NLPW 2016
How do we document code? A good solution is to create self-explanatory code; this somewhat eliminates the need to document the code. We still need some very basic documentation. Code comments are one form of documentation, that is often misused. This talk is about self-explanatory code, the documentation we need and code comment patterns and anti-patterns.
Illustrated Code (ASE 2021)
Illustrated Code: Building Software in a Literate Way
Andreas Zeller, CISPA Helmholtz Center for Information Security
Notebooks – rich, interactive documents that join together code, documentation, and outputs – are all the rage with data scientists. But can they be used for actual software development? In this talk, I share experiences from authoring two interactive textbooks – fuzzingbook.org and debuggingbook.org – and show how notebooks not only serve for exploring and explaining code and data, but also how they can be used as software modules, integrating self-checking documentation, tests, and tutorials all in one place. The resulting software focuses on the essential, is well-documented, highly maintainable, easily extensible, and has a much higher shelf life than the "duct tape and wire” prototypes frequently found in research and beyond.
Test Driven Development
Test-driven development (TDD) is an agile software development process where test cases are developed before code. The TDD process involves writing a test, watching it fail, writing code to pass the test, and refactoring code as needed. TDD encourages dividing work into small pieces and promotes high-quality code by requiring tests to pass before adding new features. While TDD requires more initial time writing tests, it can reduce debugging time and defects in the long run.
AspectMock
AspectMock is a PHP library that allows mocking of any method call, including static and private methods, without requiring code refactoring. It uses aspect-oriented programming to intercept method calls and return mock values. To use it, install via Composer, create a custom autoloader for tests, and define the class and methods to mock along with their return values. AspectMock makes it easy to mock code as written without dependency injection refactoring required by other mocking tools.
Agile JavaScript Testing
Cover the advantages of test driven development, the reasons for pushing it all the way to the browser level, and then explore the options for testing JavaScript, look at some examples, and then integrate the tests into our existing development workflow.
Reduce Reuse Refactor
This document discusses strategies for refactoring legacy code to improve its design and maintainability. It defines refactoring as changing code structure without altering functionality. The key steps outlined are to first add new functionality, then refactor, then add more functionality. Code "smells" that indicate areas for refactoring include duplicate code, long methods, large classes, and more. Tools can help detect smells. Technical debt should be paid off incrementally by refactoring in small batches while ensuring tests pass. Specific refactoring techniques include autoloading, consolidating classes, removing globals, replacing instantiation with factories, extracting logic, and more. Testing is important throughout the refactoring process.
Documenting code yapceu2016
How do we document code? A good solution is to create self-explanatory code; this somewhat eliminates the need to document the code. We still need some very basic documentation. Code comments are one form of documentation, that is often misused. This talk is about self-explanatory code, the documentation we need and code comment patterns and anti-patterns.
TDD Walkthrough - Encryption
The document is a walkthrough of using test-driven development (TDD) to solve an encryption problem. It begins by setting up test and source code files. Tests are written based on examples from the problem. Minimal code is written to pass each test. Refactoring improves the code while maintaining passing tests. The implementation is generalized through many small iterative changes. Edge cases are addressed, like when the encryption grid is too small. The completed solution passes all tests.
PhpSpec: practical introduction
This document provides an introduction to using PhpSpec for test-driven development (TDD). It explains what TDD is, the benefits of TDD, and why PhpSpec is a good choice for TDD in PHP projects. It then walks through setting up a PhpSpec project, describing a sample Blog class, writing examples to test the Blog class, running the tests, refactoring code, and using PhpSpec matchers. The document concludes with tips on using PhpSpec to design object interactions and collaboration.
Tdd in php a brief example
The document discusses Test Driven Development (TDD) in PHP. It provides an overview of TDD, the benefits it provides like high cohesion and loose coupling, and some drawbacks. It then demonstrates a live coding example of TDD in PHP by building a simple integer calculator using PHPUnit for a math tutor application. Resources for learning more about TDD, PHPUnit, and Xdebug are also included.
EMPEX LA 2018 - Inclusion Starts with Docs
This document summarizes a talk about using Elixir's built-in documentation system, ExDoc. It recommends writing documentation in Markdown inline with source code, using moduledocs to explain modules and function docs to specify functions. It also recommends doctests to test sample code and typespecs so functions' data types are clear. Dialyzer checks that typespecs match actual functions. ExDoc publishes documentation to hexdocs.pm and supports linking to source code on GitHub. Overall, Elixir and ExDoc are praised for producing documentation that explains purposes, specifies functions clearly with examples, keeps examples up to date with doctests, and provides easy access to source code.
Thinkful - Intro to JavaScript
This document provides an introduction to JavaScript, covering key concepts like variables, data types, functions, and how the web works. It begins with introductions from the instructor and mentor. It then discusses programming fundamentals like defining problems, finding solutions, and implementing them in code. The document explains that JavaScript is used for both front-end and back-end development. It covers JavaScript variables, strings, numbers, Booleans, and basic functions. It provides examples and challenges for readers to practice the concepts. In the end, it discusses continuing education options through 1-on-1 mentorship.
Quick Intro to Clean Coding
This document provides an introduction to clean coding principles including identifying bad code through code smells, writing tests, and refactoring code. It outlines good practices for writing transparent, reasonable, and usable code and emphasizes writing tests as a safety belt and leaving the codebase in better condition. The document presents object-oriented design patterns, principles, knowledge of languages and libraries, code smells, testing, and code reviews/refactoring as tools for writing clean code. It links to an example of refactoring code in a step-by-step manner and emphasizes writing tests as the starting point and keeping them as the grammar for the system.
Tdd is not about testing
Why should we use TDD to develop in Elixir? When we are applying it correctly? What are the differences that we can find in a code developed with TDD and in code not developed with it? Is it TDD about testing? Really? In this talk, I'll show what is TDD and how can be used it in functional programming like Elixir to design the small and the big parts of your system, showing what are the difference and the similarities between an OOP and FP environment. Showing what is the values of applying a technique like TDD in Elixir and what we should obtain applying it.
Effective TDD - Less is more
The document discusses techniques for making test-driven development (TDD) more enjoyable. It provides examples of conversations where a programmer asks if they can have quality assurance write tests, and whether tests are needed if code is working. The creator of TDD notes that tests should be written to reach a high level of confidence, not just to print "OK". Several rationalizations for not writing tests are debunked. The document advocates designing programs by writing tests first, and making initial tests fail on purpose in order to have the short-term goal of fixing them. This focuses effort and makes the process more fun. Less testing is needed than achieving 100% coverage; tests should be written when most useful, such as for new code
Test Driven Development and Automation
This document discusses test driven development (TDD) and automation for PHP projects. It covers what TDD is, why it should be done, where tests should run, who should adopt TDD, and why unit testing, code coverage, code sniffing and Selenium are important. It also discusses tools for PHP TDD like Xdebug, PHPUnit, PHP_CodeSniffer and IDEs. The document provides examples of writing test cases with the red-green-refactor process and integrating TDD into a build system with automated testing on every code change.
Test Driven iOS Development (TDD)
TDD involves first writing an automated test that fails, then writing just enough code to pass that test, and refactoring the code. The red-green-refactor process ensures code is tested and well-designed. Studies found TDD reduced pre-release defects by 40-90% and increased initial development time by 15-35%, but allowed for faster development long-term by eliminating bugs early. The document demonstrates TDD with a temperature converter in Xcode, starting with failing tests for -40C=-40F and 30C=86F then coding to pass them.
Refactoring, 2nd Edition
This document discusses refactoring and summarizes the key points from Martin Fowler's book Refactoring. It covers what refactoring is, when it should be used by recognizing code smells, and how it should be done through small, incremental changes backed by thorough testing. The benefits of refactoring include improving code quality by reducing bugs and technical debt, while making the code easier to understand and modify. Tools now make refactoring easier by providing code analysis, refactoring suggestions, and quick fixes.
BDD style Unit Testing
Here are some potential caveats with BDD style testing:
1. The framework can feel too "magical" if it uses too much metaprogramming under the hood. The implementation details should not be obscured.
2. Descriptions can become too vague if they only state intentions at a very high level without concrete examples. Tests as documentation only works if the descriptions are clear and specific.
3. There is a risk of duplication if contexts or examples are not properly organized and nested. Descriptions should aim to be DRY.
4. Performance overhead of the framework if it does a lot of runtime reflection or string manipulation. The framework should have a small performance footprint.
5. Tests become brittle
It's all about behaviour, also in php - phpspec
The document discusses test-driven development (TDD) and behavior-driven development (BDD). It explains that BDD uses external specifications to describe behavior before coding starts. This solves issues with TDD like where to begin and what to test. BDD uses a double cycle of writing scenarios in Behat and then examples in Phpspec at the internal class level. Phpspec is used to describe behavior through examples before coding classes. The document provides instructions on installing Phpspec and describes how to define a specification and examples.
Test Driven Development
What is TTD?
Unit Test & Refactoring
Got Bugs?
Tenets of TTD.
Benifits of TDD.
Advantages & Disadvantages of TDD.
Ddc2011 효과적으로레거시코드다루기
The document discusses techniques for effectively working with legacy code. It recommends starting by finding small parts of legacy code that can be tested without making big changes. Then use those tests to safely extend design changes. When new features are needed, change a little code and add some tests to the affected areas. This spreads tests throughout the legacy code over time. The document also provides examples of refactoring techniques like extract method, sprout method, characterization tests, subclassing and overriding methods, and extracting method objects to untangle legacy code in a safe, test-driven way.
The First C# Project Analyzed
The PVS-Studio team is now actively developing a static analyzer for C# code. The first version is expected by the end of 2015. And for now my task is to write a few articles to attract C# programmers' attention to our tool in advance. I've got an updated installer today, so we can now install PVS-Studio with C#-support enabled and even analyze some source code. Without further hesitation, I decided to scan whichever program I had at hand. This happened to be the Umbraco project. Of course we can't expect too much of the current version of the analyzer, but its functionality has been enough to allow me to write this small article.
BDD Primer
An introduction to Test-First Behavior-Driven Development, and acceptance testing with Gherkin, with some real-life Gherkin examples. Content created for C# code, but the principles do apply to other languages/environments.
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
Slides from the St. Louis Big Data IDEA meetup. Kit Menke presented on how to test your Apache Spark applications. May 2021 meetup notes
Code Generation using T4
T4 is a template processing engine that allows generating text files like source code from templates. It takes domain models as input, such as class diagrams or database metadata, and uses these to generate code outputs through T4 templates. The templates use T4 syntax including processing directives, text blocks, code blocks, and expression blocks to generate the target files. T4 is commonly used in Visual Studio for code generation scenarios like generating Entity Framework classes or ASP.NET MVC views from models. It provides a way to describe models and have code generated automatically from those descriptions.
C Sharp String.pptx
C# String Intern function. In this presentation, we will explore the C# string intern function, a powerful feature that optimizes memory usage and improves performance in .NET applications. We will discuss the concept of string interning, its benefits, and how the intern function works within the context of C# programming. By understanding this function, developers can effectively enhance their applications' efficiency and ensure optimal utilization of resources. Join us as we delve into the world of string interning, including real-world examples and best practices for implementing this powerful feature in your C# projects.
C# DSL (eng)
DSL Domain specific language. Presentation show what is DSL and what is not. Shown a simple trick to convert internal DSL into Externals. Real external DSL example shown (How to deal with regular expression complexity).
More Related Content
Similar to Like SpecFlow
Documenting code yapceu2016
How do we document code? A good solution is to create self-explanatory code; this somewhat eliminates the need to document the code. We still need some very basic documentation. Code comments are one form of documentation, that is often misused. This talk is about self-explanatory code, the documentation we need and code comment patterns and anti-patterns.
TDD Walkthrough - Encryption
The document is a walkthrough of using test-driven development (TDD) to solve an encryption problem. It begins by setting up test and source code files. Tests are written based on examples from the problem. Minimal code is written to pass each test. Refactoring improves the code while maintaining passing tests. The implementation is generalized through many small iterative changes. Edge cases are addressed, like when the encryption grid is too small. The completed solution passes all tests.
PhpSpec: practical introduction
This document provides an introduction to using PhpSpec for test-driven development (TDD). It explains what TDD is, the benefits of TDD, and why PhpSpec is a good choice for TDD in PHP projects. It then walks through setting up a PhpSpec project, describing a sample Blog class, writing examples to test the Blog class, running the tests, refactoring code, and using PhpSpec matchers. The document concludes with tips on using PhpSpec to design object interactions and collaboration.
Tdd in php a brief example
The document discusses Test Driven Development (TDD) in PHP. It provides an overview of TDD, the benefits it provides like high cohesion and loose coupling, and some drawbacks. It then demonstrates a live coding example of TDD in PHP by building a simple integer calculator using PHPUnit for a math tutor application. Resources for learning more about TDD, PHPUnit, and Xdebug are also included.
EMPEX LA 2018 - Inclusion Starts with Docs
This document summarizes a talk about using Elixir's built-in documentation system, ExDoc. It recommends writing documentation in Markdown inline with source code, using moduledocs to explain modules and function docs to specify functions. It also recommends doctests to test sample code and typespecs so functions' data types are clear. Dialyzer checks that typespecs match actual functions. ExDoc publishes documentation to hexdocs.pm and supports linking to source code on GitHub. Overall, Elixir and ExDoc are praised for producing documentation that explains purposes, specifies functions clearly with examples, keeps examples up to date with doctests, and provides easy access to source code.
Thinkful - Intro to JavaScript
This document provides an introduction to JavaScript, covering key concepts like variables, data types, functions, and how the web works. It begins with introductions from the instructor and mentor. It then discusses programming fundamentals like defining problems, finding solutions, and implementing them in code. The document explains that JavaScript is used for both front-end and back-end development. It covers JavaScript variables, strings, numbers, Booleans, and basic functions. It provides examples and challenges for readers to practice the concepts. In the end, it discusses continuing education options through 1-on-1 mentorship.
Quick Intro to Clean Coding
This document provides an introduction to clean coding principles including identifying bad code through code smells, writing tests, and refactoring code. It outlines good practices for writing transparent, reasonable, and usable code and emphasizes writing tests as a safety belt and leaving the codebase in better condition. The document presents object-oriented design patterns, principles, knowledge of languages and libraries, code smells, testing, and code reviews/refactoring as tools for writing clean code. It links to an example of refactoring code in a step-by-step manner and emphasizes writing tests as the starting point and keeping them as the grammar for the system.
Tdd is not about testing
Why should we use TDD to develop in Elixir? When we are applying it correctly? What are the differences that we can find in a code developed with TDD and in code not developed with it? Is it TDD about testing? Really? In this talk, I'll show what is TDD and how can be used it in functional programming like Elixir to design the small and the big parts of your system, showing what are the difference and the similarities between an OOP and FP environment. Showing what is the values of applying a technique like TDD in Elixir and what we should obtain applying it.
Effective TDD - Less is more
The document discusses techniques for making test-driven development (TDD) more enjoyable. It provides examples of conversations where a programmer asks if they can have quality assurance write tests, and whether tests are needed if code is working. The creator of TDD notes that tests should be written to reach a high level of confidence, not just to print "OK". Several rationalizations for not writing tests are debunked. The document advocates designing programs by writing tests first, and making initial tests fail on purpose in order to have the short-term goal of fixing them. This focuses effort and makes the process more fun. Less testing is needed than achieving 100% coverage; tests should be written when most useful, such as for new code
Test Driven Development and Automation
This document discusses test driven development (TDD) and automation for PHP projects. It covers what TDD is, why it should be done, where tests should run, who should adopt TDD, and why unit testing, code coverage, code sniffing and Selenium are important. It also discusses tools for PHP TDD like Xdebug, PHPUnit, PHP_CodeSniffer and IDEs. The document provides examples of writing test cases with the red-green-refactor process and integrating TDD into a build system with automated testing on every code change.
Test Driven iOS Development (TDD)
TDD involves first writing an automated test that fails, then writing just enough code to pass that test, and refactoring the code. The red-green-refactor process ensures code is tested and well-designed. Studies found TDD reduced pre-release defects by 40-90% and increased initial development time by 15-35%, but allowed for faster development long-term by eliminating bugs early. The document demonstrates TDD with a temperature converter in Xcode, starting with failing tests for -40C=-40F and 30C=86F then coding to pass them.
Refactoring, 2nd Edition
This document discusses refactoring and summarizes the key points from Martin Fowler's book Refactoring. It covers what refactoring is, when it should be used by recognizing code smells, and how it should be done through small, incremental changes backed by thorough testing. The benefits of refactoring include improving code quality by reducing bugs and technical debt, while making the code easier to understand and modify. Tools now make refactoring easier by providing code analysis, refactoring suggestions, and quick fixes.
BDD style Unit Testing
Here are some potential caveats with BDD style testing:
1. The framework can feel too "magical" if it uses too much metaprogramming under the hood. The implementation details should not be obscured.
2. Descriptions can become too vague if they only state intentions at a very high level without concrete examples. Tests as documentation only works if the descriptions are clear and specific.
3. There is a risk of duplication if contexts or examples are not properly organized and nested. Descriptions should aim to be DRY.
4. Performance overhead of the framework if it does a lot of runtime reflection or string manipulation. The framework should have a small performance footprint.
5. Tests become brittle
It's all about behaviour, also in php - phpspec
The document discusses test-driven development (TDD) and behavior-driven development (BDD). It explains that BDD uses external specifications to describe behavior before coding starts. This solves issues with TDD like where to begin and what to test. BDD uses a double cycle of writing scenarios in Behat and then examples in Phpspec at the internal class level. Phpspec is used to describe behavior through examples before coding classes. The document provides instructions on installing Phpspec and describes how to define a specification and examples.
Test Driven Development
What is TTD?
Unit Test & Refactoring
Got Bugs?
Tenets of TTD.
Benifits of TDD.
Advantages & Disadvantages of TDD.
Ddc2011 효과적으로레거시코드다루기
The document discusses techniques for effectively working with legacy code. It recommends starting by finding small parts of legacy code that can be tested without making big changes. Then use those tests to safely extend design changes. When new features are needed, change a little code and add some tests to the affected areas. This spreads tests throughout the legacy code over time. The document also provides examples of refactoring techniques like extract method, sprout method, characterization tests, subclassing and overriding methods, and extracting method objects to untangle legacy code in a safe, test-driven way.
The First C# Project Analyzed
The PVS-Studio team is now actively developing a static analyzer for C# code. The first version is expected by the end of 2015. And for now my task is to write a few articles to attract C# programmers' attention to our tool in advance. I've got an updated installer today, so we can now install PVS-Studio with C#-support enabled and even analyze some source code. Without further hesitation, I decided to scan whichever program I had at hand. This happened to be the Umbraco project. Of course we can't expect too much of the current version of the analyzer, but its functionality has been enough to allow me to write this small article.
BDD Primer
An introduction to Test-First Behavior-Driven Development, and acceptance testing with Gherkin, with some real-life Gherkin examples. Content created for C# code, but the principles do apply to other languages/environments.
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
Slides from the St. Louis Big Data IDEA meetup. Kit Menke presented on how to test your Apache Spark applications. May 2021 meetup notes
Code Generation using T4
T4 is a template processing engine that allows generating text files like source code from templates. It takes domain models as input, such as class diagrams or database metadata, and uses these to generate code outputs through T4 templates. The templates use T4 syntax including processing directives, text blocks, code blocks, and expression blocks to generate the target files. T4 is commonly used in Visual Studio for code generation scenarios like generating Entity Framework classes or ASP.NET MVC views from models. It provides a way to describe models and have code generated automatically from those descriptions.
Similar to Like SpecFlow (20)
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
More from Dmitry Dorogoy
C Sharp String.pptx
C# String Intern function. In this presentation, we will explore the C# string intern function, a powerful feature that optimizes memory usage and improves performance in .NET applications. We will discuss the concept of string interning, its benefits, and how the intern function works within the context of C# programming. By understanding this function, developers can effectively enhance their applications' efficiency and ensure optimal utilization of resources. Join us as we delve into the world of string interning, including real-world examples and best practices for implementing this powerful feature in your C# projects.
C# DSL (eng)
DSL Domain specific language. Presentation show what is DSL and what is not. Shown a simple trick to convert internal DSL into Externals. Real external DSL example shown (How to deal with regular expression complexity).
C sharp mash up
C# Mash up. Tips and tricks, unusual behavior, strange syntax and more. If you plan to use this for a C# language interview, do it carefully. Here are described extremes and not typical things. And even experienced programmers can tolerate errors here.
DSL with C# easy start
What's DSL? How it looks like?
Internal DSL. Easy trick to convert internal DSL into External DSL.
Just a few words about external DSL
фотоFun
Photo with Fun. Фото и развлечения на лето в одной презентации. Если после просмотра вы задумаетесь над тем что фотография - это весело и интересно, то цель презентации достигнута. Презентация была показана на вечеринке Печа-Куча, Новосибирск 4 июня 2014
More from Dmitry Dorogoy (7)
Recently uploaded
Odoo ERP Vs. Traditional ERP Systems – A Comparative Analysis
When it is all about ERP solutions, companies typically meet their needs with common ERP solutions like SAP, Oracle, and Microsoft Dynamics. These big players have demonstrated that ERP systems can be either simple or highly comprehensive. This remains true today, but there are new factors to consider, including a promising new contender in the market that’s Odoo. This blog compares Odoo ERP with traditional ERP systems and explains why many companies now see Odoo ERP as the best choice.
What are ERP Systems?
An ERP, or Enterprise Resource Planning, system provides your company with valuable information to help you make better decisions and boost your ROI. You should choose an ERP system based on your company’s specific needs. For instance, if you run a manufacturing or retail business, you will need an ERP system that efficiently manages inventory. A consulting firm, on the other hand, would benefit from an ERP system that enhances daily operations. Similarly, eCommerce stores would select an ERP system tailored to their needs.
Because different businesses have different requirements, ERP system functionalities can vary. Among the various ERP systems available, Odoo ERP is considered one of the best in the ERp market with more than 12 million global users today.
Odoo is an open-source ERP system initially designed for small to medium-sized businesses but now suitable for a wide range of companies. Odoo offers a scalable and configurable point-of-sale management solution and allows you to create customised modules for specific industries. Odoo is gaining more popularity because it is built in a way that allows easy customisation, has a user-friendly interface, and is affordable. Here, you will cover the main differences and get to know why Odoo is gaining attention despite the many other ERP systems available in the market.
UI5con 2024 - Bring Your Own Design System
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
https://2024.springio.net/sessions/automated-software-refactoring-with-openrewrite-and-generative-ai/
Hand Rolled Applicative User Validation Code Kata
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Requirement Traceability in Xen Functional Safety
Using OpenFastTrace to trace requirements in Xen functional safety
How to write a program in any programming language
How to write a program in any programming language
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers. This video you can watch from my youtube channel at https://youtu.be/m-F-mZA3MkU
Mobile App Development Company In Noida | Drona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Using Query Store in Azure PostgreSQL to Understand Query Performance
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
WWDC 2024 Keynote Review: For CocoaCoders Austin
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
Recently uploaded (20)
Odoo ERP Vs. Traditional ERP Systems – A Comparative Analysis
Odoo ERP Vs. Traditional ERP Systems – A Comparative Analysis
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
How to write a program in any programming language
How to write a program in any programming language
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers.pptx
Mobile App Development Company In Noida | Drona Infotech
Mobile App Development Company In Noida | Drona Infotech
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
Like SpecFlow
- 2. “Simple” SpecFlow example Scenario: Add two numbers Given the first number is 50 And the second number is 70 When the two numbers are added Then the result should be 120
- 3. Where is the code?
- 4. Code
- 5. First problem … duplicates
- 6. Where is my DRY principle?
- 10. Like SpecFlow but not so hard! • No new “Languages” • Stay on same tech stack (C#) • Any test framework • xUnit for example • Data driven tests = any other tests in a project • Easy switch • No new tool, license required • Absolutely free
- 12. LikeSpecFlow
- 13. Show me how it works on a real example.
- 14. Show me how it works on a real example.
- 15. Show me test results, pls.
- 16. Code magic …
- 18. Open web page
- 19. How is a method name transformed into readable text?
- 20. [CallerMemberName] attribute rushes to the rescue!
- 21. Magic code
- 22. Q & A • Who use Specflow? • Do you have a real example where non programmer write tests (without touching C#) • Do you have test spec out of sync with doc problem? • Why not to use simple C# tests? • What’s your reasons to use SpecFlow? • Are you happy with SpecFlow or it could be better? Let’s discuss
- 23. Other solutions (BDDFY) Why it is ok and why not?
- 24. BDDfy
- 25. BDDfy
- 26. BDDfy results
- 27. BDDfy advanced => advanced => advanced
- 29. Artificial intelligence to the rescue!
- 30. Prompt I will provide you with a textual command and a list of C# function signatures. Your task is to analyze the function name, parameter names, and types and determine whether the provided text can be interpreted as a textual function call command. Please convert the text provided into a function call. Example textual command: 'Beep three times.' Example function signature: 'void Beep(int timesToBeep);' Expected result: 'Beep(3);
- 33. Test code, ready to run
- 34. Full control