Interview Questions and Answers

Interview Questions And Answers

Manual, automation, qtp,qc, bugzilla, agilemethodology, functional ...More
Manual, automation, qtp,qc, bugzilla, agilemethodology, functionaltesting, non functionaltesting, black box,structural, peer to peertesting, white boxtesting, static testing,dynamic testing,Assertion Testing. (NBS), Automated Testing ,Background testing, Bug,Beta Testing, Benchmarks,Benchmarking, Big-bangtesting , Boundary ValueAnalysis , Cause EffectGraph Less

Interview Questions and Answers

to get instant updates about 'Interview Questions And Answers' on your MyPage. Meet other similar minded people. Its Free!


All Updates

No Detailed Information available.

No feeds found

Posting your question. Please wait!...


Manual, automation, qtp, qc, bugzilla, agile methodology, functional testing, non functional testing, black box, structural, peer to peer testing, white box testing, static testing, dynamic testing, Assertion Testing. (NBS) , Automated Testing , Background testing, Bug, Beta Testing, Benchmarks, Benchmarking, Big-bang testing , Boundary Value Analysis , Cause Effect Graph


10:36 AM - 13 Apr 14

Explain Smoke Testing in Easy and Simple Way?

Smoke Testing is always confused with Sanity Testing Example but in reality both the testing examples are different with each other. Here I am writing Smoke Testing Example in such a way that your confusion can definitely be removed by seen the example.Now before us proceeding towards Smoke Testing Example it is very important for us to first take a warm look at Smoke Testing.Smoke Testing – Brief LookSmoke Testing is considered as the surface level testing which is always used to validate that build provided by development to QA team is ready to accept for further testing. In Smoke Testing we test the major point’s means major functionality of the application and it is also known by the name Build Acceptance Testing (BAT).Smoke Testing Example – Real OneSmoke Testing Example is given below which is totally based on Real Practical Scenario means which totally reflect your software testing process in a company environment.For example we are working in a small project named Employee Management System and in this project there are four modules like New Employee Module, Existing Employee Module, Admin Module, User Module etc. So firstly in this four modules development team performs the Smoke Testing by executing all the major functionality of modules like New Employee is able to login or not and after login new employee can seen the record of the existing employee or not, and employee that is created can also be edited, deleted or not.So in this way Smoke Testing is done by development team before releasing means submitting the build to the Software Testing team.Now when the build is hand over means releasing to the testing team than the software testing team has to check whether to accept or reject the build by checking the major functionality of that build. So as you know we are taking the example Employee Management System, so our build is Employee Management System.Now when the build (Employee Management System) is submitted means release to the testing team than the testing team has to check whether to accept the build (Employee Management System) or not by checking the major functionality of the build like employee is able to login or not and after login they can seen the existing employee record or not and after that logout easily or not. So this is the Smoke Testing done by Software Testers.Keep in MindPlease keep one thing in mind that firstly Smoke Testing is done by developer before releasing the build to the tester and when developers done the smoke testing than they releasing the build to the testing team and then testing team decide whether to accept the build or not for performing further testing by checking the major or you can say essential functionality of the build.ConclusionSmoke Testing Example is widely used and Smoke Testing is always done whenever we have to accept the build means before accepting the build we dosmoke testing to check whether we accept the build or rejected (Refused).Answers Here...
07:30 AM - 14 Feb 14

Automated Testing

1. Does automation replace manual testing?Automation is the integration of testing tools into the test environment in such a manner that the test execution, logging, and comparison of results are done with little human intervention. A testing tool is a software application which helps automate the testing process. But the testing tool is not the complete answer for automation. One of the huge mistakes done in testing automation is automating the wrong things during development. Many testers learn the hard way that everything cannot be automated. The best components to automate are repetitive tasks. So some companies first start with manual testing and then see which tests are the most repetitive ones and only those are then automated.As a rule of thumb do not try to automate:Unstable software: If the software is still under development and undergoing many changes automation testing will not be that effective. Once in a blue moon test scripts: Do not automate test scripts which will be run once in a while. Code and document review: Do not try to automate code and document reviews; they will just cause trouble. The following figure shows what should not be automated.All repetitive tasks which are frequently used should be automated. For instance, regression tests are prime candidates for automation because they're typically executed many times. Smoke, load, and performance tests are other examples of repetitive tasks that are suitable for automation. White box testing can also be automated using various unit testing tools. Code coverage can also be a good candidate for automation.  2. How does load testing work for websites?Websites have software called a web server installed on the server. The user sends a request to the web server and receives a response. So, for instance, when you type the web server senses it and sends you the home page as a response. This happens each time you click on a link, do a submit, etc. So if we want to do load testing you need to just multiply these requests and responses "N" times. This is what an automation tool does. It first captures the request and response and then just multiplies it by "N" times and sends it to the web server, which results in load simulation.So once the tool captures the request and response, we just need to multiply the request and response with the virtual user. Virtual users are logical users which actually simulate the actual physical user by sending in the same request and response. If you want to do load testing with 10,000 users on an application it's practically impossible. But by using the load testing tool you only need to create 1000 virtual users. 3. Can you explain data-driven testing?Normally an application has to be tested with multiple sets of data. For instance, a simple login screen, depending on the user type, will give different rights. For example, if the user is an admin he will have full rights, while a user will have limited rights and support if he only has read-only support rights. In this scenario the testing steps are the same but with different user ids and passwords. In data-driven testing, inputs to the system are read from data files such as Excel, CSV (comma separated values), ODBC, etc. So the values are read from these sources and then test steps are executed by automated testing.Answers Here...
08:11 PM - 02 Oct 13

Waterfall model

The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed fully before the next phase can begin. At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. In waterfall model phases do not overlap.Diagram of Waterfall-model:               Advantages of waterfall model: Simple and easy to understand and use. Easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process. Phases are processed and completed one at a time. Works well for smaller projects where requirements are very well understood. Disadvantages of waterfall model: Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage. No working software is produced until late during the life cycle. High amounts of risk and uncertainty. Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects. Not suitable for the projects where requirements are at a moderate to high risk of changing. When to use the waterfall model: Requirements are very well known, clear and fixed. Product definition is stable. Technology is understood. There are no ambiguous requirements Ample resources with required expertise are available freely The project is short.Answers Here...
08:06 PM - 02 Oct 13

Incremental model

In incremental model the whole requirement is divided into various builds. Multiple development cycles take place here, making the life cycle a“multi-waterfall” cycle. Cycles are divided up into smaller, more easily managed modules. Each module passes through the requirements, design, implementation and testing phases. A working version of software is produced during the first module, so you have working software early on during the software life cycle. Each subsequent release of the module adds function to the previous release. The process continues till the complete system is achieved.For example:                                                       In the diagram above when we work incrementally we are adding piece by piece but expect that each piece is fully finished. Thus keep on adding the pieces until it’s complete.Diagram of Incremental model:          Advantages of Incremental model: Generates working software quickly and early during the software life cycle. More flexible – less costly to change scope and requirements. Easier to test and debug during a smaller iteration. Customer can respond to each built. Lowers initial delivery cost. Easier to manage risk because risky pieces are identified and handled during it’d iteration. Disadvantages of Incremental model: Needs good planning and design. Needs a clear and complete definition of the whole system before it can be broken down and built incrementally. Total cost is higher than waterfall. When to use the Incremental model: Requirements of the complete system are clearly defined and understood. Major requirements must be defined; however, some details can evolve with time. There is a need to get a product to the market early. A new technology is being used Resources with needed skill set are not available There are some high risk features and goals.Answers Here...

View more rss »


View more links »

No messages found
Suggested Pages
Tell your friends >
about this page
 Create a new Page
for companies, colleges, celebrities or anything you like.Get updates on MyPage.
Create a new Page
 Find your friends
  Find friends on MyPage from