Home Blog


Q:- Can we check the server side validations are implemented or not on website from QA screen without backend?

A:- Yes, there is a way to know server side validations are implemented or not on the developed site from QA system. This really should be known server side validations are implemented or not to halt unexpected request from users side with invalid information.

If Server side validations are not implemented in developed program then site owner may get unexpected data with invalid values and that situation will make a disturbed behavior to site administrator, so due to this a QA/Team should use techniques to be aware about implementation status.

Sharing an reference technique to know about server side validations are implemented or not, suppose a contact form is developed and sent it to testing team then tester or team should use a simple technique for stopping java script then further need to fill invalid data so now if proper server side validations are implemented then request will not submitted means it is cleared now server side validations are implemented or not.

Q: What to say exactly about QA & QC in interview?

A: Answer should make a reply with some proper words in interview and I can say there should be “proper analysis then create the test cases for executing after getting developed site, application & build” related to “QA” for providing the assurance and for “QC” we can reply “review the site, application & build then give the standard & more friendly suggestions to improve quality & for giving the proper control to flow

Quality assurance process comes during development environment then developed environment to find out wrong implementation and not expected behavior according to requirement further quality control process review to control the quality of developed program for better improvement for further implementation to manage quality.

With a simple example like a request for info form is implemented for registered users or guest user and after testing a tester got it is working fine but all user’s info is also need to fill manually for registered users also now a new suggestion got to auto fetch registered user info during request form filling without any problem so it will manage the quality even with improvement.

Q:- How to get proper implemented functionality in very complicated feature?

A:- Sometimes we get a complex program to implement and there may be a chance to get wrong implementation in feature so there is a very responsible job to a “testing engineer”.

Means, Quality Engineer should start analysis before getting the developed feature then create the cases and then execute the case after getting the developed feature and provide your status after executing your case.

An analyst must be a good thinker according to positive way and negative test conditions also. See an example with proper analysis related to just a simple requirement implementation, like a registration form is implemented on website and according to requirement there was need to set “date of birth” field which was also implemented but during testing process got picker is providing future years right now so it means no proper implementation is there.

Q: What is reliability testing in software and sites?

A: It is about reliability that is most needed in software systems, sites and services. This type of testing is performed by QA Member/QA Team to get reliability about expected result without any negative behavior of program. Due to this verification process complete team can be sure about reliability of developed software which will be very needed before launching in market.

Reliability testing should be done according to service of program which means user must be very comfortable with software about reliability of existing values whatever is being passed by user and process should be done carefully to get reliability before releasing software to market. Sometimes a single mistake can break the reliability of program and definitely that will be very bad impact of team.

With some other meaning it can be defined like expected result must be there after executing the condition with reliability no any negative behavior of executed condition should be there. Proper executing values related result must be out with expected result no different out with expected condition.

Q: What is usability testing process?

A: It is like end user process. In this process there is need to be sure about user point of view meets there before releasing the implemented program.

Under test strategy cycle this process is also one of main to be execute with some test cases about user point of views. Such as user point of view is easy to get flow and use of site/service and application.

For getting more about usability testing taking a simple real time example such as a service is running with consultancy to get meeting appointment and everything is easy to read schedule and required fields to fulfill user related values in “appointment related form” on service portal means everything is very user friendly to read and request from users views.

Q: What is severity?

A: Severity will be a status about a written program, can be like it is technical disturbance review process. How much issue make technical behavior disturbance then will be defined by one of status low, medium and high.

In a written program there may be any type of problem and due to that program won’t work according to requirement and on that condition QA team will define the status of issue, means what type of mistake is there as per technical view.

For instance taking a simple module to be cleared more, like a “sign up” module is developed by development team and shared to QA team for verification now during verification process QA team found “sign up” feature is working but an invalid value is being passed for “email id” like “example@examplecom” ( without dot ), it means  when further user will try to login then probably user won’t be able to login may be user will try correct email id and due to proper restriction to “login form” user won’t get access then further will try to “forget password” then it will also not work. So means “severity status will high”.

Q: What is priority?

A: Reply can be like it is requirement implementation review process according to need of client means very needed, needed or just needed. How much task make needed requirements related program’s scope then will be defined by one of status low, medium and high.

Priority is about mainly need of feature in program which means without that implementation client will not be ready to accept program so this is priority of a source.

With an example of program about priority such as a requirement to write a program about sign up module to access in site and some other features like create a content section where further content can be passed from backed but it is about a further process so priority first will come to sign up program.

Priority tasks can be in many examples just need to think according to client requirement and scope of project means thinking must be very smart about hierarchy of programming structure.

Q: What is bug tracking system?

A: It is about track an issue in system. In other words, suppose there is a bug which is found during verification process and then it is reported by testing team/tester to developer by using any bug tracking tool or there may be a documentation process.

Process can be followed with one of bug tracking system. In market many bug tracking management services are available. Some system provide complete management flow from test cases creation to bug tracking management.

Taking an example to know about track an issue, like a module is developed and tester get an issue  during verification then tester report issue on bug tracking system now senior will be able to track issue status means when issue did report by tester and when fixed by developer if not fixed by developer or not verified by tester whereas fixed by developer senior can track the status.

Q: What is bug life cycle?

A: It is a process from where an issue is reported to closed status. Means, suppose an issue is reported from QA side to developer then developer make their status like resolved, not a bug (due to technical reason), referred to further process (low priority) then QA team review the resolved status issue & if get it is resolved then have the closed status.

For bug life cycle get an example: Like there is “contact form” and “QA/QA Team” reported bug to “developer” like “value of name field” is not passed with “email notification to admin/site owner” then “developer” reviewed the code again and after fixing this issue reported back to “QA or Team” then further “QA” will verify and get now “value of name field” is being passed with “email notification to admin” then “bug life cycle” is followed.

But still get some other related issue due to wrong implementation then bug life cycle will be processing for further and completed until problem is solved and “QA/QA Team” make status “fixed” on “defect report”

Q: When to write automated test scripts?

A: This is one of the main module of test strategy process that depends on the condition of written test case according to requirement of real use of programs.

Software/Service is there to be used by many users at same time and getting many repetition for verification process & there may be some complex features so due to this automated process should be use there. By automated process repetition can be done easily and parallel service request complexity will not so hard to verify.

Automated scripts can also be used for further verification techniques such as retesting and regression testing or scripts can also be there for performance & security.

Taking a simple example to know more clarity, such as a “contact us form” on website and there are some fields like “name, email, phone and address” and now script can be recorded on any “recording supported tool or created by QA after creating script tester will run the test script and suppose get an issue like “value of name field” is not being stored in “database” then further developer will fix issue and QA get revert back with updated status from developer and now QA won’t need to write any new script just or spend extra time just need to run created script and result will be generated in few minutes.

Q: What is cross browsing technique?

A: As name of query it is asking for cross browsers compatibility. This is mainly related to verification process with different-different browsers over compatibility execution according to test scripts.

Mostly issues comes related to compatibility and there is need to execute the conditions over almost most running browsers.

Sometimes a function works over a browser but not working with other browsers such as a “drop-down” is select-able means it is compatible with a browser and not working with other browsers means not select-able so this is a issue of browser compatibility so there is need to execute a condition which should be related to “cross browsing testing”.

Process can be executed by manually or with automated scripts.

Q: What is the process about End-to-End testing strategy?

A: This is a process mainly related to execute the flow of module. With some other words to verify a cycle of  functionality.

A process where it comes with expected result from initial to final phase. Like there is a module in site/app to recharge mobile service balance there process starts with service detail, amount and location then goes to expected service according to need as 2G, 3G, 4G and may other services then it goes to service charge amount after it payment process comes then confirmation receipt/message deliver to user.

Simply to know process end to end verification get this instance:- There is a registration form and user is registering with valid values now process is done and user get message like registration is successful now further owner of site will get a email notification about new registration and record is saved in database and lead management then can be a simple way to get more about end to end process.

So this is a process with some examples. There may be two or more than two modules connected in a site/app to be executed by QA Team.

Q: How to find out not secure connected page when security connection is already implemented on site?

A: Page security is a needed verification step by QA/QA Team after implementation on site but sometimes one or more of those pages may not be connected and there security can be break. So a QA/QA Team should not forget to work on that.

Many automation techniques are available to find out not secure connected page. Process can be done by manually also but this will take enough time and one or more pages may be there those are not found by tester/team.

There is one simple technique also available to get insecure page by module to module. Just need to open the module of site what needed to be verified then run the command “Ctrl+U” now code will be visible there and now need to run “Ctrl+F” then find insecure page if page is there then will be highlighted there.

Command can be changed according to “OS” but process will be same for finding not secure connected page if getting any reason about commands not working then in simply way use the “right click then select source code of page and further find unsecured page which is not connected with HTTPS”

Finding not secure connected page related case can also be used by using any link related testing tool  so first thing will be needed to run tool then all pages link will be fetched there after completing of executing then use find command and use keyword like “http” then pages will be highlighted and find site’s pages if any page is there then definitely it will be a simple trick to this case about not secure connected page.

Example with founded links:- Suppose previously pages was called from “http://……com” then after implemented “SSL” pages must be called from “https://test.com”. There should not be called any page, image or any source from “http”.