Topic 1 DS. Name the type of bugs which can be related with coding of a program?

Ans It can be syntax error and a syntactical errors. AS. Being a tester what will be your role in software development. What can be best required from a software tester? Ans To find the bugs To find the bugs and find them as early as possible To find the bugs, find them as early as possible and make sure they get fixed. Required from a good software tester Must be explorer Must be a troubleshooter Must be relentless, keeps on trying Must be creative, perfectionists Must have a good judgment Must be tactful and diplomatic

DL. Define the term software bug. If there is a bug what can be possible causes for it. Also discuss its role over cost of software project? Ans Anything which makes a software to behave abnormally then required are called as bugs its major causes can be 1. SW doesnt do something the specification says it should do. 2. SW does something the specification says it shouldnt do. 3. SW does something the specification doesnt mention. 4. SW doesnt do something the specification doesnt mention but should. 5. SW is difficult to understand, hard to use, slow, or in the testers eyes will be viewed by the end user as just plain not right. The bug can have following impacts over the cost of software project

Found early might cost next to nothing or very low If found until the software is coded and tested might be manageable. If customer finds it, then it can be thousands or even millions of dollars.

LA. For developing a software for hospital compare the implementation of software implementation models Big-Band model, Code-and-Fix model, and waterfall model? Ans - The Waterfall Model consists of the following main steps: 1. Requirements Analysis. 2. System Design and Program Design. 3. Coding. 4. Testing. Disadvantages of the Waterfall Model: You can not think out all the detailed requirements and goals at the beginning of most projects. Sometime you have to go further and then you can get more information to do the job. The model does not accommodate this natural uncertainty very well. 1. The Waterfall Model does not tell how to transfer from one stage to another. 2. Practically, there are a few project which always follow the sequential steps that the model proposes.
3. Developing a system using the Waterfall Model does not yield a working version

of the system until late in the process. The Code-And-Fix Model

1. Team falls in it automatically when they dont want to use something else.

2. Starts with a rough idea, dose some simple design and then proceeds into a long repeating cycle of coding, testing and fixing bugs. And finally product is released. 3. Least overhead for planning and documenting, results can be shown immediately. The Big-Bang Model

1. Very little planning, scheduling and formal development process. 2. Maximum time for developing the software and writing the code. 3. There is one starting point but release date is flexible.

Topic 2 DS. Sometimes we cant make it sure that a software can be completely tested. What can be the reasons? Ans - The number of possible inputs is very large. The number of possible outputs is very large. The number of paths through the software is very large. The software specification is subjective. You might say that a bug is in the eye of the beholder. AS. Taking two numbers as Inputs for additions give examples when it can be accurate results and when it can be more prcised? Ans the more result is same as actual output that will be accurate, if that is not as required in actual output then it will be prcised output. The following situations can occur with output 1. It can be neither accurate nor prcised 2. It can be prcised, but not accurate 3. It is accurate, but not prcised 4. It can be accurate and prcised DL. Define the terms verification, validation, quality, reliability, testing and quality assurance in general and what relevance they can have with software project? Ans Verification is the process confirming that something software meets its specification. Validation is the process confirming that it meets the user's requirements. Quality and Reliability

Quality is "a degree of excellence" or "superiority in kind." If a software product is of high quality, it will meet the customer's needs. The customer will feel that the product is excellent and superior to his other choices. Reliability is just one aspect of quality. To ensure that a program is of high quality and is reliable, a software tester must both verify and validate throughout the product development process. Testing and Quality Assurance (QA)

The goal of a software tester is to find bugs, find them as early as possible, and make sure they get fixed. A software quality assurance person's main responsibility is to create and enforce standards and methods to improve the development process and to prevent bugs from ever occurring.

DA. Being a software tester design a test case to implement white box and black box testing for a software meant for result generation of student? Ans

In black-box testing - The tester only knows what the software is supposed to do he can't look in the box to see how it operates. If he types in a certain input, he gets a certain output. He doesn't know how or why it happens, just that it does. Black-box testing is sometimes referred to as functional testing or behavioral testing. In white-box testing (sometimes called clear-box testing), the software tester has access to the program's code and can examine it for clues to help him with his testing he can see inside the box. The design of test case to be used Test case No. Condition to be tested Test data Expected result Status (p/f)

Topic 3 DS. Define the term static testing in relation to an application software. Give example also? Ans - Static testing refers to testing something that is not running - examining and reviewing it. For example, checking out a used car by kicking the tires and checking the paint. In case of software it can be performing dry run on software without actually running or executing it.

AS. Giving example of software give the differences between static white box and static black box testing? Ans Static Black Box Testing

Static testing is a form of software testing where the software isn't actually used. It is generally not detailed testing, but checks mainly for the sanity of the code, algorithm, or document. It is primarily syntax checking of the code and/or manually reviewing the code or document to find errors. This type of testing can be used by the developer who wrote the code, Code reviews, inspections and walkthroughs are also used. From the black box testing point of view, static testing involves reviewing requirements and specifications Static White Box Testing

In white-box testing (sometimes called clear-box testing), the software tester has access to the program's code and can examine it for clues to help him with his testing he can see inside the box.

DL. Using some examples give the application areas of static white box and static black box testing for a software? Ans Answer must any application with direct access to code and without having access to code.

AL. Design a test cases to implement the static white box, static black box, white box and black box test on software for railway reservation? Ans the answer must be consist of any of test case sample like Test case No. Condition to be tested Test data Expected result Status (p/f)

testcase id

test case name

test case desc

test steps step expecte d actual

test case status

test status (P/F)

test prority

defect severi ty

Topic 4 DS. Define the term dynamic testing in relation to an application software. Give example also? Ans - Dynamic testing (or dynamic analysis) is a term used in software engineering to describe the testing of the dynamic behaviour of code. In dynamic testing the software must actually be compiled and run.

AS. Giving example of software give the differences between Dynamic white box and Dynamic black box testing? Ans

Testing software without having an insight into the details of underlying code is dynamic black-box testing. It's dynamic because the program is running you're using it as a customer would. it's black-box because you're testing it without knowing exactly how it works with blinders on. You're entering inputs, receiving outputs, and checking the results.

Another name commonly used for dynamic black-box testing is behavioral testing because you're testing how the software actually behaves when it's used. To do this effectively requires some definition of what the software does namely, a requirements document or product specification. Testing a running program and since it's white-box, it must be about looking inside the box, examining the code, and watching it as it runs. Using information you gain from seeing what the code does and how it works to determine what to test, what not to test, and how to approach the testing.

DL. Compare application of test to pass and test to fail on software? Give your comment which is to be applied first? Ans- Test to Pass We really assure that the software minimally works. You don't push its capabilities. You don't see what you can do to break it. Applying the simplest and most straightforward test cases. When designing and running your test cases, always run the test-to-pass cases first. Test to Fail Designing and running test cases with the sole purpose of breaking the software is called testing-to-fail or error-forcing.

The test to pass is to be applied first as we will get the work behavior of software.

DA. Give application areas of Data testing, Boundary conditions, Sub-Boundary conditions, State testing and Equivalence partitioning on a software meant for book shop? Ans - Data testing While performing software testing on the data, we are checking that information the user inputs, results that he receives, and any interim results internal to the software are handled correctly.

Boundary conditions

If software can operate on the edge of its capabilities, it will almost certainly operate well under normal conditions. Boundary conditions are special because programming, by its nature, is prone to problems at its edges.

Sub-Boundary conditions

Some boundaries are internal to the software aren't necessarily apparent to an end user but still need to be checked by the software tester. These are known as sub-boundary conditions or internal boundary conditions.

State Testing

The other side of software testing is to verify the program's logic flow through its various states. A software state is a condition or mode that the software is currently in.

Topic 5 DS. Name the compatibilities provided by Microsoft office 2007? Ans It provides backward and forward compatibilities. DA. Discuss the issues which can be tested while applying compatibility test on an application? Ans

It must support forward and backward compatibility. MULTIPLE VERSION TESTING Data Sharing Compatibility.

DL. Define the term data sharing compatibility, there are how many methods for implementing it, while testing this issue which areas have to be covered? Ans The more application share data with other applications the maximum powerful will be the application. Program that supports and adheres to published standards and allow users to easily transfer data to and from other software is a great compatible product.

The most familiar means of transferring data from one program to another is saving and loading disk files. Adherence's to low low-level standards for the disk and file formats makes this sharing possible more flexible.

Methods for data sharing compatibility test File save and file load = We save our data to a floppy disk (or some other means of magnetic or optical storage) and then carry it over to another computer running different software and load it in. The data format of the files needs to meet standards for it to be compatible on both computers. File export and file import = The means that many programs use to be compatible with older versions of themselves and with other programs. Cut, copy, and paste = The most familiar methods for sharing data among programs without transferring the data to a disk. The transfer happens in memory through an intermediate program called the Clipboard.

Issues to be tested While performing compatibility test, we need to make sure that its data can be properly copied in and out of the Clipboard to other programs. The Clipboard is designed to hold several different data types. Common ones in Windows are text, pictures, and sounds. DDE (pronounced D-D-E), COM (for Component Object Model), and OLE (pronounced oh-lay) are the methods in Windows of transferring data between two applications. DDE stands for Dynamic Data Exchange and OLE stands for Object Linking and Embedding. Other platforms support similar methods

Topic 6 DS. What are the differences between user interface provided by MS-Dos and Windwos? Ans MS-Dos was Command User Interface based operating system where as windows is fully fledged Graphical user interface based operating system.

AS. If there is any need to test user interface of application for disabled persons. If yes, which type of disabilities are tested and how they are dealt with? Ans A serious topic that falls under the area of usability testing is that of accessibility testing or testing for the disabled. A 1997 government Survey of Income and Program Participation (SIPP) used by the U.S. Census Bureau found that about 53 million people (nearly 20% of the population) in the country had some sort of disability. With our aging population and the penetration of technology into nearly every aspect of our lives, the usability of software becomes more important every day.

Types of disabilities Visual impairments = Color blindness, extreme near and far sightedness, tunnel vision, dim vision, blurry vision, and cataracts are examples of visual limitations. Hearing impairments = Someone may be partially or completely deaf, have problems hearing certain frequencies, or picking a specific sound out of background noise. Such a person may not be able to hear the sounds or voices that accompany an onscreen video, audible help, or system alerts. Motion impairments = Disease or injury can cause a person to lose fine, gross, or total motor control of his hands or arms. It may be difficult or impossible for some people to properly use a keyboard or a mouse. Cognitive and language = Dyslexia and memory problems may make it difficult for someone to use complex user interfaces.

How they are being dealt Developing software with a user interface that can be used by the disabled isn't just a good idea, a guideline, or a standard it's often the law. United States, have applied three laws for this concern. Accessibility Features in Software Windows, Mac OS, Java, and Linux all support accessibility to some degree.

 The software only needs to adhere to the platform's standards for communicating with the keyboard, mouse, sound card, and monitor to be accessibility enabled. Sticky Keys allows the Shift, Ctrl, or Alt keys to stay in effect until the next key is pressed. Filter Keys prevents brief, repeated (accidental) keystrokes from being recognized. ToggleKeys plays tones when the Caps Lock, Scroll Lock, or NumLock keyboard modes are enabled.

DL. Discuss the types of documents which can be associated with a software, Give your comments on the importance of testing documents with an application? Ans
Software components that can be classified as documentation.

Packaging text and graphics = This includes screen shots from the software, lists of features, system requirements, and copyright information. Marketing material, ads, and other inserts = Important tools used to promote the sale of related software, add-on content, service contracts, and so on. Warranty/registration = Customer fills out and sends in to register the software. Can be part of the software, being displayed onscreen for the user to read, acknowledge, and complete online. EULA = Legal document that the customer agrees to that says, among other things, that he won't copy the software nor sue the manufacturer if he's harmed by a bug. Labels and stickers = Appear on the media, on the box, or on the printed material. There may also be serial number stickers and labels that seal the EULA envelope. Installation and setup instructions = Information is printed directly on the discs, but it also can be included on the CD sleeve or as a CD jewel box insert. If it's complex software, there could be an entire installation manual. User's manual = Most software now comes with a small, concise "getting started type manual with the detailed information moved to online format.

 Online help = Online help often gets intertwined with the user's manual, sometimes even replacing it. Online help is indexed and searchable, making it much easier for users to find the information they're looking for. Tutorials, wizards, and CBT (Computer Based Training) = These tools blend programming code and written documentation. A user can ask a question and the software then guides him through the steps to complete the task. Like Microsoft's Office Assistant Samples, examples, and templates = An example of these would be a word processor with forms or samples that a user can simply fill in to quickly create professional-looking results. Error messages = They fall under the category of documentation. Like symptoms and remedies for those problems Importance of testing the documentation Good software documentation contributes to the product's overall quality in three ways It improves usability= All the issues related to a product's usability? Much of that usability is related to the software documentation. It improves reliability = Reliability is how stable and consistent the software is. If the user reads the documentation, uses the software, and gets unexpected results, that's poor reliability. It lowers support costs = Users who are confused or run into unexpected problems will call the company for help, which is expensive. Good documentation can prevent these calls by adequately explaining and leading users through difficult areas. AL. Discuss the factor on which documentation testing depends, while testing the documentation which issues has to be taken care of? Ans Factor on which documentation testing depends If it's non-code, like printed user's manual or the packaging, testing is a static process much like, "Examining the Specification," and "Examining the Code. If the documentation and code are closely tied, such as with a hyperlinked online manual or with a helpful paper clip guy, then it needs dynamic test effort to be applied.

DOCUMENTATION TESTING CHECK LIST

General Areas Audience = Level of audience, not too novice, not too advanced. Terminology = Is the terminology proper for the audience? Are the terms used consistently? Content and subject matter = Are the appropriate topics covered? Are any topics missing?

Correctness Just the facts = If all the information factually and technically correct? Step by step = Read all the text carefully and slowly. Figures and screen captures = Check figures for accuracy and precision. Do they represent the correct image and is the image correct? Samples and examples = Load and use every sample just as a customer would. If it's code, type or copy it in and run it. Samples and examples = Load and use every sample just as a customer would. If it's code, type or copy it in and run it.

Topic 7 DS. When software can be considered as secured and unsecured? Ans A secure product is a product that protects the confidentiality, integrity, and availability of the customers' information, and the integrity and availability of processing resources, under control of the system's owner or administrator. A security vulnerability is a flaw in a product that makes it infeasible even when using the product properly to prevent an attacker from usurping privileges on the user's system, regulating its operation, compromising data on it, or assuming ungranted trust.

AS. What can be various methods for breaching security of software? Mention the motives for which software can be hacked? Ans

The Hacker is One who is proficient at using or programming a computer; a computer buff. One who uses programming skills to gain illegal access to a computer network or file.

Motives for hacker Challenge/Prestige = The simplest and most benign form of hacking is when someone breaks into a system purely for the challenge of the task and the prestige (among his fellow hackers) of succeeding. There's no intent of anything more threatening. Curiosity = The hacker doesn't stop at just gaining access. Once inside, he wants to look around to see what's there. Curiosity is the motive. The hacker will peruse the system looking for something interesting. A software system could have a security vulnerability that allows a hacker to gain access (challenge/prestige) but still be secure enough to prevent the hacker from looking at any of its valuable data. Use/Leverage = This is the level where the hacker does more than just breaking and entering. Here the hacker will actually attempt to use the system for his own purpose. Vandalize = Vandalizing means Defacing, Destruction, and Denial of Service.

DL. Discuss the security threats for which a software need to be protected? Ans it can be program, network, user based threat. Students have to discuss few of them. DA. While the designing an application for a bank, which type of security measures have to applied in the application? Ans The answer must consist of Authentication of user, amount checking in account, types of transaction, final updation of account.

Topic 8 DS. Name few of the features which makes a website more complex?

Ans Customizable layout, customizable content, dynamically changing text, compatibility with different web browsers etc. DA. Give application areas of applying whitebox testig, blackbox testing over a website testing? Ans The answer must be based on the contents which can be tested while applying whitebox, blackbox testing on a website. DL. Discuss the components which can be tested while applying whitebox, blackbox, graybox, configuration and compatibility test of a website? Ans Whitebox testing Dynamic content. Database driven web pages Server performance and loading Security

Configuration and compatibility test Hardware platform Browser plug in Browser options Text size Video resolution and color depth Modem depth

Black box testing Text Hyperlinks Graphics Forms

AL. Discuss the types of test which needs to be applied for a website meant for a bank and a website for bookshop?

Ans The answer must be based on application of various types of website testing on these two types.