:- Key points to be begin with if you want to be a good web tester.
1. You must be able to understand the project you want to test as if you own it. Trust me if you are missing this key point, you will never be able to test your website.
2. Inspect Element :
Above is what is called the best part of web testing, the only thing that's best is you can observe everything about a website by just looking at the above console. Namely they serve below purpose.
a) Network: It shows us what kind of calls are getting sent to the servers and by what path. By path my meaning is to tell that URL. This also tells that what kind of Server status this particular call has and whether the call is complete or not.
To Know more about these server response codes. i am providing a easy Link. (Click on the link)
This Network call if you will understand, you will excel in testing and will find many more bugs. Plus this helps you understand different types of request Methods, such as GET,POST,OPTIONS etc etc.
a.1) GET : This is also a very important types of request method, To better understand say you want to send query strings, say some id with a particular value. You will use this method.
eg: www.shreenivash.com/name=shreenivash
As a tester its very important to understand these request methods because if you will understand these, you can use them to test SQL injection and explore many more options.
To know more about these request methods look on www.w3schools.com/tags/ref_httpmethods.asp
This will help you understand these methods in better way.
I will guide you about SQL injection in a separate blog.
Similarly Network calls will explain all about how a website communicates with servers. These hold very key information about the servers these requests are hitting and many more. So if you have any questions why a exposed Server address is getting used in these Network request you can raise these to your technology managers and tell them about, How severe these information is.
There are many more tools which are preferred in market, famous is Firebug. Because it is often said that if you can understand what firebug does you know how server , web communication goes on.
b) CONSOLE: Console is the place where you can access all the amazing data a website keeps under its cookies and JAVASCRIPT cache. like user data, email's etc etc.
Just check this image out.
to use any console command, Just navigate to console menu and type in alphabets from A to Z and if the programmer/ Developer has left any Javascript command in his/her code you can invoke and use it smartly.
You can set many things from this console like you can set a new cookie or modify any JS variable. Use it smartly and you can make your team proud.
c) COOKIES: This is too a very important part of websites. Mostly all the session or you can say data related to user's identity are kept here in a very secure manner. You can alter these cookies as per the requirement or your understanding in teams you work for.
There are many other benifits of Inspect element options like memory profiling of how much your website taking RAM of the system its running on. etc etc. i will cover there in more details in later sections.
3. PAGE SOURCE : Page source is the key place a tester need to know. All and every thing about your website you are testing is present in the page source. Default command to check the page source is
windows: ctrl +U
MAC: command + U
Most important thing about testing is to understand that there is no magic happening when a website loads in your system , by system i mean your laptop or desktop or even your mobile where you are loading a website.
Browsers are told what to do by the page source, which code to read, How to read CSS, HTML, JAVASCRIPT etc etc. so as a tester you must make sure that your page source is not exposing any important data that is not meant for end user perspective.
Because even developers are Humans and Humans tend to make mistake.
4. KILL SESSION: Before understanding how to kill a session? You need to understand what session means. I know experts will have better answer but for testers in Laymen language: Take example of cricket. if you are going to bat in match and you get out, doesn't matter you got LBW, got bowled or got catch out. You are out. You cannot bat again and add runs to your currently batting runs in current match. This is called one session so if you will kill session. you will have to start all over again.
To do this in browsers we clear cache/cookies of a website. This can be done easily by these shortcuts
windows: ctrl +shift + delete/Backspace button
MAC: command +shift + delete
These commands will open a short window where you will select cookies and cache and will delete it
This will kill the current session and you can start all over again to test same scenario's
What kind of scenario's are affected when we kill a session ?
- Logged in user
- Inconsistency in data if any location based cookie is present.
1. You must be able to understand the project you want to test as if you own it. Trust me if you are missing this key point, you will never be able to test your website.
2. Inspect Element :
Above is what is called the best part of web testing, the only thing that's best is you can observe everything about a website by just looking at the above console. Namely they serve below purpose.
a) Network: It shows us what kind of calls are getting sent to the servers and by what path. By path my meaning is to tell that URL. This also tells that what kind of Server status this particular call has and whether the call is complete or not.
To Know more about these server response codes. i am providing a easy Link. (Click on the link)
This Network call if you will understand, you will excel in testing and will find many more bugs. Plus this helps you understand different types of request Methods, such as GET,POST,OPTIONS etc etc.
a.1) GET : This is also a very important types of request method, To better understand say you want to send query strings, say some id with a particular value. You will use this method.
eg: www.shreenivash.com/name=shreenivash
As a tester its very important to understand these request methods because if you will understand these, you can use them to test SQL injection and explore many more options.
To know more about these request methods look on www.w3schools.com/tags/ref_httpmethods.asp
This will help you understand these methods in better way.
I will guide you about SQL injection in a separate blog.
Similarly Network calls will explain all about how a website communicates with servers. These hold very key information about the servers these requests are hitting and many more. So if you have any questions why a exposed Server address is getting used in these Network request you can raise these to your technology managers and tell them about, How severe these information is.
There are many more tools which are preferred in market, famous is Firebug. Because it is often said that if you can understand what firebug does you know how server , web communication goes on.
b) CONSOLE: Console is the place where you can access all the amazing data a website keeps under its cookies and JAVASCRIPT cache. like user data, email's etc etc.
Just check this image out.
You can set many things from this console like you can set a new cookie or modify any JS variable. Use it smartly and you can make your team proud.
c) COOKIES: This is too a very important part of websites. Mostly all the session or you can say data related to user's identity are kept here in a very secure manner. You can alter these cookies as per the requirement or your understanding in teams you work for.
There are many other benifits of Inspect element options like memory profiling of how much your website taking RAM of the system its running on. etc etc. i will cover there in more details in later sections.
3. PAGE SOURCE : Page source is the key place a tester need to know. All and every thing about your website you are testing is present in the page source. Default command to check the page source is
windows: ctrl +U
MAC: command + U
Most important thing about testing is to understand that there is no magic happening when a website loads in your system , by system i mean your laptop or desktop or even your mobile where you are loading a website.
Browsers are told what to do by the page source, which code to read, How to read CSS, HTML, JAVASCRIPT etc etc. so as a tester you must make sure that your page source is not exposing any important data that is not meant for end user perspective.
Because even developers are Humans and Humans tend to make mistake.
4. KILL SESSION: Before understanding how to kill a session? You need to understand what session means. I know experts will have better answer but for testers in Laymen language: Take example of cricket. if you are going to bat in match and you get out, doesn't matter you got LBW, got bowled or got catch out. You are out. You cannot bat again and add runs to your currently batting runs in current match. This is called one session so if you will kill session. you will have to start all over again.
To do this in browsers we clear cache/cookies of a website. This can be done easily by these shortcuts
windows: ctrl +shift + delete/Backspace button
MAC: command +shift + delete
These commands will open a short window where you will select cookies and cache and will delete it
This will kill the current session and you can start all over again to test same scenario's
What kind of scenario's are affected when we kill a session ?
- Logged in user
- Inconsistency in data if any location based cookie is present.
Comments
Post a Comment