Beacon - End to End Automation with selenium
When we talk about enterprise level automation where in there are multiple technology stack involved it becomes exceedingly difficult to automate every application using the same tool. Selenium web driver has become a defacto standard when it comes to web application automation and no body would prefer any other tool over it when it comes to web. But what about the other applications, We may have some SAP/ some .NET applications that are linked to the web application and needs to be automated as well. Lets go for some other tool here, but oops this tool does not talk java (which is what the automation team uses here). Basically we need to maintain two different automation teams with two different automation framework which is defenitely and overhead.
The talk is about
1. How to over come this scenario
2. Rabbit MQ
3. Integrating the MQ server with Grid
4. Other tool (other language binding) integrated to selenium
5. Building java COM bridge
6. Developing custom bindings to your tools which by default does not have them
Outline/Structure of the Talk
Beacon is an innovation in action, which will serve as an inter-disciplinary communication channel between tools and technologies, enabling its customers with the capability to use the tools of their choice with their favourite programming language, thereby unlocking a totally different level in the space of test automation.
High Reusability is ensured due to object oriented design patterns
High Flexibility as it provides a means to utilize existing frameworks in tools otherwise not supported
Extensibility is enhanced as there is a provision to enhance the scope to include more coverage in testing
Integration with CI and SCM tools are relatively easy due to the usage of generic languages like java, c# or ruby compared to tool specific
languages and formats
Uniformity and Ease of Maintenance is established irrespective of the tool selection
Resourcing is no longer a burden as the existing resources can easily switch roles
Bridging the gap between unit testers and functional testers by allowing the unit testers to use advanced automation interfaces.
Any one who have faced the problem statement mentioned above.
schedule Submitted 5 years ago
People who liked this proposal, also liked:
Bhumika S / Anand Bagmar - Say ‘No’ to (more) Selenium TestsBhumika SSr. Quality AnalystMYOBAnand BagmarSoftware Quality EvangelistEssence of Testing
schedule 5 years agoSold Out!
How many times do we test the same things at multiple layers, multiple levels, adding time to the build process and testing cycle, delaying the feedback?
We know what to test and how to test, but what is the right place to test it?
In this workshop, we will demonstrate how as QA’s we can identify what tests can be classified as unit tests, integration test and functional test. Using a case study, we will see how each component can be tested as part of unit testing; the integration of different parts and the functioning of a software system as a whole and how functional tests fit into this big picture. We will then bring all these tests together to understand and build the testing pyramid and how it enables us to build the right testing framework with fewer selenium i.e functional tests.
Justin Ison - Android Mobile Device Grid & CI - Getting StartedJustin IsonSr. Software EngineerApplitools
schedule 5 years agoSold Out!
In the modern era, we have many different cloud testing services to choose from. These cloud services are useful and help reduce the burden of building and maintaining your own Selenium Grid environment. However, there are many scenarios in which you need your tests running locally and quickly, such as you work for the government (or agency), you have sensitive software/data you cannot expose to the cloud, or service costs are too expensive for your organization.
This presentation will feature getting started with setting up your own mobile device grid, running your tests in parallel, running in CI (Jenkins), and the lessons I have learned along the way.