Вы находитесь на странице: 1из 10

Re: What is difference between static and dynamic and testing?

Answer Static testing: #3 *finding the defect in earlier

stage. *verification performed without execution like 1.code inspection 2.reverse engineering(through testing understanding the domain) Dynamic testing: *verification or validation performed by execution.

Re: write 3 main test cases for excel sheet? Answer Hi Friends, #1

1. click on start->programs-> Verify is there is Ms office. 2. Check Ms-Excel in that Ms Office. 3. Click on It,check whether is opening or not. 4. Check the window is blank excel sheet. 5. If close the window is it asking for saving the document or not even though there is no data. I think this simple way of writing test cases for excel sheet.
1) How to test session ? 2) There is a website in which the user has to register to use its features. Suppose one user has registered in that site by paying some amount only for 1 month. Now i want to test the application that the user should not use the features of the site after 1 month. How to test it? The tester cannot wait for 30 days to test it....bear in mind..Thanks in advance... Answer Ans 1: One way is to validate # 1 cookies if this is web based

application. If there is any

database interaction then you can validate using both data base and cookies. Ans 2: The details provided looks incomplete. Without time stamp comparison in application this feature cannot be tested. e.g. when the user is registering in the site paying some amount then application can store the system time or time of registration or store in database : system time + 1 month as expiration time. Further there can be a check to compare the expiration time. After knowing the logic what developer has put in application, you can change the time stored in data base to test the expiration conditions. Here, you have to test boundaries.
What's a 'test plan'?

A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort.
What's a 'test case'?

A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results. Note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. For this reason, it's useful to prepare test cases early in the development cycle if possible.
What can be done if requirements are changing continuously?

A common problem and a major headache. Work with the project's stakeholders early on to understand how requirements might change so that alternate test plans and strategies can be worked out in advance, if possible. It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the application from scratch.

If the code is well-commented and well-documented this makes changes easier for the developers. Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes. The project's initial schedule should allow for some extra time commensurate with the possibility of changes.

what is the call-pair testing? there is any length for Test case? A call-pair is the connection between two functions in which one function "calls" the other function. Testing the functions where one function calls or refers the another function is termed as Call-pair Testing. For example, you have to book a ticket in the Railway reservation page. When "Book Ticket" button is clicked it will call the another function "Unallocated Seats" to check for the availability status. Here the function Book Ticket is the main functionality which is tested, but while testing this function it will call the another function "Unallocated seats" for checking the availability status. Testing this type of function will come under Call Pair Testing. So, in this case both the functions are validated. Call pair testing is mostly used in the Integration Testing, where after unit testing, you will integrate the unit tested components and test whether as a system it performs as per the specifications.
What if the application has functionality that wasn't in the requirements?

It may take serious effort to determine if an application has significant unexpected or hidden functionality, and it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies

that were not taken into account by the designer or the customer. If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only effects areas such as minor improvements in the user interface, for example, it may not be a significant risk.
What if an organization is growing so fast that fixed QA processes are impossible?

This is a common problem in the software industry, especially in new technology areas. There is no easy solution in this situation, other than: Hire good people Management should 'ruthlessly prioritize' quality issues and maintain focus on the customer Everyone in the organization should be clear on what 'quality' means to the customer
How does a client/server environment affect testing?

Client/server applications can be quite complex due to the multiple dependencies among clients, data communications, hardware, and servers. Thus testing requirements can be extensive. When time is limited (as it usually is) the focus should be on integration and system testing. Additionally, load/stress/performance testing may be useful in determining client/server application limitations and capabilities. There are commercial tools to assist with such testing. (See the 'Tools' section for web resources with listings that include these kinds of test tools.)
How can World Wide Web sites be tested?

Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort. Other considerations might include: What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required under such loads (such as web server response time, database query response times). What kinds of tools will be needed for performance testing (such as web load testing tools, other tools already in house that can be adapted, web robot downloading tools, etc.)? Who is the target audience? What kind of browsers will they be using? What kind of connection speeds will they by using? Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)? What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations, applets, etc. load and run)? Will down time for server and content maintenance/upgrades be allowed? how much? What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it expected to do? How can it be tested? How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant connection requirements and testing? What processes will be required to manage updates to the web site's content, and

what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.? Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers? Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site?? How will internal and external links be validated and updated? how often? Can testing be done on the production system, or will a separate test system be required? How are browser caching, variations in browser option settings, dial-up connection variabilities, and real-world internet 'traffic congestion' problems to be accounted for in testing? How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the system and do they require testing? How are cgi programs, applets, javascripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested? Some sources of site security information include the Usenet newsgroup 'comp.security.announce' and links concerning web site security in the 'Other Resources' section. Some usability guidelines to consider - these are subjective and may or may not apply to a given situation (Note: more information on usability testing issues can be found in articles about web site usability in the 'Other Resources' section): Pages should be 3-5 screens max unless content is tightly focused on a single topic. If larger, provide internal links within the page. The page layouts and design elements should be consistent throughout a site, so that it's clear to the user that they're still within a site. Pages should be as browser-independent as possible, or pages should be provided or generated based on the browser-type. All pages should have links external to the page; there should be no dead-end pages. The page owner, revision date, and a link to a contact person or organization should be included on each page.

In V-model both testing and development done simultaneosly,we know that.But how can you say that both happen parallely.how is it related in real time?This question has been asked to me today only.Can any one please help me on this? Answer In V-model while development is # 2 going on, QA team will have

the work of preparing test plans, test cases and peer review, Client review etc... of those testcases, and helping the development team in understanding the requirements as the QA team would have gone through the requirment docs throughly for writing testcases.
What is the difference between bug,defect, error, failulre, fault & mistake? Answer Bug/Defect : #5

A bug or defect is a flaw in a

system or system component which may cause the system or the system component fail to perform its desired action. Error : It is a human mistakes Failure : If the product or the application falied to perform its desired action according to enduesr prospective. Fault : It is a incorrect intermediate statement encounter during program execution Mistake : Nothing but error raised by human action

can any one give the format of writing test cases in excel sheet Test Case ID Requirement Id Test Name Prerequisites Description (Steps to execute) Expecte Result Actual Result Status Remarks
e: how to write test case for Add, Delete,Update,search and Edit button. Please its urgent.Could anybody help me as soon as possible Answer Hi..., #1

Main Functionalities: 1. You check the buttons are enabled 2. Check the buttons when its enabled and when its disabled

3. After click the button, page responding or not. Add: 1. When u have click the add button, record should be added. Delete: 1. When u have click the delete button, record should be deleted. Update: 1. Modify value should be updated when u have click this button. Search: Searching result should be display when u have enter the search button Search button should be enabled after enter the search value Edit: Edit button should be enable when i have to edit the value Low level test case: 1. Check the font size 2. Chenk the font color 3. Check the spelling mistake 4. Check the button size (questions asked in interview)hi every one can any one please answer to this questions.these questions were asked in an interview.i have another interview next week . 1.when the time schedule is tight how will you approch the testing,and the relese is nearing and we need to finish testing how can we follow in that case.do we need to exicute all the test cases or can priortise and leave some to next relase. 2. when a new feature is added to the existing application we need to add new test cases but after that

do we need to change all the existing test cases and while running do we need to exicute entire application test cases or only the new feature test cases and related new feature test cases. 3.do you have any situation where you have to write and exicute the test cases same time, how will you follow.does it happens in real time. 4.example of bug which is not reproducible.like tester say that there is bug and developer say no can some example of such bugs. 5.during regression testing some times do we need to add new some additional test cases to test that bug. (1)The time schedule is tight,and release time nearing, then , in such case, we may execute main test cases ie main functionality in application.A triage meeting is kept with the client , for what are the functions he need urgently. after that the remaining functions can be tested in next release. (2)If any new feature is added then , obviously new test case is to be written for the added feature. it is not necessary to change all the test cases, but if the added test case is interfaced with sum other test case then the test case cases are executed with those interfaces also. (3)Iam not sure for this question. but according to my knowledge,this is rare case to happen in same time. (if U get answer for this question then kindly mail to me) (4)This may depend on application. But a Tester can justify the developer that , In my(tester) BRD this requirement is given, which is not executing in ,wat U have developed. (5)I think no need for additional test case. Because, Regression testing is done for repeated bugs. But if the

bugs are occur each time, we have to test our test case, that the test data is occurdung to the BRD,If not then new or additional test case is to be written. Sameena you are right for 2, and please find few things that I could give you based on knowledge on testing (3) Yes we do have a sutiatuation where we wont be having much time for planning when the project cycle follows agile methodology. Here testing will be performed based on few prepared TCs and user / project knowledge is more important to test these product as we dont have proper document. This agile methodology is followed up to where the TCs and defects are not documented propery but communicated to developer at once to fix the bug.this method is followed up when the time and cost of the project is estimated very low. (4) Example : time out error, work flow errors (for web based applications) error may occur due to data discrepancies Time out error occurs when the Web service of a page is ideal or server is down we do face time out error which cannot be reproduce frquently we do sometimes face workflow error and fatal errors that does not occur frequently. errors based on data discrepancies are also not reproducible, for example, take a simple application - login u want check a web page with user name and password with ok button there may be 1 customisable field that u can add according to the client client 1 need ok button alone client 2 need ok and region of the user to login

so u ad having 1 customisable fields to add that drop down to client 2 and present the ok button alone to client 1 When u try to add a customisable field ther would not be any datas for that field to retrive from DB bcoz of that there may some error occurs and when the Data is added to it, it may work fine. (5) For regresstion testing we wont change or add TCs to TC set. Bug might have been raised based on existing TCs. So no new TCs are added. And retesting is different and regression testing is different
Interviewer can ask you to explain what you did in all the mentioned projects? What was the project about? What was your roll? For Which testing type you were responsible? Have you wrote test cases? If you did automation then How you performed automation testing on those projects?