QA training Brampton and placement assistance, QA training Brampton and placement Mississauga, QA training Brampton and placement Mississauga, QA Training Canada, QTP jobs Toronto.,

19. Which test cases are written first: white boxes or black boxes?

Normally black box test cases are written first and white box test cases later. In order to write black box test cases we need the requirement document and, design or project plan. All these documents are easily available at the initial start of the project. White box test cases cannot be started in the initial phase of the project because they need more architecture clarity which is not available at the start of the project. So normally white box test cases are written after black box test cases are written.

Black box test cases do not require system understanding but white box testing needs more structural understanding. And structural understanding is clearer i00n the later part of project, i.e., while executing or designing. For black box testing you need to only analyze from the functional perspective which is easily available from a simple requirement document.

20. Explain Unit Testing, Integration Tests, System Testing and Acceptance Testing?

Unit testing - Testing performed on a single, stand-alone module or unit of code.

Integration Tests - Testing performed on groups of modules to ensure that data and control are passed properly between modules.

System testing - Testing a predetermined combination of tests that, when executed successfully meets requirements.

Acceptance testing - Testing to ensure that the system meets the needs of the organization and the end user or customer (i.e., validates that the right system was built).

21. What is a test log?

The IEEE Std. 829-1998 defines a test log as a chronological record of relevant details about the execution of test cases. It's a detailed view of activity and events given in chronological manner.

The following figure shows a test log and is followed by a sample test log.

22. Can you explain requirement traceability and its importance?

In most organizations testing only starts after the execution/coding phase of the project. But if the organization wants to really benefit from testing, then testers should get involved right from the requirement phase.

If the tester gets involved right from the requirement phase then requirement traceability is one of the important reports that can detail what kind of test coverage the test cases have.

23. What does entry and exit criteria mean in a project?

Entry and exit criteria are a must for the success of any project. If you do not know where to start and where to finish then your goals are not clear. By defining exit and entry criteria you define your boundaries.

For instance, you can define entry criteria that the customer should provide the requirement document or acceptance plan. If this entry criteria is not met then you will not start the project. On the other end, you can also define exit criteria for your project. For instance, one of the common exit criteria in projects is that the customer has successfully executed the acceptance test plan.

24. What is the difference between verification and validation?

Verification is a review without actually executing the process while validation is checking the product with actual execution. For instance, code review and syntax check is verification while actually running the product and checking the results is validation.

QA training Brampton and placement assistance, QA training Brampton and placement Mississauga, QA training Brampton and placement Mississauga, QA Training Canada, QTP jobs Toronto., 
source :http://www.indiabix.com

Testing Training Scarborough, Testing Training Toronto,

13. What group of teams can do software testing?

When it comes to testing everyone in the world can be involved right from the developer to the project manager to the customer. But below are different types of team groups which can be present in a project.

• Isolated test team
• Outsource - we can hire external testing resources and do testing for our project.
• Inside test team
• Developers as testers
• QA/QC team.

14. What impact ratings have you used in your projects?

Normally, the impact ratings for defects are classified into three types:

• Minor: Very low impact but does not affect operations on a large scale.
• Major: Affects operations on a very large scale.
• Critical: Brings the system to a halt and stops the show.

15. Does an increase in testing always improve the project?

No an increase in testing does not always mean improvement of the product, company, or project. In real test scenarios only 20% of test plans are critical from a business angle. Running those critical test plans will assure that the testing is properly done. The following graph explains the impact of under testing and over testing. If you under test a system the number of defects will increase, but if you over test a system your cost of testing will increase. Even if your defects come down your cost of testing has gone up.

16. What's the relationship between environment reality and test phases?

Environment reality becomes more important as test phases start moving ahead. For instance, during unit testing you need the environment to be partly real, but at the acceptance phase you should have a 100% real environment, or we can say it should be the actual real environment. The following graph shows how with every phase the environment reality should also increase and finally during acceptance it should be 100% real.

17. What are different types of verifications?

Verification is static type of s/w testing. It means code is not executed. The product is evaluated by going through the code. Types of verification are:

1. Walkthrough: Walkthroughs are informal, initiated by the author of the s/w product to a colleague for assistance in locating defects or suggestions for improvements. They are usually unplanned. Author explains the product; colleague comes out with observations and author notes down relevant points and takes corrective actions.
2. Inspection: Inspection is a thorough word-by-word checking of a software product with the intention of Locating defects, Confirming traceability of relevant requirements etc.

18. How do test documents in a project span across the software development lifecycle?

The following figure shows pictorially how test documents span across the software development lifecycle. The following discusses the specific testing documents in the lifecycle:

• Central/Project test plan: This is the main test plan which outlines the complete test strategy of the software project. This document should be prepared before the start of the project and is used until the end of the software development lifecycle.
• Acceptance test plan: This test plan is normally prepared with the end customer. This document commences during the requirement phase and is completed at final delivery.
• System test plan: This test plan starts during the design phase and proceeds until the end of the project.
• Integration and unit test plan: Both of these test plans start during the execution phase and continue until the final delivery. 

 Testing Training Scarborough, Testing Training Toronto, Testing Training Markham, Struts Training, Software Testing training Toronto  and placement assistance,

source :http://www.indiabix.com

Software Testing training Basics - Software Testing training toronto Interview Questions and Answers

7. What is configuration management?

Configuration management is the detailed recording and updating of information for hardware and software components. When we say components we not only mean source code. It can be tracking of changes for software documents such as requirement, design, test cases, etc.

When changes are done in adhoc and in an uncontrolled manner chaotic situations can arise and more defects injected. So whenever changes are done it should be done in a controlled fashion and with proper versioning. At any moment of time we should be able to revert back to the old version. The main intention of configuration management is to track our changes if we have issues with the current system. Configuration management is done using baselines.

8. How does a coverage tool work?

While doing testing on the actual product, the code coverage testing tool is run simultaneously. While the testing is going on, the code coverage tool monitors the executed statements of the source code. When the final testing is completed we get a complete report of the pending statements and also get the coverage percentage.

9. Which is the best testing model?

In real projects, tailored models are proven to be the best, because they share features from The Waterfall, Iterative, Evolutionary models, etc., and can fit into real life time projects. Tailored models are most productive and beneficial for many organizations. If it's a pure testing project, then the V model is the best.

10. What is the difference between a defect and a failure?

When a defect reaches the end customer it is called a failure and if the defect is detected internally and resolved it's called a defect.

11. Should testing be done only after the build and execution phases are complete?

In traditional testing methodology testing is always done after the build and execution phases.

But that's a wrong way of thinking because the earlier we catch a defect, the more cost effective it is. For instance, fixing a defect in maintenance is ten times more costly than fixing it during execution.

In the requirement phase we can verify if the requirements are met according to the customer needs. During design we can check whether the design document covers all the requirements. In this stage we can also generate rough functional data. We can also review the design document from the architecture and the correctness perspectives. In the build and execution phase we can execute unit test cases and generate structural and functional data. And finally comes the testing phase done in the traditional way. i.e., run the system test cases and see if the system works according to the requirements. During installation we need to see if the system is compatible with the software. Finally, during the maintenance phase when any fixes are made we can retest the fixes and follow the regression testing.

Therefore, Testing should occur in conjunction with each phase of the software development.

12. Are there more defects in the design phase or in the coding phase?

The design phase is more error prone than the execution phase. One of the most frequent defects which occur during design is that the product does not cover the complete requirements of the customer. Second is wrong or bad architecture and technical decisions make the next phase, execution, more prone to defects. Because the design phase drives the execution phase it's the most critical phase to test. The testing of the design phase can be done by good review. On average, 60% of defects occur during design and 40% during the execution phase.


Selenium Training course Toronto with job placement assistance.Selenium Training course Mississauga with job placement assistance., Software testing training Brampton,

Software Testing training toronto Interview Questions and Answers

Stepin2it.COM        Call 416-743-6333  for software testing training Toronto, Brampton, Scarborough,Mississauga.  
Software Testing training Toronto Basics

1. Can you explain the PDCA cycle and where testing fits in?

Software testing is an important part of the software development process. In normal software development there are four important steps, also referred to, in short, as the PDCA (Plan, Do, Check, Act) cycle.

Let's review the four steps in detail.

1. Plan: Define the goal and the plan for achieving that goal.
2. Do/Execute: Depending on the plan strategy decided during the plan stage we do execution accordingly in this phase.
3. Check: Check/Test to ensure that we are moving according to plan and are getting the desired results.
4. Act: During the check cycle, if any issues are there, then we take appropriate action accordingly and revise our plan again.

So developers and other stakeholders of the project do the "planning and building," while testers do the check part of the cycle. Therefore, software testing is done in check part of the PDCA cyle.

2. What is the difference between white box, black box, and gray box testing?

Black box testing is a testing strategy based solely on requirements and specifications. Black box testing requires no knowledge of internal paths, structures, or implementation of the software being tested.

White box testing is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.

There is one more type of testing called gray box testing. In this we look into the "box" being tested just long enough to understand how it has been implemented. Then we close up the box and use our knowledge to choose more effective black box tests.



The above figure shows how both types of testers view an accounting application during testing. Black box testers view the basic accounting application. While during white box testing the tester knows the internal structure of the application. In most scenarios white box testing is done by developers as they know the internals of the application. In black box testing we check the overall functionality of the application while in white box testing we do code reviews, view the architecture, remove bad code practices, and do component level testing.

3. Can you explain usability testing?

Usability testing is a testing methodology where the end customer is asked to use the software to see if the product is easy to use, to see the customer's perception and task time. The best way to finalize the customer point of view for usability is by using prototype or mock-up software during the initial stages. By giving the customer the prototype before the development start-up we confirm that we are not missing anything from the user point of view.

4. What are the categories of defects?

There are three main categories of defects:

1. Wrong: The requirements have been implemented incorrectly. This defect is a variance from the given specification.
2. Missing: There was a requirement given by the customer and it was not done. This is a variance from the specifications, an indication that a specification was not implemented, or a requirement of the customer was not noted properly.
3. Extra: A requirement incorporated into the product that was not given by the end customer. This is always a variance from the specification, but may be an attribute desired by the user of the product. However, it is considered a defect because it's a variance from the existing requirements.

5. How do you define a testing policy?

The following are the important steps used to define a testing policy in general. But it can change according to your organization. Let's discuss in detail the steps of implementing a testing policy in an organization.

• Definition: The first step any organization needs to do is define one unique definition for testing within the organization so that everyone is of the same mindset.
• How to achieve: How are we going to achieve our objective? Is there going to be a testing committee, will there be compulsory test plans which need to be executed, etc?.
• Evaluate: After testing is implemented in a project how do we evaluate it? Are we going to derive metrics of defects per phase, per programmer, etc. Finally, it's important to let everyone know how testing has added value to the project?.
• Standards: Finally, what are the standards we want to achieve by testing? For instance, we can say that more than 20 defects per KLOC will be considered below standard and code review should be done for it.

6. On what basis is the acceptance plan prepared?

In any project the acceptance document is normally prepared using the following inputs. This can vary from company to company and from project to project.

1. Requirement document: This document specifies what exactly is needed in the project from the customers perspective.
2. Input from customer: This can be discussions, informal talks, emails, etc.
3. Project plan: The project plan prepared by the project manager also serves as good input to finalize your acceptance test.

The following diagram shows the most common inputs used to prepare acceptance test plans.






Source :http://www.indiabix.com

Software testing training Toronto ,Brampton ,Markham. Mississauga,Scarborough

We specialize in providing best hand on professional software testing  training  Toronto services in Software QA Testing, QTP, Manual Testing, Performance Testing, Mobile Apps Testing, LoadRunner, and Automation Testing with latest updates.

Our instructors have 12 years of experience maintaining in the area of software testing.

We  provide live projects, which includes E Commerce Project, Baking Project, Health Care Project, , and many other domains.
Benefits of Software testing  training courses :
Software testing training Toronto ,Brampton ,Markham. Mississauga,Scarborough.
- Enrol once and enjoy a lifetime  access to all our live classes and materials.
- onsite/online  , instructor led class available .-
- Real time project work sessions on various domains.
- Walk into your next interview with confident as you attend our unlimited mock interview sessions.
- Help with Resume preparation by our experts.
- Recruiter driven placement service.100% job placment assiatnace
- course material is  built based on professional standards and employer insights
- Instructors are  ISTQB  Certified Experts in SOFTWARE TESTING  field and they bring years of industry experience into the training classes.
CALL 416-743-6333 EMAIL US :info@stepin2it.ca   www.stepin2it.com   www.stepin2it.com

QA training Toronto

1)Are you prepared for job market challenges?

2) Not receiving enough calls?

3) Struggling to find a job in today's job market?

The answer to these problems is to self assess your skills and seek professional help in retraining and upgrading your skills to make them more relevant to the current job market. Train for a Career not just a job and we can help.

STEPIN2IT is a Toronto Based premier training organization offering Training Programs across different genres in IT Industry. Our unique approach to training has helped many a student to improve their skill set and successfully find a job in today's tough market conditions. If you are interested in maximizing your potential and differentiating yourself from the rest of your competition, read further.

Programs are designed keeping in mind various levels of programming knowledge and skills. Beginner and Advanced programs available.

SKILLS UPGRADE Programs Offered:

* Software Testing Program -- 35 Hours offered on Weekdays/Weekends

For a list of all courses we offer and recruitment assistance, please contact us.

Call us: 416-743-6333 or visit us on www.stepin2it.com

Why choose US:

ü Mentorship & facilitation from Industry professionals

ü Small class sizes

ü Quality instructors (Certified & Experienced Professionals)

Guaranteed competence through hands on training approach

ü Cost-effective Training

ü FREE Reading Material

ü Access to network of Recruiters & Clients

ü 100% job assistance to all students through our sister recruiting company

ü Job Help & Support

ü Lab Access



WE DO PROVIDE ONLINE CLASSES.


Software testing training Toronto, software testing jobs Toronto, qa training Toronto, sqa training Toronto, QA TRNG, Testing TRNG Toronto, Testing Training Toronto, Testing Training Markham, Testing Training Scarborough, Testing Training Mississauga, QTP Training Toronto, QTP Training Mississauga, QTP Training Scarborough, Loadrunner Training Toronto, Loadrunner Training Mississauga, Loadrunner Training Scarborough, Selenium Training Toronto, Selenium

Manual testing toronto interview questions

Hi, I found this document to be helpful while planning for manual testing interview.Personal Question

1.    How you want to see yourself after 3 years?
I would be looking at a senior member in the organization where i could take some crucial decision and also leading a team of testers.

2.    What is your life dream?
To be a good manager for a team of young testers.

3.    Tell about your Positives and negatives?
My positives are group work and adjusting mentality. My negatives are difficulty in saying a 'no'.

4.    In what way you say that this work given to you will be done better than others?
My ability for team work, better understanding, and client coordination will give a better out put.

5.    When you realize for a relentless fault that you have done that will cause a major problem how you will react?
I will owe it up and explain to my seniors about how i did the mistake and apologize for the same. Then will find ways by which i can solve the issue.

6.    How will be your Problem management in absence of your immediate senior?
I will talk to my team members and take a collective decision and talk to senior over phone and tell him about the team decision and ask him for his advice and proceed as per his instructions.

7.    Tell me about your very good and very bad experience?
My good experience was after SIT a few bugs were not rectified and send to client the developers took the responsibility for the bugs. When the same issue was raised by the client the developers said that they had rectified it. Since the issue was raised by the client it     directly came top the quality dept from our top management and since i had screen shoots and explained the situation to my seniors before sending the release i was not affected by it.

8.    When you are forced to do the work that is not coming under your responsibility what will you do?
It will basically depend on the scope of the project. If it is not there in the scope will tell them it is not in our project scope. But if we happen to see that the client is a very important for the organization will try to put in some extra effort and do the work for the client.


Software testing training Toronto,Software testing training Brampton,Software testing training Mississauga,
Software testing training Markham,Software testing training Scarborough,
QA Training Toronto,QA Training Brampton,QA Training Mississauga, QA Training Markham,QA Training Scarborough,QA Training Canada.









Technical Questions

1.    What is Software Testing?
Software testing is a testing to make a product bug free. Testing involves operation of a system or application under controlled conditions and evaluating the results. The controlled conditions should include both normal and abnormal conditions.

2.    What is the Purpose of Testing?
To give a product to the client that is bug free and working up to the expectation of the client as his requirement.

3.    What types of testing do testers perform?
Unit Testing, Integration Testing, SIT, UAT, Black Box and White Box.

4.    What is the Outcome of Testing?
A bug free product as per the expectation of the client.

5.    What kind of testing have you done?
Unit Testing and SIT.

6.    What is the need for testing?
To give a product to the client that is bug free and working up to the expectation of the client as his requirement.

7.    What are the entry criteria for Functionality and Performance testing?
Functionality Testing: All the relevant documents should be prepared (Test condition, Cases) and signed off by the client. The testing environment should be freeze.
Performance testing: The application should be stable and SIT should have been done.

9.    What is test metrics?
Test Metrics is a mechanism to know the effectiveness of the testing that can be measured quantitatively. It is a feedback mechanism to improve the Testing Process that is followed currently.
Test metrics should cover basically 3 things:
a.    Test coverage.
b.    Time for one test cycle.
c.    Convergence of testing.

10.    Why do you go for White box testing, when Black box testing is available?
To check the internal logic and to cover all basis path and loop testing.

11.    What are the entry criteria for Automation testing?
The entry criteria is that the application should be stable.

12.    When to start and Stop Testing?
Testing can start once the coding is completed and application is stable or a part of the module coding is completed. Testing can end once all the bugs raised by the tester is rectified or differed for future enhancement.



13.    What is Quality?
A product that is fit to use. Quality means getting things right at the first time when it is done.

14.    What is Baseline document, Can you say any two?
These documents are used for testing and developing they are Functional Specification and Business Requirement.

15.    What is verification?
The process of evaluating a system or component to determine whether the products of the given development phase satisfy the conditions imposed at the start of that phase. [IEEE] [Did we develop the right product?]

16.    What is validation?
Determination of the correctness of the products of software development with respect to the user needs and requirements. [Did we develop the product right?]

17.    What is quality assurance?
A planned and systematic set of activities to ensure that variances in processes are clearly identified, assessed and improving defined processes for fulfilling the requirements of customers and product or service makers.

A planned and systematic pattern of all actions necessary to provide adequate confidence that the product optimally fulfils customer's expectations.

A planned and systematic set of activities to ensure that requirements are clearly established and the defined process complies with these requirements.

18.    What is quality control?
Quality control is a process by which actually helps us in delivering a product that is bug free and maintains some standards

19.    What are SDLC and TLC?
SDCL is Software Development Life Cycle and TLC is Testing Life Cycle

20.    What are the Qualities of a Tester?
A tester should have a good logical understanding of the application and his job is to see ways by which he can find errors in the system. He should also give some good constructive ideas to the development team to develop a good product.

21.    When to start and Stop Testing?
Testing can start once the coding is completed and application is stable or a part of the module coding is completed. Testing     can end once all the bugs raised by the tester is rectified or differed for future enhancement.

22.    What are the various levels of testing?
Unit Testing
Integration Testing
SIT
UAT


23.    What are the types of testing you know and you experienced?
Unit Testing
Integration Testing
SIT

24.    What exactly is Heuristic checklist approach for unit testing?
It is one of the techniques used in usability testing

25.    After completing testing, what would you deliver to the client?
Test Closure Documents like Test Case, Test Conditions, Traceability Matrix, Defect Report, Test Summary Report, Test Data and Down Time Report.

26.    What is a Test Bed?
It is set of data we input when we get a blank database for starting the testing.

27.    What is a Data Guidelines?
Guidelines which are the inputs for preparing the data.

28.    Why do you go for Test Bed?
When we get a empty database for testing it will not be possible for us to start testing so we need to input some initial data so that we can start the testing (so that we do not get data set up problems).

29.    What is Severity and Priority and who will decide what?
Severity is to tell how whether the bug is Critical, Medium, or Low. If it is critical it is a show stopper if it is medium it has some functional problem but can proceed if it is low some minor alignment or look and feel problem.
Priority is when the bugs will be rectified.
Severity is decided by the testers and priority is decided by the developers.

30.    Can Automation testing replace manual testing? If it so, how?
No automation cannot replace manual testing. Only if an application is stable can we go for automation. To find whether an application is stable we need to do Manual testing.

31.    What is a test case?
Test case is derived from a test condition and it tells what functionality we are going to test for a given condition and the expected result.

32.    What is a test condition?
Test condition is derived from BR/FS, which reflects the actual customer requirements.

33.    What is the test script?
It tells us the flow or a step-by-step process that we are going to execute along with the test data.

34.    What is the test data?
It is a data that we are going to use to test a particular functionality.

35.    What is an Inconsistent bug?
If we get a bug that cannot be simulated or it come some times only then it is called inconsistent bug.
36.    What is the difference between Re-testing and Regression testing?
Retesting is one which is done fully and regression is one it is done related to a bug and the places it can have an impact.

37.    What are the different types of testing techniques?
Equivalence Class Partisan, Boundary Value Analysis, Error Guessing.

38.    What are the risks involved in testing?
Schedule Risk
Resource Risk
Technology Risk

39.    Differentiate Test bed and Test Environment?
Test bed is initial data that is entered to start testing. Test Environment is the environment in which we are going to test the application.

40.    What is the difference between quality and testing?
Quality is a process to deliver a bug free product. Testing is a part of quality.

41.    What is the difference between White & Black Box Testing?
White box is used for code checking and see the flow of loops.
Black box we do a functionality testing without looking at the coding.

42.    What is the difference between Quality Assurance and Quality Control?
Quality control is a process by which actually helps us in delivering a product that is bug free and maintains some standards.
Quality Control is a process by which we maintain certain standard so that we develop a product which will have some pre defined standards.

43.    What is the difference between Testing and debugging?
Testing is a process by which we identify the bugs and debugging is a process by which the developers identify the bugs and rectifies it.

44.    What is the difference between bug and defect?
Defect is a deviation from the FS/BR. A bug is an error found in the application.

45.    What is the difference between verification and validation?
Verification asks, "Is the product being built right?" It is the process of determining whether or not the products of a given phase of the software development cycle fulfill the established requirements. Validation asks, "Is the right product being built?" It evaluates software at the end of the development lifecycle to ensure that the product not only complies with standard safety requirements and the specific criteria set forth by the customer, but performs exactly as expected.

46.    What is the difference between functional spec. and Business requirement specification?
Functional specification is used for SIT and Business requirement is used for UAT.  FS is more technical used for development process and BR is more useful towards the analysis point.



47.    What is the difference between unit testing and integration testing?
Unit is the basic level of testing and tries to validate more towards field level validation. Integration testing is done at a module level.

48.    What is the diff between Volume & Load?
In volume number of transaction is increased and the no of user constant in load the no user will be increased and transaction is kept constant.

49.    What is diff between Volume & Stress?
In volume number of transaction is increased and the no of user is constant in stress both user and transaction is increased.

50.    What is the diff between Stress & Load Testing?
In stress both user and transaction is increased in load the no user will be increased and transaction is kept constant.

51.    What is the Diff between Two Tier & Three tier Architecture?
Business/ application logic resides in a separate system in 3 tier where as in 2 tier it resides in the front end system.

52.    What is the diff between Client Server & Web Based Testing?
Client server it is a controlled environment we concentrate more at the functionality where as in web based we check more towards the security of the application.

53.    What is the diff between Integration & System Testing?
Integration testing we test the interfaces in system testing we test the functionality.

54.    What is the Diff between static and dynamic?
Static Testing: Analysis of a program carried out without executing the program.
Dynamic Testing: Testing software through executing it.

55.    What is the diff between alpha testing and beta testing?
Alpha testing is done by user is performed at the development site.
Beta testing is done by user is performed at the client site.

56.    What are the Minimum requirements to start testing?
The application should be stable to start testing.

57.    What is Smoke Testing & when it will be done?
Smoke testing is like adhoc testing and it is normally done at the sanity testing level or during the last stage of testing to see that no error is there in the application.

58.    What is Adhoc Testing? When it can be done?
Adhoc testing is a free form testing it can be done if we do not have much information about the application or during the normal testing process also for it helps to find some defects that are not covered in the conditions.




59.    What is security testing?
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

60.    What is database testing?
To check if the data base get updated once a transaction is posted in the front end and also to see if the data gets updated in the data base correctly.

61.    What is the relation ship between Quality & Testing?
Testing is a part of quality and testing tell us how to improve the quality of a product and where we have to concentrate.

62.    How do you determine, what to be tested?
Based on the FS and the priority of the modules that need to delivered we determine what needs to be tested.

63.    How do you go about testing a project?
Start with the initiation, planning, execution, defect management and test closure.

64.    What is the Initial Stage of testing?
Initiation.

65.    What is Web Based Application Testing?
Web Based Application Testing is End-to-end system testing with dynamically created test actions based on results from previous test actions.

66.    What is Two Tier & Three tier Architecture?
2 Tier: Refers to client/server architectures in which the user interface runs on the client and the database is stored on the server. The actual application logic can run on either the client or the server.
3 Tier: A special type of client/server architecture consisting of three well-defined and separate processes, each running on a different platform:

a.    The user interface, which runs on the user's computer (the client).
b.    The functional modules that actually process data. This middle tier runs on a server and is often called the application server.
c.    A database management system (DBMS) that stores the data required by the middle tier. This tier runs on a second server called the database server.

67.    What is the use of Functional Specification?
It gives an over view of the application and helps us in planning, estimation, duration and helps us in writing test case and conditions.

68.    Why do we prepare test condition, test cases, and test script (Before Starting Testing)?
To deliver a good product and also to show that we have covered all the scenarios in the application and we have fully covered the application.

69.    Is it not waste of time in preparing the test condition, test case & Test Script?
No

70.    How do you go about testing of Web Application?
To concentrate more towards the security and loading of different pages and links.

71.    How do you go about testing of Client Server Application?
To concentrate more towards the functionality part.

72.    What is meant by Static Testing?
It is testing without executing, just a walk through of the application.

73.    Can the static testing be done for both Web & Client Server Application?
Yes

74.    In the Static Testing, what all can be tested?
Baseline documents, test deliverables before test execution and closer.

75.    Can test condition, test case & test script help you in performing the static testing?
Yes
76.    What is meant by dynamic testing?
Is normal testing done by executing the application.

77.    Is the dynamic testing a functional testing?
Yes

78.    Is the Static testing a functional testing?
No

79.    What are the functional testing you perform?
SIT

80.    What is meant by Alpha Testing?
Alpha testing is done by user is performed at the development site.

81.    What kind of Document you need for going for an Functional testing?
Functional Specification.

82.    What is meant by Beta Testing?
Beta testing is done by user is performed at the client site.

83.    At what stage the unit testing has to be done?
It is done at the initial stage after completing the coding and we find the application to be stable.

84.    Who can perform the Unit Testing?
Normally the developers are better to do unit testing. If it is not done by them then it can be done by the testers.

85.    When will the Verification & Validation be done?
Verification before testing and validation during testing.




86.    What is meant by Code Walkthrough?
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

87.    What is meant Code Review?
A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards. It is also called as Code Inspection.

88.    What is the testing that a tester performs at the end of Unit Testing?
Integration Testing.

89.    What are the things, you prefer & Prepare before starting Testing?
Understanding the application fully, test conditions, test case, test data, traceability matrix.

90.    What is Integration Testing?
IT checks to see the integration (flow of information from one module to another) between different modules.

91.    What is Incremental Integration Testing?
Module by module testing is Incremental Integration Testing.

92.    What is meant by System Testing?
System testing is functional testing.

93.    What is meant by SIT?
System Integration Testing.

94.    When do you go for Integration Testing?
Once unit testing is done and application is stable.

95.    Can the System testing be done at any stage?
No only after we complete unit it is advisable to go for System testing.

96.    What are stubs & drivers?
Stub: A skeletal or special-purpose implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it.
Driver: A program or test tool used to execute software against a test case suite.

97.    What is the final Stage of Integration Testing?
SIT.

98.    Where in the SDLC, the Testing Starts?
After Coding.

99.    What is the Outcome of Integration Testing?
A stable application that can be sent to production for SIT.

100.    What is meant by GUI Testing?
To check for GUI components and the their functionality.

101.    What is meant by Back-End Testing?
It is database testing.

102.    What is Compatibility Testing?
Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

103.    What is Usability Testing?
Usability testing is to see how good the product is as per the requirements of the customer and also to see how user friendly the product is.

104.    What is the Importance of testing?
To deliver a bug free product as per the requirement of the client.

105.    What is meant by regression Testing?
Regression Testing is used to check the status of bugs that we sent top developers and to see if they have any impact due to the rectification of the bugs sent.

106.    When we prefer Regression & what are the stages where we go for                                                                                Regression Testing?
After the fixing of the defects by the developers we go for regression.

107.    What is performance testing?
It is testing to see what happens to the application under different loads of data.

108.    What is the Performance testing; those can be done Manually & Automatically?
It is testing to see what happens to the application under different loads of data. It is normally done using tools (automation).

109.    What is Volume, Stress & Load Testing?
In volume number of transaction is increased and the no of user constant in load the no user will be increased and transaction is kept constant in stress both user and transaction is increased.

110.    What is a Bug?
It is a defect in the product that dose not match with the FS or the expected result.

111.    What is a Defect?
It is a deviation from the FS that lead to error.

112.    What is the defect Life Cycle?
It tells us what happens after a bug is raised by the tester.

113.    What is the Priority in fixing the Bugs?
Critical bugs are normally fixed first followed by medium and then low normally.


114.    Explain the Severity you rate for the bugs found?
Severity is to tell how whether the bug is Critical, Medium, or Low If it is critical it is a show stopper if it is medium it has some functional problem but can proceed if it is low some minor alignment or look and feel problem.

115.    Diff between UAT & IST?
For UAT we use the BR, for IST we use the FS.

UAT is done normally by the end user with a good domain knowledge and IST by the Testers.

In IST we do testing based on condition and in UAT it will be mostly done in scenario based.

116.    What is meant by UAT?
It is User Acceptance Testing.

117.    What all are the requirements needed for UAT?
Sit should have been done, BR document should be available.

118.    What is risk analysis?
It helps us to find what are the risks associated with a project.
Schedule Risk
Resource Risk
Technology Risk

119.    How to do risk management?
By finding out the expected risk before testing.

120.    What are test closure documents?
Test Closure Documents like Test Case, Test Conditions, Traceability Matrix, Defect Report, Test Summary Report, Test Data and Down Time Report.

121.    What is traceability matrix?
It is document which tells whether we have tested completely.

122.    What ways you followed for defect management?
We used tracebility matrix and Orbi Solve.