In response to the COVID-19 virus, the majority of Syntax Technologies software developers were instructed to work from home starting in March 2020. From April 21 to May 6, 2020, it took place. My boss suggested that another QA member and I attend electronically because flying was no longer necessary (or really even allowed), and we did so.
The conference focused on SDET Online Training and included a wide range of software testing-related subjects, including:
· timing for automating
· Risk, dependability, and reuse
· API Testing advantages
· Role of SDET
· Scrum framework automation
· Mobile testing tools include Appium and Espresso
· Architecture for an automation framework
· Management of test data and artificial data
· Test automation and DevOps
· testing in a controlled setting
· coordinating with testers and devs (soft skills)
· Evaluation of test automation performance
· Scalability
· both machine learning and artificial intelligence
· Creating a culture of excellence
· CI/CD and DevOps quality
· updating your CI/CD process, among other things
It's clear why this conference lasted ten days now.
Test techniques and equipment: What is SDET?
There were several distinct test methodologies and test tools covered. J Meter, Appium, Espresso, Pester, and other specific tools were covered. I had heard of some of them before, but not all of them.
While watching the slides and listening to the talks, it was clear from the start that the speakers were discussing the SDET. I didn't know the phrase, at least not in the way it was being used, I thought. Although I thought I understood what it meant, I was still unsure. I enquired about an SDET from my excellent colleague using WebEx Teams, the preferred instant messaging service at Syntax Technologies. He revealed that the software development engineer was working in testing. Now that I thought about it, it made sense. I knew what that position was and some of the duties, but I had no idea that it was also used as a position unto itself or had its own acronym! The SDET Training Course quickly became a word I was also familiar with as speaker after speaker mentioned it in some form. Then it dawned on me that they are a crucial member of the team.
Why do people use automation tools?
The software team (development and QA) at Syntax Technologies uses automation tools for a variety of projects. I'm using TestComplete right now to create automated tests for a Windows-based legacy product of ours. This device is part of the effort to combat COVID-19, which has forced so many of us to work from home. TestComplete is also used by other Syntax Technologies QA engineers for various products.
Cypress is a modern front end testing tool of the next generation that may be used for unit, integration, and end-to-end tests. Any programme that runs in a browser can be tested by Cypress. At Syntax Technologies, Cypress tests are created for one of our web interfaces for a little, cheap air quality sensor that is simple to set up in or near a troublesome region.
Actually, a separate engineer at Syntax Technologies is utilising two distinct automation technologies for a brand-new product that will be published soon for several platforms. For desktop applications, Spectron automation is utilised, and Appium is used for mobile versions (IOS and Android). These are only a few instances of TSI's work in test automation.
Questions outnumber solutions
I was able to test my application under test using JavaScript automation code written in TestComplete, but I quickly realised how difficult it was to apply the test scripts as efficiently as possible. When, where, and how would they be conducted? What purpose would the outcomes serve? What connection would they have to software development? Continuous Development and Integration What versioning system would be used, and how would the code be maintained? How could the programme itself be developed, released, and tested continuously?
Other queries came up. Am I utilising the proper tool, and what will my next difficulties with new items be? How can the automation team use best practises even though we test various products and utilise various tools? What are some DevOps best practises?
Comments