Since it’s rarely possible to Test every possible aspect of an Application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include: Use risk analysis [...]
100% bugfree testing is not at all possible. If we say 100% testing is completed, then that will be the end to any software. Then why we are getting so many projects still. Because we didn’t develop a bugfree project. We can’t develop a bugfree project. Take an example, Why Win Runner, oracle has so [...]
Common factors in deciding when to stop Testing: Show stoppers encountered Too many minor bugs pending to be fixed Deadlines (release deadlines, testing deadlines, etc.) Test cases completed with certain percentage passed Test budget depleted Coverage of code/functionality/requirements reaches a specified point Bug rate falls below a certain level Beta or alpha testing period ends [...]
A software project Test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software Product. The completed document will help people outside the test [...]
Define load, performance and Stress testing? What are the goals of a performance testing of a Web Application? State a generalized process for load Test? Or explain how you did it previously. How do you determine user soad for a perf test of a Web application? What do you understand by the terms ‘Response Time’, [...]
This was the interview question asked at oracle Corporation to a Test Engineer: What do you do if Developer not accepting your bug? This question is mainly to test you patience, planning and approach towards an issue in the team or organization. Act smartly to answer this question. As per our experience and analysis, we [...]
Following are some challenges while testing software 1. Requirements are not freeze. 2. Application is not testable. 3. Tester & Developer communication is not happening 4. Defect in defect tracking system 5. Miscommunication or no Communication 6. Bug in software development tools. 7. Proper decision making and team management 8. Time pressures 9. Lack of [...]
After completion of software Integration and Integration testing, the development team is releasing a software build to Test engineer team. The testing team is conducting system testing on that software in two sub levels such as Functional Testing Non-Functional Testing Functional testing is concentrating on customer requirements and the Non-Functional testing is concentrating on customer [...]
Non-Functional Testing: After completion of functional testing successfully, the testing team is concentrating on non-functional testing. During non-functional testing, the testing team is concentrating on customer expectations or software characteristics. This non-functional testing is classified into below sub testing topics. Usability Testing (UI Check) Manual Check (Help documents testing) Compatibility Testing OR Portability Testing Configuration Testing [...]
Functional Testing: It’s a mandatory testing level, during this Test the testing team is validating a software build functionality in terms of below factors with respect to customer requirements. Behavioral / GUI: The changes in properties of Objects OR controls in a software is called behavioral or GUI. Input Domain: Whether the Objects are taking [...]