When anyone speaks about test automation, people tend to co-relate to functional and regression testing. 

People spend lots of effort and money in test automation and to see better ROI on functional and regression areas, my point is why are we just restricting ourselves only to functional automation, why cannot we move ahead and use test automation for non-functional aspects as well? 

Sounds Interesting???

Considering the current maturity of Automated Testing, I have come up with few Value Added Services (VAS) for test automation, which adds more than just developing automation scripts. Imagine creating an Test Automation which will not just check for the functionality of the application, but also checks for security, page performance and accessibility.

This presentation presents them using selenium test automation. 

I have created tools like Accessibility Cop, Page Speedometer and XSS Detective which uses selenium either to retrieve details or use it as a mechanism for web crawling to find the non functional bugs in your web application. 

Would like to demonstrate these tools and show case the ROI being achieved using these tools 

 

 

 

 

 

 
1 favorite thumb_down thumb_up 5 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Introduction to VAS
  • VAS Applications
    • Accessibility Cop
      • This service would help you find the DOM related accessibility flaws in your application
    • XSS Detective 
      • This service would help you to find the security flaws in your application
    • Page Speedometer 
      • This service would help you understand and report client side performance 
      • Additionally could be used as a platform for performance testing of your application
    • Demo of VAS applications 
  • Integration of VAS applications with any Selenium Framework 
    • How easily we could integrate with any selenium framework 
  • Summary 
  • Q&A

 

 

Learning Outcome

There could many outcomes from this session, if you see leveraging your current automation framework to non functional areas is the major learning from this session. However to go with it a anyone could understand 

  • Importance of Non-Functional testing
  • ROI of automating NFT
  • Basic understanding of using selenium 
    • For accessibility testing 
    • For security testing 
    • For understanding client side performance 

Target Audience

Everyone

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Surendran Ethiraj
    By Surendran Ethiraj  ~  1 year ago
    reply Reply

    Thanks Anand and Dave , would change the timing to 45 mins as suggested. I would be more than happy to answer the queries and explain more on the proposal. 

    Thanks again for your support. 

     

  • Anand Bagmar
    By Anand Bagmar  ~  1 year ago
    reply Reply

    Hi,

    The tools you are speaking of, if someone is interested, how can they use the same? I am assuming they are available for public use and not propriety, correct?

    Is 20 min sufficient to demo all the different aspects you are talking about? Do you think 45 min would be better suited for this?

    • Surendran Ethiraj
      By Surendran Ethiraj  ~  1 year ago
      reply Reply

      Hi Anand,

      The tools are actually interfaces which could be plugged in with any framework, the idea of this presentation is to show case the use of selenium on non-functional aspects along with your regular automation. 

      Regarding the 20 min presentation, I am sure I could manage a demo with my content on the specified time. These interfaces would work in parallel after triggering so I could complete my demo in 5 mins and I could use the remaining for presenting the content and the results. 

      Regarding the availability of interfaces, right now I have not open sourced the interfaces, it is still with me, would try to do it sooner. 

      • Anand Bagmar
        By Anand Bagmar  ~  1 year ago
        reply Reply

        Thanks. 

        As Dave also suggests, I recommend a 45 min session - as there will be good value and discussions around this with the attendees. 

        Lastly - not suggesting you open-source your work (though that would be awesome) - but it is important to share what others can use, not just know about. 

  • Dave Haeffner
    By Dave Haeffner  ~  1 year ago
    reply Reply

    I agree with Anand. A longer session might make more sense if you're able to stretch it out by spending more time on the explanation and not have to rush through the demo. You can also take your time showcasing the code/architecture. There would also be more time for questions at the end (which I'm assuming there will be a good number of).