Selenium is a popular open source test automation tool, so popular it has its own conference event which run for 3 whole days across continents and is attended by hundreds of enthusiastic testers, and people wanting to know more about testing and automation. In my little experience of coaching for last 7 years, i feel what english language has done for common man[those from non english speaking countries] in earning bread and butter and giving them an elite status, selenium has done for manual testers.

Anyone and everyone wants to learn Selenium. The magic of selenium or the flexibility is that it can be learnt with your choice of programming languages. I have taught people Selenium with Java, C#, Python and Ruby largely in past these years. I wish to delve into the world of Javascript now and see what this has to offer to us. So this workshop is for those open minded souls out there who wish to pick up another language and learn, unlearn, relearn selenium with it.

 
 

Outline/Structure of the Workshop

Outline/Structure of the Workshop [480 mins]

  • De-Mystifying JavaScript [180 minutes]
    • Introduction to JS
    • Datatypes in JS
    • DataStructures in JS
    • Loops and Conditional Statement in JS
    • JS Objects and Functions
  • Jump into the world of Selenium [120 minutes]
    • Selenium Projects – IDE, Webdriver and Grid
    • Locators in Selenium
    • Selenium Commands
  • Holy Grail – Selenium WebDriver [180 minutes]
    • Browser through demo AUT
    • Setup webdriver js client libraries
    • Automate 2-3 demo workflows using javascript as language

The entire workshop is hands-on. In every segment we will be having coding exercises. So please ensure the laptops are already ready with the working setup.

Learning Outcome

At the end of the session you should be able to automate 2-3 flows from the demo web application using selenium tool and java script programming language. And you will be guided to your way forward so that you can complete the learning on your own.

Target Audience

If you want to learn, I am here to learn with you.

Prerequisites for Attendees

Laptop with internet connection.

Admin Access to your laptop

Eclipse

Basic Manual Testing Concepts

Basic Web Technologies - HTML, XML, XPATH, CSS, DOM.

JAVA 8 installed.

schedule Submitted 2 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Anand Bagmar
    By Anand Bagmar  ~  3 weeks ago
    reply Reply

    Hi Pallavi,

    Unfortunately, the conference is unable to accept additional full-day workshops due to logistics issues on the conference days. As an alternative, would you be interested in modifying your full-day workshop submission to either a 90-min mini-workshop or a 45 min session which can be reviewed by the program team for selection?

    While we understand modifying the content of a full-day workshop to a 45-min or 90-min is not ideal, at least this way you get a chance to share your learning and knowledge with the attendees.

    If you agree, can you please edit this proposal of your accordingly and drop a note to the program team in form of a comment once updated?

    Regards, Anand

    • Pallavi R Sharma
      By Pallavi R Sharma  ~  3 weeks ago
      reply Reply

      Hi Anand

      i totally understand the concern. It is alright with me if this proposal for workshop cannot be considered for the conference.

      thanks for the review from you and srinivasan.

      -pallavi.

  • Srinivasan Sekar
    By Srinivasan Sekar  ~  1 month ago
    reply Reply

    Hi Pallavi,

    Thanks for proposing this workshop. I don't see a detailed run down of agenda for 480mins. Can you update it there?

    • Pallavi R Sharma
      By Pallavi R Sharma  ~  1 month ago
      reply Reply

      Hello Srinivasan

      I have updated the workshop, and divided the 480 minutes time into three different learning division. The workshop is aimed at beginners primarily people with little or no programming background, but having testing knowledge. 

      Thanks

      Pallavi.

      • Srinivasan Sekar
        By Srinivasan Sekar  ~  4 weeks ago
        reply Reply

        Thanks for the update, Pallavi. I suggest to have coding hats across the day not just only on last 3hours. Having short exercises even on basics is a must have. Running through the theory part of Selenium for next 2hours isn't recommended. I suggest mixup the coding hats across the day along with theory part so people feel the value and experience it at same moment. Please update the same.

        • Pallavi R Sharma
          By Pallavi R Sharma  ~  4 weeks ago
          reply Reply

          The entire session is coding. one cannot teach JS in theory or selenium concepts/ locators in theory. the complete workshop is handson. 

          i just tried to create 'creative' headings... :| looks like didnt work well.. 

          what do you suggest.. 

          • Srinivasan Sekar
            By Srinivasan Sekar  ~  4 weeks ago
            reply Reply

            Good but it doesn't depict the same in above run-down. Attendees take decisions to attend workshop or not by only going over the abstract. I accept title should be impressive but the content distribution also matters as it is a whole day workshop. Remove coding hats on title placed only on final three hours and probably leave a exclusive note saying hands-on exercise on each topic will be helpful for attendees.

            • Pallavi R Sharma
              By Pallavi R Sharma  ~  4 weeks ago
              reply Reply

              Understood Srinivasan, and updated. Please let me know if anything else is required in here. Thanks for the suggestions. 

              • Srinivasan Sekar
                By Srinivasan Sekar  ~  4 weeks ago
                reply Reply

                Looks good to me now, Pallavi. Thanks.

                • Pallavi R Sharma
                  By Pallavi R Sharma  ~  4 weeks ago
                  reply Reply

                  Okay, thanks Srinivasan. 

                  • Srinivasan Sekar
                    By Srinivasan Sekar  ~  4 weeks ago
                    reply Reply

                    Hi Pallavi,

                    Have another query: How many attendees are you targeting? Will you be able to manage it alone? Note: As you know, we expect 400+ attendees for the conference.

                    • Pallavi R Sharma
                      By Pallavi R Sharma  ~  4 weeks ago
                      reply Reply

                      To answer your question, i have a question first, what is the size of the workshop rooms, which are planned for full days? 

                      Will this workshop become part of the main conference? 

                      Or will this be planned seperately?

                      Please let me know about it.

                      We can work under "assumptions" currently for me to understand how to answer the question you have asked. 

                      • Srinivasan Sekar
                        By Srinivasan Sekar  ~  4 weeks ago
                        reply Reply

                        Yes, these workshops are part of the main conference. AFAIK, 90mins workshops can even accommodate ~100 people. I wanted to understand what was the number in mind when you were submitting. 480mins workshop call decisions are with Tech Steering Committee of Selenium as we have not done one before as part of the main conference.

                         

                        • Pallavi R Sharma
                          By Pallavi R Sharma  ~  4 weeks ago
                          reply Reply

                          for a whole day workshop which is part of the main conference, there are some challenges which i see

                          a- people who are part of the workshop, can participate for whole day

                          b- leave after attending few hours

                          c- join in middle 

                          d- are these assumptions correct? 

                          e- because there will be parallel tracks of talks running, and a lot of people will be interested to hear them

                          f- i would like to understand about this first, because this changes then the model of workshop and impacts the way to handle a variable* audience. 

                           

  • Anuradha Sharma
    By Anuradha Sharma  ~  4 weeks ago
    reply Reply
    •  

    I think the submission could be improved by:

    Hi Pallavi,

    You have mentioned 180 mins on JavaScript. But I see, you are covering only basics of JavaScript, then whats the point of attending this workshop. We will pay 4000 INR for this workshop but the kind of JavaScript content is not that impressive.  you are just covering basics:

    • Introduction to JS -- it will take only 5-10 mins
    • Datatypes in JS -- max 15 mins
    • DataStructures in JS  -- can you please write down the topics that you are covering DS/ALGO for Javascript point of view.
    • Loops and Conditional Statement in JS -- max. 15-20 mins
    • JS Objects and Functions -- 30 mins. 

    I am not sure, this workshop is really helpful or not. Audience should be satisfied after attending this workshop. But I really dont see a good value addition after seeing this course content. anyone can learn such Javascript basics from google, then why someone needs to join this workshop?

    Thanks

    Anu


  • Liked Shweta Sharma
    keyboard_arrow_down

    Shweta Sharma / Nikita Jain - Accessibility testing 101

    45 Mins
    Talk
    Beginner

    "This world is such a beautiful place to live in." If you can read the first sentence without any screen readers or assistance, you're privileged. As technologists, shouldn’t we be more empathetic towards differently-abled people and make all parts of our website accessible to them? In my humble opinion, the true power of technology can be identified when it reaches out to people of all kinds having different physical or psychological challenges. We not only legally bound to provide Accessibility but also it should be considered as our moral responsibility.

    As testers, we have a wonderful opportunity to contribute to Accessibility by ensuring that the site is accessible in many different ways. Although it is impossible to identify all the issues that exist around Accessibility in the world, we are lucky enough to still understand a majority of them. With this understanding, there have been many measures taken in order to make your site accessible. But, don’t forget - we are QA engineers. We got to ensure that the site is accessible as per the standards set by WCAG 2.0 (AA) by testing for accessibility using various tools and techniques.

  • Liked Krishnan Mahadevan
    keyboard_arrow_down

    Krishnan Mahadevan - My experiments with Grid

    45 Mins
    Tutorial
    Intermediate

    Everyone starts off with a simple grid setup which involves a hub and one or more nodes.

    This traditional setup is a good start but the moment one starts to get serious with the selenium grid and decide to house their own selenium grid for their local executions, that is when issues start.

    My experiences with the Selenium grid in the past couple of years has led me to get introduced some of the most prevalent problems with maintaining an in-house selenium grid.

    • Nodes get unhooked randomly due to network glitches.
    • Nodes introduce false failures due to memory leaks.
    • Selenium Grid running out of capacity.
    • Nodes require OS upgrades/patches etc.
    • Needing to deal with auto upgrades by browsers (especially chrome and firefox)

    Some of these issues I managed to fix by building a "Self Healing" Grid wherein the nodes automatically get restarted after they have serviced "n" tests. But that still didn’t solve many of these other problems.

    That was when I felt, what if there was an on-demand selenium grid.

    What if the Grid could do the following ?

    • The Grid auto scales itself in terms of the nodes based on the current load.
    • The Grid does not require a lot of infrastructure to support it.
    • The Grid can plug itself into some of the cloud providers or leverage a solution such as Docker so that the nodes can be spun and shutdown at will.

    That was how the idea of "Just Ask" an on-demand grid was born.

    Just-Ask is an on-demand grid. It has no nodes attached to it.

    It’s designed to spin off nodes on demand, run test against the newly spun off node and after test runs to completion, clean-up the node as well. The node can be backed by anything. It could be Docker (or) it could be a VM running on any of the popular clouds.

    The session aspires to walk the audience through with my experiments with the selenium grid, my learnings on the selenium grid internals and how I used all of that knowledge to build my own On Demand Selenium Grid. What better avenue to share these learnings than a Selenium Conference.

    The session will introduce the audience to the grid internals and their concepts such as

    • What is a Selenium Remote Proxy ? What is it used for? What can you do with it?
    • What is a Hub (or) Node level Servlet ? When would you need one ?
    • All of this followed by a quick demo on "Just Ask", the on-demand grid that I have built and open sourced here: https://github.com/rationaleEmotions/just-ask

  • Liked Amit Rawat
    keyboard_arrow_down

    Amit Rawat - Is Puppeteer better than Selenium

    45 Mins
    Demonstration
    Intermediate

    Puppeteer is a Node js library (developed by Google Chrome team) to control Chrome and Firefox and is getting lot of traction recently because of its amazing capabilities. It has already become so popular that it has got 50K+ stars on Github against Selenium's 15K+ stars.

    In the last Google I/O event, this tool's capability has been showcased and it has been perceived as the next generation Web Test Automation Tool.

    Is Puppeteer better than Selenium? The answer is 'No', and I will cover 'why' in detail during this talk. I will show some live examples to demonstrate that Selenium can also do all those advance things which Puppeteer promises to do.

  • Liked Vaibhav Singhal
    keyboard_arrow_down

    Vaibhav Singhal - Helping Test & Test Automation with AI-ML

    Vaibhav Singhal
    Vaibhav Singhal
    Test Lead
    ToTheNew
    schedule 2 months ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    "To implement or use AI (mostly creating a solution to help in testing) you don't need to be an expert or some certified data scientist etc. My talk revolves around how being a normal automation tester, we see some challenges and with limited knowledge, we start leveraging AI to help in our test. Talk create a mindset and case study how AI may help you in some of your day to day challenges in testing."

    The impact of AI has penetrated our lives and increasing daily. Related to AI-ML existence in Testing, two scenarios are:

    - Testing AI programs

    - AI helping Testing

    This talk is related to later aspects of "AI Helping Testing". There are a number of possible ways how it is impacting and many companies are already working on developing tools around same and many test solutions are already available in market.

    Whenever AI keywords are intercepted, the common image is of "autonomous car, robots" and then the question, how these cars and robots will help us in testing, rather the thought should be these the outputs of AI.

    AI/ML can be leveraged in the number of areas and scenarios to solve and help in our day to day testing activities. This talk would discuss about AI/ML, its impact, some existing solutions available, doing brainstorming ideas, so you can identify in your project. Also, USE CASE how we took AI benefit to solve our Automation problem.

    Use Case - Problem Statement

    1- Multiple automation suites running daily and sharing reports. Each report is having some failures. To do defect triaging for multiple failures is difficult.

    Solution: Displaying consolidated reports of actual and new failures suggested by the prediction model (qa analysis on failures was reduced by 80%) based on classification & Deep learning..

    2- Auto analysis while bug reporting directly to bug management tool.

    Solution: Model predicting the defect is already raised in bug management tool, as per the score it would take appropriate action to create new, update, no action, only notification to team etc.

    Talk includes below takeaways:

    1- Understanding how is AI/ML/Deep learning specifically in software testing.

    2- Brainstorming how to leverage AI to help in your tests.

    3- Initial steps to start for any model.

    4- Tools to leverage

  • Liked Virender Singh
    keyboard_arrow_down

    Virender Singh - Rise of Shadow DOM - Lets solve it through Selenium & WebDriverIO

    45 Mins
    Demonstration
    Beginner

    Shadow DOM is kind of web standard that developers use to encapsulate their custom HTML code and style components so that no other global style components can override their code. It ensures that a component will work in any environment, even if other CSS or JavaScript is run on the page i.e. Shadow DOM hides away the complexity of the components from the rest of the page because it renders separately from main DOM.

    Selenium legacy selectors are not able to interact these custom elements under the shadow DOM so we need java script to interact with shadow DOM elements and we also require JavascriptExecutor interface for their execution.

    We will also talk about the WebdriverIO tool v5.5.0, which implicitly support Shadow DOM elements.

  • Liked Sanjay Kumar
    keyboard_arrow_down

    Sanjay Kumar - ChroPath- Smarter way of writing automation script!!

    Sanjay Kumar
    Sanjay Kumar
    ChroPath Creator
    AutonomIQ
    schedule 3 months ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate
    • Want to save 70-80% manual effort of automation script writing!!
    • Wasting time in verifying xpath one by one?
    • Want to complete automation script without wasting much time?
    • Are you still wasting time in writing english manual test cases?
  • Liked Naveen Khunteta
    keyboard_arrow_down

    Naveen Khunteta - Best Practices to implement the test automation framework starting from Design - To -> Infrastructure - To -> Execution.

    45 Mins
    Talk
    Intermediate

    Best Practices - How to get the best 'Return ON Investment' (ROI) from your Test Automation.

    This has been observed that, most of the test frameworks wont be able to survive due to lack of expertise, no maintenance, no best practices being followed, and finally your test automation will be dead after few months, and there is no "Return ON Investment" from this. This is the most common problem, most of the companies are struggling and finally back to square to the Manual testing.

    My proposal : HOW to leverage your test automation in terms of best practices, best ROI, and how to adopt best automation culture in your organisation.
    I strongly propose some of the important points/suggestions to achieve this in your Organisation/Team.
    1. Test Automation Practices:
    • Design Patterns (Web/Mobile/API)
    • What to Automate/Not to Automate
    2. Common Automation Frameworks at Org Level:
    • How to design Generic Utilities, Libraries and different Components, which can be suitable for all the teams in the same Org.
    • Best practices to design your Tests (Automation).
      • Common Design Patterns
      • Common application level and Page libraries
      • Best Practices to use Assertions in your Tests (How and What to write for assertions). Most of the people don't write proper assertions and this is making your test unreliable and no defects found during execution.
    3. Inclusion of API/Backend libraries in your UI test automation as an external Maven/Gradle Dependencies to avoid un-necessary tasks, some of the important points to be considered here:
    • User Creation from APIs (No need to automate user creation from web/app for all the test cases)
    • API tests are stabled most of the time
    • API calls takes lesser time as compared to web, hence include API calls in your UI/App framework to save time.
    • Less flaky test

    4. Best Code Review Process (Do not merge your code into Master without proper Code Review)

    • Implement PR (PULL Request) Process
    • Static Code Analysis using SonarQube, Cobertura, JACOCO etc..
    • Get the benefits of Best Test Automation Quality Matrices
    • Sometimes, Manual (Functional Tester) should review your code (Assertion, test steps and use cases) to get the best coverage
    5. Quality is A Team responsibility:
    • Developers, POs, Manual QEs and Automation engineers should be included to get an overview of test automation coverage.
    6. Maintenance of the Frameworks
    • After couple of months, it should not make your life miserable if you don't maintain your libraries and framework properly.
    • Do not use Hard Coded values, make it simple and Generic.
    7. Infrastructure Setup for Test Design and Test Execution:
    • Proper Browser - OS lab setup
    • Proper Mobile Labs setup with different Devices - IOT, iOS, Android, iPad, Tablets
    • Proper CI - CD common configuration using Jenkins, Dev Ops, AWS, Docker and Cloud setup
    • Handling multiple Docker nodes using Kubernates (use of Selenoid, GRID on Cloud)
  • Liked Srinivasu gangam
    keyboard_arrow_down

    Srinivasu gangam - Zero Touch Automation using NLP (Natural language processing) & AI

    Srinivasu gangam
    Srinivasu gangam
    Sr Manager
    Cotiviti India
    schedule 3 months ago
    Sold Out!
    45 Mins
    Demonstration
    Intermediate

    Problem Statement:

    As part of SDLC process:

    1. Is your product quality impacted due to a smaller number of QA resources available in the team?
    2. Are you waiting for QA resources to certify your code every time when you deploy? Is this impacting your product lead time (Speed to Market)?
    3. Is your Product delivery timelines are impacted due to last minute defects identified?
    4. Do you have your QA resources only in one location, but you want to “follow-the-sun” approach for Software delivery across multiple locations?
    5. Do you have manual testers who are not skilled in programming, but you want them to execute automated test scripts w/o any training efforts and automation setup?
    6. Would you like your team more agile and cross functional with Delivery?
    7. Would you like to increase your QA team’s productivity while they invest more time in script development rather than script execution?

    If answer is ‘Yes’ for above questions, "Zero touch automation" is the solution for above challenges that we have been facing part of SDLC.

    Solution: Zero touch automation with cutting-edge technologies

    In this session, I will cover how we solved this problem using innovative solutions, Cutting-edge technologies like NLP (Natural language processing), AI & Cloud solutions.

    You will learn how AI, NLP integrated with core automation components to achieve Zero touch automation.

    This solution is not just revolutionary, it is paradigm shift in test automation to get results to your email with detailed analysis of failure categorization with recommended actions to users.

    I will also cover how E2E automation will be driven with decisions taken by machines based on what user is looking for . There is no manual intervention in this process. NLP and AI play key role to help machines to take decisions.

    We will also cover how we empowered developer/release manager/any team member/Manager to trigger the scripts from their cell phone and get the detailed execution report without having any automation software installed in their computer or Phone.

    We will be demonstrating how the request will be initiated from User, understand the need from user using NLP & AI , Fetching the code from bitbucket to select appropriate automation scripts , running them on Selenoid/docker server , storing results to MongoDB , receiving email with test results and Failure analysis.

    What is the value of zero touch automation?

    1. Enable speed to market: Now that Developers does not need to wait for QA resource, Changes can be certified quickly and ready to push to production. Lead time will be significantly reduced.
    2. Increase quality: Now that test automation is easy and it can run multiple times in each environment, most of the defects will be uncovered and addressed before code goes to production.
    3. Ease of test execution: Test execution will be very easy, no automation or framework setup required from user side. Test execution can be done 24*7.
    4. Productivity: Increase QA team’s Productivity to focus more on script development rather than focusing on script execution and failure analysis .
  • Liked Gaurav Singh
    keyboard_arrow_down

    Gaurav Singh - How to build an automation framework with selenium : patterns and practices

    Gaurav Singh
    Gaurav Singh
    Product Engineer
    Go-Jek
    schedule 3 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    With an ever increasing no of businesses being conducted on web the testing need to write automated tests for the app's UI is something that can never be ignored. As you all know Selenium provides an API that enables us to do this quite effectively.

    However, when tasked with setting up the automation framework, there are a lot of questions that arise in the minds of aspiring test developers regardless of what level they are in their career.


    Some of such questions are:

    1. How does one actually go about the business of building a robust and effective automation framework on top of selenium?
    2. What are the elementary building blocks to include in the framework that an aspiring automation developer should know of?
    3. How should we model our tests? XUnit style vs BDD?
    4. Are there good practices, sensible design patterns and abstractions that we can follow in our code?
    5. What are some of the anti patterns/common mistakes we should avoid

    A lot of literature, documentation and blogs exists on these topics on the web already.

    However In this talk,

    I would combine this existing knowledge and my years of experience in building automation frameworks and breakdown these elements and walk you through exactly the sort of decisions/considerations and practices that you can take while starting to implement or improve the UI automation for your team.

    Hope to see you there!

  • Liked Vinayaka Mayura G G
    keyboard_arrow_down

    Vinayaka Mayura G G - Search Relevancy Testing: QA in Machine Learning Models

    Vinayaka Mayura G G
    Vinayaka Mayura G G
    QA
    ThoughtWorks
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    The adoption of Artificial Intelligence is getting more traction, it is in need to enhance QA capabilities to cope up with these skills. Machine Learning is used extensively in retail applications for solving complex problems, one of them is solving the search relevancy. Showing the appropriate results for the user is important for the conversion rate to go high. As Machine Learning poses different challenges such as a Test Oracle, Fairness, Correctness and Robustness to do QA, We may need to follow different approaches and testing techniques to do the QA for Machine Learning models.

    Different Machine learning types such as Supervised and Unsupervised Models have different characteristics and are used for different types of problems. Though these solves different complex problems, Machine learning Models also a unit of software code that needs to be verified as a normal software system. When a Machine learning model is seen as a whole system, it may look complex and unsolvable. We can group them into small modules and verify for quality. Black box and White box testing techniques can be applied to verify the functionality. Data, Feature Engineering and Algorithms are the major part of the Machine Learning model. We will see how we applied different techniques to validate these.

    This talk is focused on viewing the Machine Learning software as a whole and performing the Quality Analysis for it. We look at how different is testing a machine learning model from typical software testing. We will discuss the challenges that came across, the Process involved in building an ML model. We take an example of Search Relevance for an explanation. We will dive into the areas where quality is assessed. The significant factors considered here are measuring Accuracy and Efficiency. We will look into the different black box testing techniques for different Algorithms. Let us also see how traditional testing is different from testing machine learning applications. I will go through different black-box testing techniques with examples following a live demo.

  • Liked Argneshu Gupta
    keyboard_arrow_down

    Argneshu Gupta - Get rid off Xpath in iOS Native App Automation

    Argneshu Gupta
    Argneshu Gupta
    QA Lead
    3PillarGlobal
    schedule 1 month ago
    Sold Out!
    45 Mins
    Demonstration
    Beginner

    It is always challenging for us while dealing with Xpath and Css in iOS Mobile Automation.Even we can't think to do iOS native app mobile automation without them .

    So problems we need to face are

    • High Maintenance
    • High Execution Time
    • Complex installation
    • Additional Web server

    Do we have some solutions for this problem - The answer is Yes !!! -> KIF(Keep It Functional)

  • Liked Vishal Srivastava
    keyboard_arrow_down

    Vishal Srivastava / Khyati Sehgal - Setup Grid Infra with AWS Nodes & Autoscaling of AWS Nodes

    45 Mins
    Demonstration
    Intermediate

    When it comes to creating a project we always search for ideas that are open-source, easily scalable, ready to use.

    We as humans always have a tendency to grow and expand and when it comes to customizable infrastructure it's a big Yes.

    In this talk, we will be focussing on how we can save the cost of actual servers with easily scalable and manageable open-source software using an open-source tool - selenium grid. How we set up the nodes and hub altogether to make cross-browser, multi-platform execution takes place.

  • Liked NITESH JAIN
    keyboard_arrow_down

    NITESH JAIN - Automation a driving factor for successful agile model

    20 Mins
    Talk
    Intermediate

    We are living in the era of fast paced software development . Quality was always a concern and will always be . Now as the industry is demanding to shorten the testing time , its getting more hard and challenging to cope with the speed of development in the same agile mode.

    Lets understand what we can contribute and make ourselves future ready on software testing.