A Day In The Life of a QA Tester at a Software Development Company 

What do u mean with lead to bugs? How can u not find bugs urself? Genuinely asking ❤

This is a should be case, a tonne of companies still don't have mature testing practices like this and are often dumped in well after a build is out

@simondean9127 You are totally right, but as @licriss already mentioned, many companies, especially start ups and small businesses, don't have the resources to the all the static testing and are always pushing the development without properly testing it and evaluating all the possible issues beforehand. That's just the sad reality for us QA people. After that you are stuck with more regression testing, reproducing and reporting bugs and working with the developers in general than working on the quality of the product with Product and Business team. The only way out is raising these issues with the company management, getting more testers involved or changing the project/job for a more "mature SDLC/TDLC" one :)

Depends on the company, usually you start with a daily standup meeting where someone asks you what did yesterday, what you’re doing today and if you’re going to have any blockers(problems). Then you can look at your ticket tracking software(most popular is jira) and then start writing your automation tests based on that. You could be doing some manual testing too. And that’s pretty much iy

@@ninjaxmen Thank You! Took me like 40 seconds to read this yet the video is minutes long lol

One of the biggest complaints I see from people getting from other IT fields into testing is either constant context switching or boring repetitive tasks depending on the workplace and the fact that suddenly noone understands what they do and doesn't believe that they can't work faster, unless you get more into automation then its just context switching and the ability to stop things before theyre done because most places cut the time for QA much more than the dev time. For manual testng basically at the lowest level you're trying to determine how to do certain actions in an app based on what someone (BA, PO or user) thinks they want to do with an app, and taking all possible interpretations of someones desired behaviour as well as finding different ways to do it, a good manual tester can figure out what the least clever, most clever and average users are likely to do to get to an end goal and script those sequences out and do those, essentially the goals of the most effective manual testers are once they've done the workflow normally they do it in a way that gets the devs to say "thats not how you're supposed to use it" or "no real user would do that" because those are the points that usually break in production and you'll pick up the other small or obvious bugs along the way. The hardest part for most at first is often trying to describe what you did or will do in a clear repeatable way or what you did yesterday because usually you have to take a risk based approach and as soon as you've worked through the key areas of one system workflow you should be switching to the next highest priority and you'll be often dealing with systems that are too broken to do some actions within good tims which then gets political because people never believe a slow process is actually slow until they try it themselves, also explaining convoluted processes to pissed of devs is a big part of the job, some devs get really aggressive with testers who are able to figure out the more irrational workflows especially ones that have worked at places that make high bug count a negative KPI Some places are more mature and give proper time to testing as well as time spent automating the most boring or tedious tests, in those places typically manual testing will just be about taking a user journey and doing it in both the most basic and most unusual ways to try and find bugs in a given area for an app, these places are somewhat rare though

I’m a junior QA tester. Obvs it depends what stage of testing, normally a typical day is writing test scripts, prepping data, and arranging for key users to come in and perform tests then guiding and assisting them through the tests (for user acceptance testing). You also submit defect reports, progress reports, help with aspects of the test plan etc. If you look at the ISTQB CTFL syllabus you may get a rough idea. Hope this helps :)

😂😂omg 😂

There is a misconception of total isolation in IT but it is exceptionally collaborative BDD

​@@caekeherderofrabbits940tjhis got nothing to do with misconception, it got the do that as a IT engineer you have to possibillity to work from home and can have a better connecties with home front! Because we can work digital!! But a lot of suckers still wanted to work 5 days on the office despite you can change your life ans work from home and discover more than only live in the 4 square box in the office

Your exspectations are true! You have the freedom to work from home! And to be in the box office whole day long like a slave

@@AnubisGeb I left IT so I don't care anymore

Is it possible to find a job as a manual QA?

@@PerformanceY yes you do.

hello storyahe, which tool do you use in work? I mean, as a QA automation do you use selenium or cypress?

I think you should find a offline course in your location first. Then, you can learn by your own

To become a good software tester, you really do not need much. 90% of my success was spending my childhood and teenage years with technologies including Windows PC, laptop, dumb phones, smartphones, Android, iOS as a user, being curious, fiddling with the device / OS settings and not just what you see at first glance when using it. Being detail-oriented and a perfectionist, curious and organized helps a lot. You will learn mostly everything else within your first two months on a junior testing job position. My current position is a senior software tester and I've been doing it for less than 2 years and I'm good at it (according to my results on various projects), feel free to ask :) I've had many colleagues who just started in IT software testing while previously having no IT experience and they became valuable pretty quickly.

@@JackD0ff how much coding do you need?

@@GooseMan-64 depends on whether you want to do manual or automation testing. In manual testing, you don't need any. Having some knowledge about basic programming principles is an advantage, but you won't be coding at all as a manual tester

@@JackD0ff do you have a discord, can you be my mentor I’m starting a QA job soon

Yeah that's my bad 😅 only reason I said Monday as that's the main day everyone is working in the office haha!

🤣

@@michaelclark09 thanks for the video, I am a new manual QA and wondering if any ISTQB qualifications/ any coding languages would be useful?

@@kkkchel helpful but not required

there are manual tester which dont need coding but u should know basic, and there is automation coding which involve a lot of coding but got higher paid tho

As a software tester I mainly use Jira, Appcheck and TestProject :)

@@michaelclark09 is it worth to get ISTQB certification?

As a QA Engineer I mainly use Swagger, Postman, SQL, and C# for Automation. We also use Azure DevOps for our Scrum Boards in my company

qa junior testor is the best start compared to the ease of coding. I went for front end web development course to find out i would not be best starting off. QA testing is easy compared to everything else whitebox testing involves knowledge in coding you can do automated or blackbox functional and non functional testing. white box is a little more on the advanced side but you could pull it off starting off as junior but ill leave it up to silverchip to answer this question better.

@@proatbilliards white box is only hard for people that have no idea what the code is doing. So yes most testers would find white box difficult, but for most developers white box is easy

I can help you

@@musawerpopal2279 what's your experience?

Also in the same boat here, applying for jobs endlessly but not getting interviews or next steps at entry level roles. I have completed a manual testing course and I am also ISTQB certified at foundation level. Just want to get my foot in the door and learn on the job but I just can't seem to get past the application stage.

any laptop with at least 8 GB ram and 256 GB SSD.... recommend 16 GB ram if you can

As Vijay said, a laptop with 16GB ram and at least a 10th gen i5 (11th or 12th gen i5 would be better) and a decent sized SSD would do you good :) personally for testing I use a Macbook Pro though

she is dired

Why you want to switch can you elaborate

Me too bro I've been studying this skill for about three months

Is there a jobs in this field?

@@ghettoghost2657 where u studying from and how u plan to get ur foot in door with no prior experience?

did you do it?

im not a expert but i figure someone has to be the one asking the ai to run the tests, so probably no, the tasks will maybe differ in the future though

@@august5135 look like will be less jobs for sure

Better get into UX then :)

I don't think so. I mean it can help you write some simple test cases, but something more advanced and you need to write it yourself. With automation I think it's the same thing. For desktop application testing, the AI don't see the elements, so it won't write it for you (same with website testing). But what I like to do is take my automation scripts and give to AI and ask for improvements (refactoring) and if I see anything good, chances are I will implement them.

AI will be able to automate tests. However, many companies are bound by regulators who impose specific rules. We are the watch keepers for AI. The best way to future proof your role will be to learn as much as you can about AI so you can test around known weaknesses. Our world will change, if you do a qa job which can be automated you are already placed in the race of extinction. Skill up now! You will also find that qa devs certainly BAs will be at risk in the future.

Yes

It requires coding or not ?

@@angelmary1 Nope!

100% yes.

​@angelmary1 manual doesn't require coding, but automation requires coding. But Bro trust me it's not hard, just requires you getting used to it. don't feel discouraged.

No

Anyone can learn QA definitely go to a nice bootcamp or a program to learn more but a bootcamp they expect you to finish in 3 months or less depends on the bootcamp which a program you can take your time learning the skills that you need

google for jobs and then apply

@@ZDProds-c8p says you gotta have 4 year degree in it. I already have a degree in something else.

@@Paragon_Reason If you know how to do a certain job properly, you are not required to have a degree in it. Especially in IT.

this guy seems he is native english speaker, what's the problem with his english?

he speaks english not because its his only language but because its the only language you speak

@@rodrigocruz8548 he speaks english because hes english, just like anyone else. It's the accent people struggle with