The document discusses the principles of progressive enhancement and provides examples of how to implement it. Progressive enhancement involves building web applications that provide basic functionality to all users and then enhance the experience for those with newer browsers and capabilities. It emphasizes testing for support before applying enhancements and avoiding the need to degrade functionality. This approach allows web applications to work for all users while taking advantage of newer features where available.
Top 13 Mistakes Committed by Angular Java script DevelopersSarah Elson
According to a survey conducted by Libscore (A JavaScript analytics service) in 2016, nearly 12,000 websites out of a million were operating using Angular JavaScript. These also include some established firms like Wolfram Alpha, Sprint, ABC news, Walgreens and Intel. Angular JavaScript is a JavaScript-based open-source front-end web application framework to address the problems encountered in developing single-page applications.
These slides are from my talk at the JSinSA (http://www.jsinsa.com/). This talk covers things I want people to know about Microsoft & JavaScript and highlights my favourite features & tools!
Video: http://youtu.be/KIPo3Rct1E4
More: http://sadev.co.za/content/visual%20studio%20%3C3%20javascript
Testing is a prolonged process and with the increasing demand, enterprises have started depending on it for their daily functioning's. Creating a perfect application with error free codes is seldom easy. Here are a few common mistakes that programmers make during the testing automation process along with tips to avoid them.
Top 13 Mistakes Committed by Angular Java script DevelopersSarah Elson
According to a survey conducted by Libscore (A JavaScript analytics service) in 2016, nearly 12,000 websites out of a million were operating using Angular JavaScript. These also include some established firms like Wolfram Alpha, Sprint, ABC news, Walgreens and Intel. Angular JavaScript is a JavaScript-based open-source front-end web application framework to address the problems encountered in developing single-page applications.
These slides are from my talk at the JSinSA (http://www.jsinsa.com/). This talk covers things I want people to know about Microsoft & JavaScript and highlights my favourite features & tools!
Video: http://youtu.be/KIPo3Rct1E4
More: http://sadev.co.za/content/visual%20studio%20%3C3%20javascript
Testing is a prolonged process and with the increasing demand, enterprises have started depending on it for their daily functioning's. Creating a perfect application with error free codes is seldom easy. Here are a few common mistakes that programmers make during the testing automation process along with tips to avoid them.
Page-Object pattern is very commonly used when implementing Automation frameworks. However, as the scale of the framework grows, there is a limitation on how much reusability really happens. It inherently becomes very difficult to separate the test intent from the business domain.
I talk about this problem, and the solution I have been using - Business Layer - Page-Object pattern, which has helped me keep my code DRY.
For more details (links to slides, etc.), see my blog: http://goo.gl/biRn4n
* Blog post: http://wakeupandcode.com/asp-net-and-unit-testing
Learn how you can use Unit Testing to build robust web applications in ASP.NET!
Anyone can learn how to build web applications.... but how robust is your application in the real world? With Unit Testing, you can write code to test your application code to detect and prevent bugs!
Overview of the need for APIs in order to build RIAs with Adobe Flex. Also a breif walkthrough on how to create Mashups with Flex and Kapow Mashup Server.
Dreamforce 15 presentation on jsForce in Action. See accompanying github repository for source code and installation instructions.
Github Repo: https://github.com/gbockus/jsForceInAction
Developing a web or mobile application takes a lot of effort, but all that effort can go down the drain quickly if you improperly load test the application or completely skip testing. Load testing applications is important and a necessary step in the pre-production stage.
New applications, ones that have not yet made it to the production stage, likely don’t have a performance benchmark established. You don’t typically know what to expect with a new app, which is why before you do a larger load test on any application you first do some baseline testing. This will allow you to establish some benchmarks and pick out any performance issues before you place a larger load on the app. For example, if your app crashes with just five users, you have a problem. Look to the application architects to determine if any service level agreements have been set for the application during design.
Once you have done some baseline testing you are ready to load test your application to determine its performance levels under heavier load. Here are 5 essential tips for starting load testing on an application.
Continuous Testing Meets the Classroom at Code.orgSauce Labs
Code.org's Brian Jordan, a Software Engineer, takes the audience for a fun tour of Code.org’s continuous, automated testing suite. Brian discusses how Code.org approaches testing throughout the product development cycle, given their unique testing challenges—developing interactive, game-like curriculum for just the types of browsers you’d expect to find in school computer labs—from Internet Explorer 9 to iPads across 40+ languages.
Web automation with Selenium for software engineersMikalai Alimenkou
We all know Selenium/WebDriver more as testing automation tool. But in reality this is just a tool/library to automate operations with different browsers using similar API from different languages. In this talk I will show how to use different parts of Selenium product family for day to day tasks of developer, QA engineer or even Project Manager. Hope after visiting this talk you will spend less time on boring procedures and improve many things in your current development process.
Don’t Go over the Waterfall: Keep Agile Testing AgileTechWell
All too often an agile iteration resembles a mini-waterfall cycle with developers coding for the duration of the iteration and then throwing code “over the wall” to the test team. This results in the all-too-familiar “test squeeze” with testers often testing code after the iteration has already finished. When testing occurs after an iteration’s end, the agile principle of potentially releasable is violated and negatively impacts the next iteration. To avoid these problems we must ensure that all testing is completed before the end of the iteration. But how can we achieve this? Aaron Barrett explains that the solution lies in the planning and processes that govern the agile team. Learn proven strategies that allow your test teams to move testing back inside the iteration and take back a plan to keep you from going over the waterfall.
Page-Object pattern is very commonly used when implementing Automation frameworks. However, as the scale of the framework grows, there is a limitation on how much reusability really happens. It inherently becomes very difficult to separate the test intent from the business domain.
I talk about this problem, and the solution I have been using - Business Layer - Page-Object pattern, which has helped me keep my code DRY.
For more details (links to slides, etc.), see my blog: http://goo.gl/biRn4n
* Blog post: http://wakeupandcode.com/asp-net-and-unit-testing
Learn how you can use Unit Testing to build robust web applications in ASP.NET!
Anyone can learn how to build web applications.... but how robust is your application in the real world? With Unit Testing, you can write code to test your application code to detect and prevent bugs!
Overview of the need for APIs in order to build RIAs with Adobe Flex. Also a breif walkthrough on how to create Mashups with Flex and Kapow Mashup Server.
Dreamforce 15 presentation on jsForce in Action. See accompanying github repository for source code and installation instructions.
Github Repo: https://github.com/gbockus/jsForceInAction
Developing a web or mobile application takes a lot of effort, but all that effort can go down the drain quickly if you improperly load test the application or completely skip testing. Load testing applications is important and a necessary step in the pre-production stage.
New applications, ones that have not yet made it to the production stage, likely don’t have a performance benchmark established. You don’t typically know what to expect with a new app, which is why before you do a larger load test on any application you first do some baseline testing. This will allow you to establish some benchmarks and pick out any performance issues before you place a larger load on the app. For example, if your app crashes with just five users, you have a problem. Look to the application architects to determine if any service level agreements have been set for the application during design.
Once you have done some baseline testing you are ready to load test your application to determine its performance levels under heavier load. Here are 5 essential tips for starting load testing on an application.
Continuous Testing Meets the Classroom at Code.orgSauce Labs
Code.org's Brian Jordan, a Software Engineer, takes the audience for a fun tour of Code.org’s continuous, automated testing suite. Brian discusses how Code.org approaches testing throughout the product development cycle, given their unique testing challenges—developing interactive, game-like curriculum for just the types of browsers you’d expect to find in school computer labs—from Internet Explorer 9 to iPads across 40+ languages.
Web automation with Selenium for software engineersMikalai Alimenkou
We all know Selenium/WebDriver more as testing automation tool. But in reality this is just a tool/library to automate operations with different browsers using similar API from different languages. In this talk I will show how to use different parts of Selenium product family for day to day tasks of developer, QA engineer or even Project Manager. Hope after visiting this talk you will spend less time on boring procedures and improve many things in your current development process.
Don’t Go over the Waterfall: Keep Agile Testing AgileTechWell
All too often an agile iteration resembles a mini-waterfall cycle with developers coding for the duration of the iteration and then throwing code “over the wall” to the test team. This results in the all-too-familiar “test squeeze” with testers often testing code after the iteration has already finished. When testing occurs after an iteration’s end, the agile principle of potentially releasable is violated and negatively impacts the next iteration. To avoid these problems we must ensure that all testing is completed before the end of the iteration. But how can we achieve this? Aaron Barrett explains that the solution lies in the planning and processes that govern the agile team. Learn proven strategies that allow your test teams to move testing back inside the iteration and take back a plan to keep you from going over the waterfall.
A brownbag presentation at IPC media in London about the need to use libraries to make web development much less random and more professional. Get the audio at: http://www.archive.org/details/ProfessionalWebDevelopmentWithLibraries
JavaScript is the most widely used language cross platforms. This talk will analyze the security concerns from past to present with a peek to the future of this important language. This talk was presented as Keynote at CyberCamp Espana 2014.
Design Systems - Develop multiple features across multiple platforms
Isomorphic Systems - Javascript rendered on backend
Shared Codebases - Component library, multiple teams, multiple platforms
Seperation of Concerns - Services seperated out, easy to migrate
Unit Testing - Much much needed
State Management - Seperate out what application is doing from UI Logic. (Thanks to Facebook)
Immutability -Core Javascript Principle we use in day to day life.
Different ways to handle Asynchronous behavior - Async/await, observables, promises, etc.
Todays web front-end applications architecture. All resources shared at the end of presentation.
Full sources on:
https://lnkd.in/gyQuFKK
https://lnkd.in/gZK8Sp3
Appium Interview Questions and Answers | EdurekaEdureka!
**Appium Certification Training: https://www.edureka.co/appium-training-mobile-automation-testing **
This Edureka PPT on Top 50 Appium Interview Question will help you to prepare yourself for Software Testing Interviews. It covers questions for beginners, intermediate and experienced professionals.
Selenium Testing playlist: https://goo.gl/NmuzXE
Selenium Blog Series: http://bit.ly/2B7C3QR
Software Testing Blog Series: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Similar to Understanding progressive enhancement - yuiconf2010 (20)
We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.
PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.
Keynote at halfstackconf 2017 discussing the falsehood of the idea that in order to survive the automation evolution everybody needs to learn how to code. Machines can code, too.
35. Complex software will always have
vulnerabilities and motivated
adversaries will always work to
discover and take advantage of
them. There is no evidence that
upgrading away from the latest
fully patched versions of Internet
Explorer to other browsers will
make users more secure.
36. It is not straightforward for HMG
departments to upgrade IE versions
on their systems. Upgrading these
systems to IE8 can be a very large
operation, taking weeks to test and
roll out to all users.
37. To test all the web applications
currently used by HMG departments
can take months at significant
potential cost to the taxpayer. It is
therefore more cost effective in
many cases to continue to use IE6
and rely on other measures, such as
firewalls and malware scanning
software, to further protect public
sector internet users.
38.
39. And this is why we
need progressive
enhancement.
106. Load the IO and Node
module.
Define the configuration
for the Ajax call.
On submission of the form
load the validate.php file
with the config and don’t
send off the form.
107. If the Ajax call was a
success, replace the
innerHTML of the form with
the HTML returned from
validate.php
108. In addition to that, focus
on the first element with an
error message - this helps
with assistive technology.