E2E Web Testing

As discussed in  Choosing a Coding Language  we'll be predominantly be discussing test automation in Java. But just for reference if you're looking for a javascript IDE you're probably looking for  Visual Studio Code . And for Java we're really talking about a choice of two.  Eclipse  and Jetbrains  Intellij IDEA . If you're joining an existing team they probably have one they use and the company will provide you with a licence for a pro edition. If you're starting from scratch at company or you are a beginner well then you have a decision to make. For me and my professional experience IntelliJ has been the go to IDE. So my opinion is probably going to lean towards pushing you in that direction. But in saying that, if you get good with one, well then the other will not be as much of a challenge to pick up. We'll focus on IntelliJ here. Below is a brief run through of installation and some of the features we'll use when developing automated end-to-end tes

So you've to decided to embark on an end-to-end test automation journey for your web based apps. This is your Odyssey. Exciting but where do you start? Choosing a programming language. There are quite a few considerations: what language is native to the application under test? are you focused on one component of a system, like web only, or are you going full stack and writing tests for web ui, mobile apps and backend api's? what language are you comfortable with now or are you starting fresh? what are fellow QA's in my organisation using and are there existing frameworks I can use? what support do I require? There's a good case for choosing the language native to the application under test. This would allow developers to get involved in the writing of end-to-end tests. But there are drawbacks to this. Tests need to be maintained and constantly optimised. Typically a dev will only ever write a tests for newly delivered features. So who is going to maintain the project. Y

  At the time of writing I've a fair few years of working in a SCRUM environment under my belt and have been involved in 2 transitions from traditional approaches to SCRUM. The first I was heavily involved in having completed the PSM1 training and leading a newly formed SCRUM team into the unknown. At this time I was duel rolling as SCRUM master and QA engineer. AS well as setting up the team to follow the SCRUM style SDLC and flows I used my newly found servant leader "power" to bring quality front and centre and build it into the way we as a team delivered software. Additionally we used metrics such as release cycle times and ticket time in status to hone in on where our bottlenecks existed so we could target these areas to deliver software quicker. These will be explored in later posts. You might have looked at the  Scrum Guide  and be thinking, hey, there's no mention of QA. That's because SCRUM is largely agnostic. You'll see the development team mentione