Handling Issue with Login - How it’s Not a Bug But Reported as a Bug (with Customer Example)

Handling Issue with Login - How it’s Not a Bug But Reported as a Bug (with Customer Example)

Video


 

Steps

Step 1- Click on Step 8 to get the new window to put email address

Notion image
 

Step 2 – Click on Step 8 to Change Login Email

Notion image
 

Step 3- Click on Step 1 , Step 4 , and 5 to put Comment and Login Details

Notion image
 

Step 4 – Click on Go to page – Click on Email – Click on Enter Button

Notion image
 

Step 5 – Turn on Screen Settings

Notion image
 

Step 6- Turn on the Play Button from desktop and run it will automatically open the window

Notion image

Demystifying Login Automation: A Deep Dive into Identifying and Fixing Common Issues

Introduction:

In the fast-paced world of software development, automation plays a crucial role in streamlining processes and increasing efficiency. However, even the most well-thought-out automation scripts can encounter issues that need careful attention and troubleshooting. In this blog post, we'll dissect a real-life example of handling an issue with login automation, highlighting the steps taken to identify and rectify the problem.

Reasons for Automation Failure:

The script dives into the intricacies of an automation process that encounters failures during login procedures. It emphasizes the importance of understanding the sequence of actions and the necessity of including all essential steps, such as clicking the sign-in button after entering login credentials.

Analysis and Solution:

By breaking down the failed automation steps and showing the corrected version, the script sheds light on the critical components of a successful login automation. It stresses the significance of meticulous planning and execution to ensure a seamless login experience for users.

Testing and Implementation:

The script demonstrates the testing process involved in validating the corrected automation steps. By utilizing tools like Postman to test webhooks and simulate login scenarios, the importance of thorough testing before implementation is highlighted.

Conclusion:

In conclusion, the blog post encapsulates the journey of troubleshooting and refining a login automation script to achieve optimal functionality. It underscores the iterative nature of software development and the continuous learning process involved in addressing challenges effectively.

Call to Action:

Are you facing similar challenges with automation scripts in your projects? Share your experiences and insights in the comments below. Stay tuned for more in-depth discussions on streamlining processes and optimizing automation workflows.

 

VIDEO TRANSCRIPT

Hey, so, looking at this, there's a couple reasons that this automation might fail, um, or will fail, and then I'll show you what I did to fix this. So, first thing, going to this URL, that's totally fine. Um, when we are filling out these input fields right here, we don't need to record a clickstep. You can if you want to, but you don't need to.

So you'll see that I have these disabled in the version that I made. The type step, typing your email here. I don't want to play it just so that we are skipping over, I guess, showing your email to everybody on YouTube. Um, but this play step is just going to type here again, this click step, I'm going to disable, and then we're going to type your password here and then we can go to that page.

The problem is, is after you typed your password, we didn't record a click step of clicking sign in, so it's never going to sign in before getting to this page. So that's probably why you saw, um, a bunch of errors with the, uh, with the page, not loading, or you not being an admin, things like that. So if I go to the automation that I made in here, this is doing something, I mean, almost, this is doing the identical things, but with all of the steps now.

So once this takes us here, um, I'm going to go ahead and pause this really quick just because this is going on YouTube so that it doesn't show your email. Um, it shouldn't show your password too, but we're just going to play these steps right here. Step three to fill out the email, skipping this cause we don't need to step five to type in the password.

And then step six is clicking sign in. So just a second. Okay. So now that we clicked sign in, we are Um, and again, I'm not sure how you were able to, like, not see admin beforehand. But I think that it was just because we weren't clicking sign in. Um, and then you had this go to page step, which was taking you here, which I assume if we went to this go to page step itself, you probably could see something like this.

And that's why you just basically saw the logged out user view. So if we run this step, which is next after clicking sign in, it'll take us here. And then I can go ahead and type my email. And then I can click, I don't know what this does for you, so I won't actually play this, but this is going to go ahead and click the send button that invites the learner.

So to trigger this, the only other changes you need to make is this should be coming from your webhook, which I think that you said you're setting this up already, or you already set this up. Um, but anyways, if we send the data here, we can select a record that'll give me my webhook trigger variables, whatever we want to go for.

And then I can enter that here. And now with this automation will do is every time this webhook is hit, it'll go to this page. We can delete these steps. It'll go to these page, type in your email, type in your password, click the sign up button, uh, or sign in button, and then go to your page. type in the email and click submit.

So I'm going to go ahead and disable this because again, I don't know if this actually changes anything for you. And I don't want to invite myself a bunch of times to your platform. Um, and then what I'll do is I'm going to go ahead and turn the screen settings off. to always show the browser. That way I can test this quickly.

We can turn this on from desktop, and then I'll open up Postman to test my webhooks. You can use something much less technical. Um, and what this will do is this is going to send it to that webhook with the email I want, and it will start this automation.

And I will pause this at some point so that it can type in the login details. Okay. Now that we logged in, we saw admin for a split second there. If I unpause fast enough, and then we'll see the webhook data that I sent get entered here and click the, it didn't click submit because I have it disabled, but it would have, um, again, using this data.

So let me know if you have any questions. Um, again, this is in your account under the, uh, I tagged it, something test magic support.

Did this answer your question?
😞
😐
🤩