�ݺ�ߣshows by User: lfryc

�ݺ�ߣshows by User: lfryc / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: lfryc / Sat, 11 Nov 2017 18:36:35 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: lfryc Role of QA in Continuous Delivery /slideshow/role-of-qa-in-continuous-delivery/81903424 roleofqaincontinuousdelivery-171111183635
QA teams are traditionally part of IT departments, but forms own silo that is separated with a wall from the rest of the team. Continuous Delivery switches the role of QA team to test automation and exploratory testing team roles. In this setup, QA is part of dev planning and takes essential part in fast and continuous delivery of the product changes into the production.]]>
QA teams are traditionally part of IT departments, but forms own silo that is separated with a wall from the rest of the team. Continuous Delivery switches the role of QA team to test automation and exploratory testing team roles. In this setup, QA is part of dev planning and takes essential part in fast and continuous delivery of the product changes into the production.]]> Sat, 11 Nov 2017 18:36:35 GMT /slideshow/role-of-qa-in-continuous-delivery/81903424 lfryc@slideshare.net(lfryc) Role of QA in Continuous Delivery lfryc QA teams are traditionally part of IT departments, but forms own silo that is separated with a wall from the rest of the team. Continuous Delivery switches the role of QA team to test automation and exploratory testing team roles. In this setup, QA is part of dev planning and takes essential part in fast and continuous delivery of the product changes into the production. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/roleofqaincontinuousdelivery-171111183635-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> QA teams are traditionally part of IT departments, but forms own silo that is separated with a wall from the rest of the team. Continuous Delivery switches the role of QA team to test automation and exploratory testing team roles. In this setup, QA is part of dev planning and takes essential part in fast and continuous delivery of the product changes into the production.

Role of QA in Continuous Delivery from Lukáš Fryč

]]> 570 2 https://cdn.slidesharecdn.com/ss_thumbnails/roleofqaincontinuousdelivery-171111183635-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Arquillian: Helping web developers and QA get along /slideshow/lfryc-arqhandout/34827687 lfryc-arq-handout-140518145612-phpapp02
Modern development practices include testing our Web applications as a fundamental part of the application development lifecycle. Web UIs though can be particularly difficult to test with basic tools. Arquillian is an award-winning integration testing framework and Selenium WebDriver is an outstanding tool for UI test automation. Together they offer a base for high-quality tests. This session looks to the Arquillian Universe for help. Equipped with the Arquillian extensions - Drone, Graphene and Warp - we will show you tests that cover both client-side (REST) and server-rendered (JSF) web applications. With a single test it is now possible to assert state (both in the server and on the client) at arbitrary points within the request lifecycle! We will look at current best practices for how to achieve a rapid turnaround when doing test development by minimizing the effort required to write tests, and thereby increase productivity and thus making these tests future-proof. Additionally we will show tools and techniques that provide a separation of concerns between test authors (developers) and test automators (QA). How to execute a single test in both arbitrary server containers as well as arbitrary client browsers. And how it can enable us to run test suites in constrained environments like cloud-based continuous integration providers.]]>
Modern development practices include testing our Web applications as a fundamental part of the application development lifecycle. Web UIs though can be particularly difficult to test with basic tools. Arquillian is an award-winning integration testing framework and Selenium WebDriver is an outstanding tool for UI test automation. Together they offer a base for high-quality tests. This session looks to the Arquillian Universe for help. Equipped with the Arquillian extensions - Drone, Graphene and Warp - we will show you tests that cover both client-side (REST) and server-rendered (JSF) web applications. With a single test it is now possible to assert state (both in the server and on the client) at arbitrary points within the request lifecycle! We will look at current best practices for how to achieve a rapid turnaround when doing test development by minimizing the effort required to write tests, and thereby increase productivity and thus making these tests future-proof. Additionally we will show tools and techniques that provide a separation of concerns between test authors (developers) and test automators (QA). How to execute a single test in both arbitrary server containers as well as arbitrary client browsers. And how it can enable us to run test suites in constrained environments like cloud-based continuous integration providers.]]> Sun, 18 May 2014 14:56:12 GMT /slideshow/lfryc-arqhandout/34827687 lfryc@slideshare.net(lfryc) Arquillian: Helping web developers and QA get along lfryc Modern development practices include testing our Web applications as a fundamental part of the application development lifecycle. Web UIs though can be particularly difficult to test with basic tools. Arquillian is an award-winning integration testing framework and Selenium WebDriver is an outstanding tool for UI test automation. Together they offer a base for high-quality tests. This session looks to the Arquillian Universe for help. Equipped with the Arquillian extensions - Drone, Graphene and Warp - we will show you tests that cover both client-side (REST) and server-rendered (JSF) web applications. With a single test it is now possible to assert state (both in the server and on the client) at arbitrary points within the request lifecycle! We will look at current best practices for how to achieve a rapid turnaround when doing test development by minimizing the effort required to write tests, and thereby increase productivity and thus making these tests future-proof. Additionally we will show tools and techniques that provide a separation of concerns between test authors (developers) and test automators (QA). How to execute a single test in both arbitrary server containers as well as arbitrary client browsers. And how it can enable us to run test suites in constrained environments like cloud-based continuous integration providers. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/lfryc-arq-handout-140518145612-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Modern development practices include testing our Web applications as a fundamental part of the application development lifecycle. Web UIs though can be particularly difficult to test with basic tools. Arquillian is an award-winning integration testing framework and Selenium WebDriver is an outstanding tool for UI test automation. Together they offer a base for high-quality tests. This session looks to the Arquillian Universe for help. Equipped with the Arquillian extensions - Drone, Graphene and Warp - we will show you tests that cover both client-side (REST) and server-rendered (JSF) web applications. With a single test it is now possible to assert state (both in the server and on the client) at arbitrary points within the request lifecycle! We will look at current best practices for how to achieve a rapid turnaround when doing test development by minimizing the effort required to write tests, and thereby increase productivity and thus making these tests future-proof. Additionally we will show tools and techniques that provide a separation of concerns between test authors (developers) and test automators (QA). How to execute a single test in both arbitrary server containers as well as arbitrary client browsers. And how it can enable us to run test suites in constrained environments like cloud-based continuous integration providers.

Arquillian: Helping web developers and QA get along from Lukáš Fryč

]]> 1723 2 https://cdn.slidesharecdn.com/ss_thumbnails/lfryc-arq-handout-140518145612-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 JSF 2.2 Deep Dive with RichFaces 5 /slideshow/jsf-22-deep-dive-with-richfaces-5/31030017 lukas-fryc-jsf22-deep-dive-with-richfaces-5-140210061749-phpapp01
JavaServer Faces (JSF) is the portion of the Java EE specification that deals with the rendering of web UIs. A server-side rendering framework, JSF is component centric and nicely encapsulates both visual and non-visual UI elements and provides a health component marketplace. The JSF specification as recently undergone a minor release increment with the release of JSF 2.2. While not the revolution seen with the release of the 2.0 specification, JSF 2.2 does include some new and sought-after features. We’ll cover these new features discussing: View Actions, Faces Flows, HTML 5 support, improved CDI integration, the FileUpload component, Resource library contract, stateless views, and the new window ID. Taking a use-case based approach we’ll see how this laundry list of new features will affect your application development. Finally we’ll look at how the RichFaces component library is leveraging these new capabilities in the upcoming RichFaces 5 release. ]]>
JavaServer Faces (JSF) is the portion of the Java EE specification that deals with the rendering of web UIs. A server-side rendering framework, JSF is component centric and nicely encapsulates both visual and non-visual UI elements and provides a health component marketplace. The JSF specification as recently undergone a minor release increment with the release of JSF 2.2. While not the revolution seen with the release of the 2.0 specification, JSF 2.2 does include some new and sought-after features. We’ll cover these new features discussing: View Actions, Faces Flows, HTML 5 support, improved CDI integration, the FileUpload component, Resource library contract, stateless views, and the new window ID. Taking a use-case based approach we’ll see how this laundry list of new features will affect your application development. Finally we’ll look at how the RichFaces component library is leveraging these new capabilities in the upcoming RichFaces 5 release. ]]> Mon, 10 Feb 2014 06:17:49 GMT /slideshow/jsf-22-deep-dive-with-richfaces-5/31030017 lfryc@slideshare.net(lfryc) JSF 2.2 Deep Dive with RichFaces 5 lfryc JavaServer Faces (JSF) is the portion of the Java EE specification that deals with the rendering of web UIs. A server-side rendering framework, JSF is component centric and nicely encapsulates both visual and non-visual UI elements and provides a health component marketplace. The JSF specification as recently undergone a minor release increment with the release of JSF 2.2. While not the revolution seen with the release of the 2.0 specification, JSF 2.2 does include some new and sought-after features. We’ll cover these new features discussing: View Actions, Faces Flows, HTML 5 support, improved CDI integration, the FileUpload component, Resource library contract, stateless views, and the new window ID. Taking a use-case based approach we’ll see how this laundry list of new features will affect your application development. Finally we’ll look at how the RichFaces component library is leveraging these new capabilities in the upcoming RichFaces 5 release. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/lukas-fryc-jsf22-deep-dive-with-richfaces-5-140210061749-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> JavaServer Faces (JSF) is the portion of the Java EE specification that deals with the rendering of web UIs. A server-side rendering framework, JSF is component centric and nicely encapsulates both visual and non-visual UI elements and provides a health component marketplace. The JSF specification as recently undergone a minor release increment with the release of JSF 2.2. While not the revolution seen with the release of the 2.0 specification, JSF 2.2 does include some new and sought-after features. We’ll cover these new features discussing: View Actions, Faces Flows, HTML 5 support, improved CDI integration, the FileUpload component, Resource library contract, stateless views, and the new window ID. Taking a use-case based approach we’ll see how this laundry list of new features will affect your application development. Finally we’ll look at how the RichFaces component library is leveraging these new capabilities in the upcoming RichFaces 5 release.

JSF 2.2 Deep Dive with RichFaces 5 from Lukáš Fryč

]]> 1889 2 https://cdn.slidesharecdn.com/ss_thumbnails/lukas-fryc-jsf22-deep-dive-with-richfaces-5-140210061749-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Web Components: Rethinking Web App Development /slideshow/lukas-frycrethinkingwebappdevelopmentwithwebcomponents/31029903 lukas-fryc-rethinking-web-app-development-with-web-components-140210061425-phpapp01
Web Components is an emerging umbrella of standards that fundamentally changes the way we compose our web applications. Web Components abstract away the complexity introduced when using low-level building blocks such as HTML, CSS and JavaScript. This complexity is usually handled on the level of web frameworks, where we can perceive few phenomenons: web frameworks usually it’s own way of how to work with low-level APIs, maintains custom UI widget suites, lock us in a particular solution. What about inventing some common denominator that could frameworks and app developers built upon? Web Components are essentially a set of improvements that are being added to the web platform: HTML Imports, Shadow DOM, <template>, custom elements, decorators. All of these APIs are on their way to becoming standards. But can we leverage them already? Thanks to polyfill libraries like Polymer we can leverage those new APIs right away! Thanks to Web Components, the web will get a new common denominator which kills fragmentation and encourages reuse and portability of user interfaces.]]>
Web Components is an emerging umbrella of standards that fundamentally changes the way we compose our web applications. Web Components abstract away the complexity introduced when using low-level building blocks such as HTML, CSS and JavaScript. This complexity is usually handled on the level of web frameworks, where we can perceive few phenomenons: web frameworks usually it’s own way of how to work with low-level APIs, maintains custom UI widget suites, lock us in a particular solution. What about inventing some common denominator that could frameworks and app developers built upon? Web Components are essentially a set of improvements that are being added to the web platform: HTML Imports, Shadow DOM, <template>, custom elements, decorators. All of these APIs are on their way to becoming standards. But can we leverage them already? Thanks to polyfill libraries like Polymer we can leverage those new APIs right away! Thanks to Web Components, the web will get a new common denominator which kills fragmentation and encourages reuse and portability of user interfaces.]]> Mon, 10 Feb 2014 06:14:25 GMT /slideshow/lukas-frycrethinkingwebappdevelopmentwithwebcomponents/31029903 lfryc@slideshare.net(lfryc) Web Components: Rethinking Web App Development lfryc Web Components is an emerging umbrella of standards that fundamentally changes the way we compose our web applications. Web Components abstract away the complexity introduced when using low-level building blocks such as HTML, CSS and JavaScript. This complexity is usually handled on the level of web frameworks, where we can perceive few phenomenons: web frameworks usually it’s own way of how to work with low-level APIs, maintains custom UI widget suites, lock us in a particular solution. What about inventing some common denominator that could frameworks and app developers built upon? Web Components are essentially a set of improvements that are being added to the web platform: HTML Imports, Shadow DOM, <template>, custom elements, decorators. All of these APIs are on their way to becoming standards. But can we leverage them already? Thanks to polyfill libraries like Polymer we can leverage those new APIs right away! Thanks to Web Components, the web will get a new common denominator which kills fragmentation and encourages reuse and portability of user interfaces. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/lukas-fryc-rethinking-web-app-development-with-web-components-140210061425-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Web Components is an emerging umbrella of standards that fundamentally changes the way we compose our web applications. Web Components abstract away the complexity introduced when using low-level building blocks such as HTML, CSS and JavaScript. This complexity is usually handled on the level of web frameworks, where we can perceive few phenomenons: web frameworks usually it’s own way of how to work with low-level APIs, maintains custom UI widget suites, lock us in a particular solution. What about inventing some common denominator that could frameworks and app developers built upon? Web Components are essentially a set of improvements that are being added to the web platform: HTML Imports, Shadow DOM, &lt;template>, custom elements, decorators. All of these APIs are on their way to becoming standards. But can we leverage them already? Thanks to polyfill libraries like Polymer we can leverage those new APIs right away! Thanks to Web Components, the web will get a new common denominator which kills fragmentation and encourages reuse and portability of user interfaces.

Web Components: Rethinking Web App Development from Lukáš Fryč

]]> 1250 3 https://cdn.slidesharecdn.com/ss_thumbnails/lukas-fryc-rethinking-web-app-development-with-web-components-140210061425-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Web Technologies in Java EE 7 /slideshow/web-technologies-in-java-ee-7/29109265 web-technologies-in-java-ee-131211082145-phpapp02
]]>
]]> Wed, 11 Dec 2013 08:21:45 GMT /slideshow/web-technologies-in-java-ee-7/29109265 lfryc@slideshare.net(lfryc) Web Technologies in Java EE 7 lfryc <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/web-technologies-in-java-ee-131211082145-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br>

Web Technologies in Java EE 7 from Lukáš Fryč

]]> 2181 5 https://cdn.slidesharecdn.com/ss_thumbnails/web-technologies-in-java-ee-131211082145-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Designing Top-Class Test Suites for Web Applications /slideshow/designing-topclass-test-suites-for-web-applications/12921486 arquillian-designing-top-class-test-suites-120514030330-phpapp01
The evolution which came with the Arquillian, award-winning integration test framework, and Selenium, outstanding tool for UI automation, allows to write high-quality tests. But these technologies can’t save the world by themselves, since they are leaving too many questions open: * Does Selenium cover everything? It covers page transitions, a simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive? What if you could fill all the above gaps?]]>
The evolution which came with the Arquillian, award-winning integration test framework, and Selenium, outstanding tool for UI automation, allows to write high-quality tests. But these technologies can’t save the world by themselves, since they are leaving too many questions open: * Does Selenium cover everything? It covers page transitions, a simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive? What if you could fill all the above gaps?]]> Mon, 14 May 2012 03:03:29 GMT /slideshow/designing-topclass-test-suites-for-web-applications/12921486 lfryc@slideshare.net(lfryc) Designing Top-Class Test Suites for Web Applications lfryc The evolution which came with the Arquillian, award-winning integration test framework, and Selenium, outstanding tool for UI automation, allows to write high-quality tests. But these technologies can’t save the world by themselves, since they are leaving too many questions open: * Does Selenium cover everything? It covers page transitions, a simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive? What if you could fill all the above gaps? <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/arquillian-designing-top-class-test-suites-120514030330-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> The evolution which came with the Arquillian, award-winning integration test framework, and Selenium, outstanding tool for UI automation, allows to write high-quality tests. But these technologies can’t save the world by themselves, since they are leaving too many questions open: * Does Selenium cover everything? It covers page transitions, a simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive? What if you could fill all the above gaps?

Designing Top-Class Test Suites for Web Applications from Lukáš Fryč

]]> 1155 5 https://cdn.slidesharecdn.com/ss_thumbnails/arquillian-designing-top-class-test-suites-120514030330-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Going mobile with RichFaces /slideshow/going-mobile-with-richfaces/12921155 richfaces-going-mobile-handout-120514022759-phpapp02
The rise of portable devices last year shows how important is making applications compatible with mobiles. When it comes to web applications, JSF offers the same strong background for mobile development as it does for desktop applications: an extensible framework with a widely-accepted development model, allowing reuse of JSF programming skills and technologies on the mobile platform. RichFaces 4.1 goes behind concepts brought by JSF and provides developer with framework which makes your applications ready for mobile devices and offers you as rich component suite as for desktop environments. Lukas is going to show you how the RichFaces Showcase was turned into an application for portable devices, how a light-weight javascript framework was designed for making RichFaces applications mobile ready, the principles of an one-page application design and what are the necessary optimizations for making RichFaces applications run on mobile devices properly.]]>
The rise of portable devices last year shows how important is making applications compatible with mobiles. When it comes to web applications, JSF offers the same strong background for mobile development as it does for desktop applications: an extensible framework with a widely-accepted development model, allowing reuse of JSF programming skills and technologies on the mobile platform. RichFaces 4.1 goes behind concepts brought by JSF and provides developer with framework which makes your applications ready for mobile devices and offers you as rich component suite as for desktop environments. Lukas is going to show you how the RichFaces Showcase was turned into an application for portable devices, how a light-weight javascript framework was designed for making RichFaces applications mobile ready, the principles of an one-page application design and what are the necessary optimizations for making RichFaces applications run on mobile devices properly.]]> Mon, 14 May 2012 02:27:58 GMT /slideshow/going-mobile-with-richfaces/12921155 lfryc@slideshare.net(lfryc) Going mobile with RichFaces lfryc The rise of portable devices last year shows how important is making applications compatible with mobiles. When it comes to web applications, JSF offers the same strong background for mobile development as it does for desktop applications: an extensible framework with a widely-accepted development model, allowing reuse of JSF programming skills and technologies on the mobile platform. RichFaces 4.1 goes behind concepts brought by JSF and provides developer with framework which makes your applications ready for mobile devices and offers you as rich component suite as for desktop environments. Lukas is going to show you how the RichFaces Showcase was turned into an application for portable devices, how a light-weight javascript framework was designed for making RichFaces applications mobile ready, the principles of an one-page application design and what are the necessary optimizations for making RichFaces applications run on mobile devices properly. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/richfaces-going-mobile-handout-120514022759-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> The rise of portable devices last year shows how important is making applications compatible with mobiles. When it comes to web applications, JSF offers the same strong background for mobile development as it does for desktop applications: an extensible framework with a widely-accepted development model, allowing reuse of JSF programming skills and technologies on the mobile platform. RichFaces 4.1 goes behind concepts brought by JSF and provides developer with framework which makes your applications ready for mobile devices and offers you as rich component suite as for desktop environments. Lukas is going to show you how the RichFaces Showcase was turned into an application for portable devices, how a light-weight javascript framework was designed for making RichFaces applications mobile ready, the principles of an one-page application design and what are the necessary optimizations for making RichFaces applications run on mobile devices properly.

Going mobile with RichFaces from Lukáš Fryč

]]> 4354 4 https://cdn.slidesharecdn.com/ss_thumbnails/richfaces-going-mobile-handout-120514022759-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 RichFaces CDK: Rapid JSF Component Development /slideshow/richfaces-cdk-rapid-jsf-component-development/11990563 cdk-handout-120313114853-phpapp01
JSF component libraries provide you with a solid basis for building enterprise UIs as they are covering most common use cases. But what can you do in a case that no existing component fits your project requirements? There are many JavaScript component projects which offer together nearly infinite possibilities. But it might not be evident that leveraging these JavaScript frameworks is as easy as writing plain old HTML code, separating component and page development efforts. But how to wrap these components to fit into JSF eco-system? That’s exactly where RichFaces CDK comes into play.]]>
JSF component libraries provide you with a solid basis for building enterprise UIs as they are covering most common use cases. But what can you do in a case that no existing component fits your project requirements? There are many JavaScript component projects which offer together nearly infinite possibilities. But it might not be evident that leveraging these JavaScript frameworks is as easy as writing plain old HTML code, separating component and page development efforts. But how to wrap these components to fit into JSF eco-system? That’s exactly where RichFaces CDK comes into play.]]> Tue, 13 Mar 2012 11:48:51 GMT /slideshow/richfaces-cdk-rapid-jsf-component-development/11990563 lfryc@slideshare.net(lfryc) RichFaces CDK: Rapid JSF Component Development lfryc JSF component libraries provide you with a solid basis for building enterprise UIs as they are covering most common use cases. But what can you do in a case that no existing component fits your project requirements? There are many JavaScript component projects which offer together nearly infinite possibilities. But it might not be evident that leveraging these JavaScript frameworks is as easy as writing plain old HTML code, separating component and page development efforts. But how to wrap these components to fit into JSF eco-system? That’s exactly where RichFaces CDK comes into play. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/cdk-handout-120313114853-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> JSF component libraries provide you with a solid basis for building enterprise UIs as they are covering most common use cases. But what can you do in a case that no existing component fits your project requirements? There are many JavaScript component projects which offer together nearly infinite possibilities. But it might not be evident that leveraging these JavaScript frameworks is as easy as writing plain old HTML code, separating component and page development efforts. But how to wrap these components to fit into JSF eco-system? That’s exactly where RichFaces CDK comes into play.

RichFaces CDK: Rapid JSF Component Development from Lukáš Fryč

]]> 2485 3 https://cdn.slidesharecdn.com/ss_thumbnails/cdk-handout-120313114853-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Arquillian: Effective tests from the client to the server /slideshow/arquillian-effective-tests-from-the-client-to-the-server/11990472 arq2-handout-120313114306-phpapp01
Tools like Selenium, an outstanding tool for UI test automation, and Arquillian, an award-winning integration testing framework, offer a base for high-quality tests which are crucial for a web app development. However writing UI tests and covering server-side logic leaves many questions open: * Does Selenium cover everything? Page transitions, simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive?]]>
Tools like Selenium, an outstanding tool for UI test automation, and Arquillian, an award-winning integration testing framework, offer a base for high-quality tests which are crucial for a web app development. However writing UI tests and covering server-side logic leaves many questions open: * Does Selenium cover everything? Page transitions, simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive?]]> Tue, 13 Mar 2012 11:43:05 GMT /slideshow/arquillian-effective-tests-from-the-client-to-the-server/11990472 lfryc@slideshare.net(lfryc) Arquillian: Effective tests from the client to the server lfryc Tools like Selenium, an outstanding tool for UI test automation, and Arquillian, an award-winning integration testing framework, offer a base for high-quality tests which are crucial for a web app development. However writing UI tests and covering server-side logic leaves many questions open: * Does Selenium cover everything? Page transitions, simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive? <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/arq2-handout-120313114306-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Tools like Selenium, an outstanding tool for UI test automation, and Arquillian, an award-winning integration testing framework, offer a base for high-quality tests which are crucial for a web app development. However writing UI tests and covering server-side logic leaves many questions open: * Does Selenium cover everything? Page transitions, simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive?

Arquillian: Effective tests from the client to the server from Lukáš Fryč

]]> 1725 4 https://cdn.slidesharecdn.com/ss_thumbnails/arq2-handout-120313114306-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Testing JSF with Arquillian and Selenium /slideshow/testing-jsf-with-arquillian-and-selenium/9335077 testing-jsf-applications-110920035747-phpapp02
Testing of web applications is significant part of development cycle from perspective of both, application development and quality assurance. JSF concepts makes testing of applications simple by separation of concerns, but enforces employing of specific tools for testing business logic and user interface. Lukas covers testing pitas and introduce frameworks which make testing of JSF application a breeze and motivate developers to follow concepts of test-driven development.]]>
Testing of web applications is significant part of development cycle from perspective of both, application development and quality assurance. JSF concepts makes testing of applications simple by separation of concerns, but enforces employing of specific tools for testing business logic and user interface. Lukas covers testing pitas and introduce frameworks which make testing of JSF application a breeze and motivate developers to follow concepts of test-driven development.]]> Tue, 20 Sep 2011 03:57:44 GMT /slideshow/testing-jsf-with-arquillian-and-selenium/9335077 lfryc@slideshare.net(lfryc) Testing JSF with Arquillian and Selenium lfryc Testing of web applications is significant part of development cycle from perspective of both, application development and quality assurance. JSF concepts makes testing of applications simple by separation of concerns, but enforces employing of specific tools for testing business logic and user interface. Lukas covers testing pitas and introduce frameworks which make testing of JSF application a breeze and motivate developers to follow concepts of test-driven development. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testing-jsf-applications-110920035747-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Testing of web applications is significant part of development cycle from perspective of both, application development and quality assurance. JSF concepts makes testing of applications simple by separation of concerns, but enforces employing of specific tools for testing business logic and user interface. Lukas covers testing pitas and introduce frameworks which make testing of JSF application a breeze and motivate developers to follow concepts of test-driven development.

Testing JSF with Arquillian and Selenium from Lukáš Fryč

]]> 8450 6 https://cdn.slidesharecdn.com/ss_thumbnails/testing-jsf-applications-110920035747-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 RichFaces 4 rolling to Mobile Era /slideshow/richfaces-4-rolling-to-mobile-era/9334957 richfaces4-rolling-into-mobile-era-110920034958-phpapp01
RichFaces 4 rolling to Mobile Era A session at JSF and RichFaces Workshop/Conference Mobile devices and smart phones are rapidly becoming the primary web client for significant amount of users. For the web developers it represents new area where they should focus when developing applications. They need to handle device specifics as feature support and display possibilities. RichFaces is opening doors for engineers which are focused on application development and rely on framework to handle consequences. RichFaces comprises suite of component which is optimized for use on both, mobile and desktop clients. Lukas discuss where HTML5 and CSS3 fits into the picture and how can JSF and RichFaces ]]>
RichFaces 4 rolling to Mobile Era A session at JSF and RichFaces Workshop/Conference Mobile devices and smart phones are rapidly becoming the primary web client for significant amount of users. For the web developers it represents new area where they should focus when developing applications. They need to handle device specifics as feature support and display possibilities. RichFaces is opening doors for engineers which are focused on application development and rely on framework to handle consequences. RichFaces comprises suite of component which is optimized for use on both, mobile and desktop clients. Lukas discuss where HTML5 and CSS3 fits into the picture and how can JSF and RichFaces ]]> Tue, 20 Sep 2011 03:49:52 GMT /slideshow/richfaces-4-rolling-to-mobile-era/9334957 lfryc@slideshare.net(lfryc) RichFaces 4 rolling to Mobile Era lfryc RichFaces 4 rolling to Mobile Era A session at JSF and RichFaces Workshop/Conference Mobile devices and smart phones are rapidly becoming the primary web client for significant amount of users. For the web developers it represents new area where they should focus when developing applications. They need to handle device specifics as feature support and display possibilities. RichFaces is opening doors for engineers which are focused on application development and rely on framework to handle consequences. RichFaces comprises suite of component which is optimized for use on both, mobile and desktop clients. Lukas discuss where HTML5 and CSS3 fits into the picture and how can JSF and RichFaces <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/richfaces4-rolling-into-mobile-era-110920034958-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> RichFaces 4 rolling to Mobile Era A session at JSF and RichFaces Workshop/Conference Mobile devices and smart phones are rapidly becoming the primary web client for significant amount of users. For the web developers it represents new area where they should focus when developing applications. They need to handle device specifics as feature support and display possibilities. RichFaces is opening doors for engineers which are focused on application development and rely on framework to handle consequences. RichFaces comprises suite of component which is optimized for use on both, mobile and desktop clients. Lukas discuss where HTML5 and CSS3 fits into the picture and how can JSF and RichFaces

RichFaces 4 rolling to Mobile Era from Lukáš Fryč

]]> 976 1 https://cdn.slidesharecdn.com/ss_thumbnails/richfaces4-rolling-into-mobile-era-110920034958-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-lfryc-48x48.jpg?cb=1523147145 https://cdn.slidesharecdn.com/ss_thumbnails/roleofqaincontinuousdelivery-171111183635-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/role-of-qa-in-continuous-delivery/81903424 Role of QA in Continuo... https://cdn.slidesharecdn.com/ss_thumbnails/lfryc-arq-handout-140518145612-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/lfryc-arqhandout/34827687 Arquillian: Helping we... https://cdn.slidesharecdn.com/ss_thumbnails/lukas-fryc-jsf22-deep-dive-with-richfaces-5-140210061749-phpapp01-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/jsf-22-deep-dive-with-richfaces-5/31030017 JSF 2.2 Deep Dive with...