Software Engineering 165. What is Software Testing? Ans: Software testing can be stated as the process of validating and verifying that a software program/application/product: Meets the business and technical requirements that guided its design and development; works as expected; and can be implemented with the same characteristics.
166. What is a bug? Ans: Bug is found before the application goes into hands of the customer. (realese). Generally found by the testers.
167. What is a defect? Ans: Defect is found after the application goes into the hands of customer(realese). Generally found by the users of application. 168. What is functional testing? Ans: Functional testing refers to activities that verify a specific action or function of the code. These are usually found in the code requirements documentation, although some development methodologies work from use cases or user stories. Functional tests tend to answer the question of "can the user do this" or "does this particular feature work".
169. What is non-functional non-functional testing? Ans: Non-functional testing refers to aspects of the software that may not be related to a specific function or user action, such as scalability or security. Non-functional testing tends to answer such questions as "how many people can log in at once".
170. What is scalability? Ans: Scalability is a desirable property of a system, a network, or a process, which indicates its ability to either handle growing amounts of work in a graceful manner or to be enlarged.
171. What is security? Ans: Security means the collective processes and mechanisms by which sensitive and v aluable information and services are protected from publication, tampering or collapse by unauthorized activities or untrustworthy individuals and unplanned events respectively.
172. What is non-functional non-functional testing? Ans: Non-functional testing refers to aspects of the software that may not be related to a specific function or user action, such as scalability or security. Non-functional testing tends to answer such questions as "how many people can log in at once".
173. What is static testing? Ans: Reviews, walkthroughs, or inspections are considered as static testing. 174. What is dynamic testing? Ans: Actually executing programmed code with a given set of test cases is referred to as Dynamic testing.
175. Can static testing be omitted? Ans: Static testing can be (and unfortunately in practice often is) omitted. 176. When can the dynamic testing be started? Ans: Dynamic testing takes place when the program itself is used for the first time (which is generally considered the beginning of the testing stage). Dynamic testing may begin before the program is 100% complete in order to test particular sections of code (modules or discrete functions). Typical techniques for this are either using stubs/drivers or execution from a debugger environment.
177. What is software verification? Ans: Verification: Have we built the software right? (i.e., does it match the specification). 178. What is software validation? Ans: Validation: Have we built the r ight software? (i.e., is this what the customer wants). 179. What is White Box Testing? Ans: White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these.
1
180. What is Black Box testing? Ans: Black-box testing is a method of software testing that tests the functionality of an application as opposed to its internal structures or workings . Specific knowledge of the a pplication's code/internal structure and programming knowledge in general is not required.
181. What is Grey Box Testing? Ans: Grey box testing involves having knowledge of internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level.
182. What is Unit-Testing? Ans: Unit testing is a method by which individual units of source code are tested to determine if they are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure.
183. What is Integration Testing? Ans: Integration testing (sometimes called Integration and Testing, abbreviated "I&T") is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests.
184.What is System Testing? Ans: System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.
185.What is System Integration Testing? Ans: System integration testing takes multiple integrated systems that have passed system testing as input and tests their required interactions.
186. What is Regression Testing? Ans: Regression testing is any type of software testing that seeks to uncover software errors after changes to the program (e.g. bugfixes or new functionality) have been made, by retesting the program. The intent of regression testing is to assure that a change, such as a bugfix, did not introduce new bugs.
187. What is Acceptance Testing? Ans: acceptance testing is black-box testing performed on a system (for example: a piece of software, lots of manufactured mechanical parts, or batches of chemical products) prior to its delivery.
188. What is Alpha Testing? Ans: Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing.
189. What is beta testing? Ans: Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users
190. What is Performance testing? Ans: Performance testing is executed to determine how fast a system or sub-system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage.
191. What is Load Testing? Ans:. Load testing is primarily concerned with testing that can continue to operate under a specific load, whether that is large quantities of data or a large number of users. This is generally referred to as software scalability.
192. What is Stability testing? Ans: Stability testing checks to see if the software can continuously function well in or above an acceptable period. This activity of non-functional software testing is often referred to as load (or endurance) testing.
2
193. What is Security testing? Ans: Security testing is essential for software that processes confidential data to prevent system intrusion by hackers.
194. What is CMMI? Ans: Capability Maturity Model Integration (CMMI) is a process improvement approach that helps organizations improves their performance. CMMI can be used to guide process improvement across a project, a division, or an entire organization.
195. What is Waterfall model? Ans: The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing a nd Maintenance.
196. What is Software Development Process? Ans: A software development process , also known as a software development lifecycle , is a structure imposed on the development of a software product. Similar terms include software life cycle and software process.
197. What is planning? Ans: The important task in creating a software product is extracting the requirements or requirements analysis. Customers typically have an abstract idea of what they want as an end r esult, but not what software should do. Incomplete, ambiguous, or even contradictory requirements are recognized by skilled and experienced software engineers at this point.
198. What is Implementation? Ans: Implementation is the part of the process where software engineers actually program the code for the project
199. When does the deployment start? Ans: Deployment starts after the code is appropriately tested, is approved for release and sold or otherwise distributed into a production environment.
200. What is spiral model? Ans: The spiral model is a software development process combining elements of both design and prototyping-in-stages, prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts.
3
