All right now let's get some more technical parts in the course of this stuff about testing times.
I this is the most common and most used thing here.
So let's stop and start from the facts on this thing.
So essentially post is testing you always must be a happy kid.
That's the danger.
But the testing is he's doing something in the way you expect it to be high.
So for example let's say that you have some on field to check the year of birth.
And so for example what the developer is offering up or expects the user to believe in there is 4 digits
number.
Why should we say 1997 or something like that.
And the point is that this can be just as good.
1 9 8 7 click some Boston TV somebody and to see that the result is good.
What do you get.
And this one.
This is the easiest of testing time.
And the previous one that is one of the most of the developed this year and this one.
So it something that has finished the code the one to make sure that it works somehow.
So they go in.
They put some data in there.
Collect some things and see if that works.
So if a person is afraid Hastur it might help you to find somebody that I really like in the surveys.
But you know it's not that long ago and you would you'd find much more about using the second type which
is negative.
Testing testing is looking at the problem from many many many different angles.
Say OK so you have a box they put you birth birth here.
So what if somebody decides to do it.
Yes that is a sentence in there instead of a number.
Maybe some people say no I'm Gene Agee's literally right as I said.
Or perhaps some person or not.
I've got a copy of my car just driving drunk and then the feel is no to soften it up or the company
expects them to do.
And sometimes you know by these actions that we're not seeing the fall and the using the brakes the
actual program which is nice which we don't want to do.
And this is the time to find the house on the box.
So it will take a lot of time and energy at the end of the day using negative testing and really trying
to figure out anything anything any possible situation with a certain part of the program you'll find
a lot of boxes in
let's take a look at the next one which is why I thought why this thing is is that you actually understand
some code I understand software languages languages for Groundlings.
So for example you need to test some placeholder some like some fields for for like a day of birth other
things.
Right.
And you know the front end part is that we can yes which is the framework for I was free and said OK
so I don't know how it works.
I understand it and I say there is some error and just just reporting the error you are looking to the
code of the actual fields and you will find the exact place you don't want to face because you're not
a software developer but just an opportunity and make it possible that if you find it it is highly appreciated
and really in your mind.
So you know the names that are used by the company your locks say oh I have stated that they didn't
know what I was testing these.
I said you don't need to look like or maybe you know how to program but you know you're just looking
in your own purely how you watched and come from this position you place for a lot and you can find
some bucks unicast thing testing is usually done just because it is purely pragmatical and be the smallest
possible part of the call.
This is something that was developer down developing some software for the client in the same programming
language usually to write a code test.
So there are very few testers for them specifically like software testers look you able because usually
if you can do the test you can program.
Usually people tend to do something about it but there are some and they're very much into it.
And so you know a little bit of that around which you can do testing done and what to do.
So I think then good luck.
It's a good place to be.
Yes functional testing functional testing as you see some documentation.
And for every part that part of the documentation for every input you provide you get to set up the
inputs provides the different output that is specified in the documentation.
The program doesn't work and is something just like you have to update the documentation you have extended
write the same sort of set of priorities which parts of the system are more important separate such
an essential function and is like Hey you tested the system functions as indices on two regression testing.
This is a very good one because the regression testing is looking at if what like yesterday doesn't
work today.
So essentially is this question.
Sometimes one is fixing something doing something else and this is very very common.
Probably more common than a lot of people would imagine.
And very often you recommend you when you're testing something shocking thing or actually bugs fixed
so you can get the production as hey you fix this bar couldn't possibly be so that you work something
out of the season.
And sometimes it they are coming I would can you use the case and then do my thing with it.
Well I mentioned this in the night and night.
And then knowing that you can go past those things around it and possibly something stop worthy.
And again a diversion can be really related to functional testing where you follow the documentation
and try to test everything that works together.
Acceptance acceptance or ossicles casting is when when you're trying to release a new version of the
application before it can go to the clients you might say hey this product is good enough to be sure
to come.
So generally again back going back today a lot of them work together.
Right so many were functionless.
So I second guessing is for example are like day to day before they release you looking they change
the way down but not only to change the way everything else would go through the list of higher functioning.
So for example if there is a button and by the way it doesn't look nice you know like somebody has mistakenly
called something that is not really important if you're doing that e-commerce website and their bottom
looks fine and good.
It's a pain but it doesn't work and they can actually kind of pay.
This is a problem we usually find is a blocker problem that prevents the functionality of the whole
system.
Pre-retirees those issues so you need to say which functionality is very important which are less important
and which ones are almost not important.
And interestingly you will start with the high level functionality is done and then can decide in that
way I think is funny this is also called multitasking and sometimes it seems that you know for follow
any guidelines that any that can be and you just micro-housing along essentially when your mouse clicks
and is called multitasking you can be really useful because I say this scope of your documentation is
easily needed.
And sometimes it's possible and very possible that something happens outside of the scope of everything
that can be taken.
So sometimes I just click the wrong thing and find somebody that's been there for like yes nobody's
seen it because nobody wanted to stop and go for it.
So don't miss out on this one as well.
And then these start very taskings 30000 is a bit Simonton after testing.
Well you're not fully in your contention how it's more of a thinking process.
And again as I say things like regression testing when you say some developer has changed something
and then you do things like ok tell him I have changed something.
Could this possibly affect anything in the system and say and then you find someone Chanology that work
in use like obviously the reporting part but then you say oh wait.
Possibly.
I know that say the infrastructure the already say that they use the same function to say like function
call very we like to other parts of the system so why not take the square and figure out that the problem
is not elsewhere.
Hi Bob.
And then figure out what is or and you can actually point out particularly when it happens and if you
don't do that it's fine.
But then developers spend their time trying to figure out what happened.
If you can particularly like say than 30 minutes one hour this Congress would be very happy to show
that you could professionalisation.
So these types of the necessary ones.
I hope you enjoyed it and knowing them is very important for you in two years or so once you come in
and just understand that you can really get the description that I'm attached to this course.
And you know come into the interview knowing these things are really out.
Let's go to the next section.