- For
loop
- While
loop
- Do
while loop
Saturday, May 19, 2012
Explain simple loops in detail?
Posted by
Sunflower
at
5/19/2012 01:15:00 PM
0
comments
Labels: Application, Code, Conditions, Coverage, Defects, Developer, Do while Loop, Errors, For Loop, Loop testing, Loops, Object Oriented, Programmer, Programming, Simple Loops, Software System, Statements, Tasks, While Loop
|
| Subscribe by Email |
|
Thursday, May 17, 2012
Explain nested loops in detail?
Why Loops are Important?
What are Nested Loops?
Posted by
Sunflower
at
5/17/2012 11:53:00 PM
0
comments
Labels: Conditions, Control, Developer, Entity, Execute, Inner, Iterations, Loop testing, Loops, Nest, Nested loops, Objects, OOP, Outer, Parent Loop, Procedures, Programmer, Statements, Tests, Types
|
| Subscribe by Email |
|
Thursday, May 3, 2012
What are the requirements in a test driven development?
Posted by
Sunflower
at
5/03/2012 11:48:00 PM
0
comments
Labels: Approach, Automation, Code, Defects, Developers, Development, Errors, Methodology, Programmer, Re-factoring, Requirements, TDD, Techniques, Test Cycles, Test Driven Development, Tests, Top-down Approach, Unit tests
|
| Subscribe by Email |
|
Saturday, April 14, 2012
What are the advantages and limitations of a mock object?
Mock objects are nowadays quite popular with the testers. The mock objects are now being used widely for conducting unit testing and also in many software development processes like the test driven development.
- The mock objects are known for their mimicking behaviour of the other non mock or original objects for which they have been created.
- The mock objects are used under the context of the object oriented programming.
- They are nothing but the fake objects that are simulated in a way as to mimic the behavior of the real objects in a way that is properly controlled and defined.
- The behavior of most of the non mock or real objects is tested against the behavior of a mock object.
- You can compare the mock object with a crash test dummy that is used by the car designers to the impact of the vehicle on the human body.
Reasons for Use
Few of them have been mentioned below:
1. The real object provides non deterministic result like current temperature and time.
2. The real object has the states that cannot be easily recreated or reproduced such as a network error.
3. The real object is quite slow such as a data base that needs initializing before the commencing of the test.
4. The real object does not exist currently.
5. The real object tends to change its behaviour.
6. The real object is to include the information for the testing purposes.
Advantages of Mock Object
- One of the characteristic of the mock objects is that they possess the same interface as that of the real objects that they mimic.
- With such an arrangement the client stays unaware of whether he is using the real object or the mock object.
- With the use of mock objects it becomes easy for the programmer to specify which and all methods will be invoked and in what order and it can also be specified which parameters are to be passed to the mock objects.
- All this is done by using the mock object frame works.
- The mock objects can even mimic the behaviour of the complex objects, for example the network socket.
- The use of mock objects can help the programmer in various ways.
- The programmer can determine whether the object that is under test responds well to the variety of situations it is put in works properly or not.
Limitations of Mock Object
- Use of mock objects can lead to close coupling of the several unit tests similar to that in the actual implementation of the code that is under testing.
- If a programmer is using the mock object frame work, the order of and number of times the mock methods are to be invoked on a mock object can be specified.
- If the code is subsequently refactored, it may fail even though the contract of the previous implementation is followed in the method.
- The unit tests are known to test only the external behaviour of the mock methods rather than testing its internal implementation.
- Therefore, maintenance needed for the tests increases if there is an overuse of the mock objects.
- Mock objects need to model the real objects perfectly well which becomes difficult if the real object has not been written yet.
Posted by
Sunflower
at
4/14/2012 12:19:00 PM
0
comments
Labels: Advantages, Behavior, Characteristics, Code, Complex, Dummy, Limitations, Methods, Mock objects, Objects, OOP, Programmer, Re-factoring, Simulate, Software testing, Testers, Tests, Unit Testing
|
| Subscribe by Email |
|
Saturday, January 7, 2012
What are different aspects of exploratory testing?
Exploratory testing is a usual approach to software testing and can be defined as a test designing, test execution and simultaneously learning process.
It was named by Cem Kaner in 1983. "He stated exploratory testing as a kind of software testing that is emphasized and focused up on the responsibility and the personal freedom of the software tester to optimize the quality and effectiveness of his /her work continually by taking in to consideration mutually supportive activities like test designing, test related learning, test result interpretation and test execution".
These activities run in parallel to each other.
- Exploratory testing basically heeds to exploiting the creativity of the tester or the programmer.
- During the testing of the software, the tester comes across various new things to learn together with experiencing them.
- The tester or the developer with his /her creativity can generate new and better test cases to run.
- Exploratory can be thought of as a black box testing methodology or technique instead of thinking of it as an approach to testing that can be used for any type of testing methodology and also at any phase of development of the software system or application.
According to some misconceptions, the testing technique or the object is considered to be the key here but, it is not so.
- In actual, the key is the cognitive engagement of the software tester and his /her responsibility of managing time.
- The effectiveness of the exploratory testing depends basically on how it is performed.
- Exploratory testing should always be performed by skilled testers or developers.
- Exploratory testing can also be thought of as an intellectual activity.
- Exploratory testing is all about discovering how the software system or application actually works and how it handles both the easy and difficult cases.
The effectiveness or the quality of the testing is largely dependent on the skills for developing test cases by the tester.
- It also depends on his/ her ability to find defects in the software code.
- We can say that the quality of the testing is directly proportional to the knowledge of the tester about the software product and different test methods.
- The more he/ she know about the software system under test and testing methodologies, the better will be the exploratory testing.
- While carrying out the exploratory testing, the expectations should be kept open.
- Only some results can be expected or predicted but not all.
- The tester is responsible for configuring, operating, observing and evaluating the product itself and its behavior, investigating the result and reporting information. - If we see practically the actual testing is a combination of both scripted testing and exploratory testing but, depending on the context of the testing the tendency is towards either one.
- Exploratory testing is more about thinking how the testing should be done more than a testing technique.
The documentation part of the exploratory testing includes:
- Documentation of all the test cases used.
- Documentation of the bugs.
Exploratory testers use tools like:
- Screen capture
- Video tools
These tools are used to generate situations of interest or as a record of the exploratory session. For exploratory testing less before hand testing is needed. Bugs are discovered quickly and the approach tends to be more intellectual. Deductive reasoning based on the results of the previous tests can also be used in the exploratory testing. This leads to increased bug detection when used properly. The main disadvantage is that the tests can’t be reviewed before hand.
Posted by
Sunflower
at
1/07/2012 10:02:00 AM
0
comments
Labels: Approach, Black box testing, Design, Developer, Effective, Exploration, Exploratory testing, Programmer, Quality, Software testing, Test cases, Test Execution, Tests
|
| Subscribe by Email |
|
Saturday, April 2, 2011
Users involved in Development Process and End-Users who are involved indirectly in the development process...
GUIDELINES FOR END-USERS
The higher the level of the manager, the less he or she is likely to care about computer technology.
The goals and priorities of management may be in conflict with those of the supervisory and operational users.
Management may not provide resources, funding or time that the users feel is necessary to build an effective system.
The end users involved indirectly in the development process are auditors, standard bearers, and quality assurance group.
The objective of this group is to ensure that the system is developed in accordance with various standard set:
- standards by other departments.
- standards by government regulatory agencies.
- accounting standards.
- they do not get involved until the end of project.
- they provide the necessary notation and format of documentation.
Development Team
It is responsible in building the software that will supporta domain specific system.
System Analyst
Responsibility is understanding the system. Within this system, he identifies customer wants, and documents and prioritizes requirements.
System Designer
Responsibility is to transform a technology free architectural design that will providethe framework within which the programmers can work.
Programmers
Responsibility of the programmers is to write the codes of the software using a particular programming language based on system design.
Testers
Work product should be reviewed for faults and errors. It ensures thatwork products meet requirements and standards defined.
Posted by
Sunflower
at
4/02/2011 05:14:00 PM
0
comments
Labels: Development, End-users, Goals, Guidelines, Indirectly, Programmer, Quality, Resources, Standards, System Analyst, System Designer, Testers, Users
|
| Subscribe by Email |
|
Sunday, October 3, 2010
Verification Strategies - Overview to Walkthroughs.
Walkthrough is a static analysis technique in which a designer or programmer leads members of the development team and other interested parties through a segment of documentation or code, and the participants ask questions and make comments about possible errors, violation of development standards, and other problems.
the objectives of Walkthrough can be summarized as follows:
- Detect the errors early.
- Train and exchange technical information among project teams which participate in the walkthrough.
- Increase the quality of the project, thereby improving morale of the team members.
The participants in walkthroughs assume the role of a walk-through leader, recorder, author and a team member.
To consider a review as a systematic walk-through, a team of at least two members shall be assembled. Roles may be shared among the tam members. the walk-through leader or the author may serve as the recorder. The walk-through leader may be the author.
Individuals holding management positions over any member of the walk-through team shall not participate in the walk-through.
Input to the walk-through includes:
- A statement of objectives for the walk-through.
- The software product being examined.
- Standards that are in effect for the acquisition, supply, development, operation and/or maintenance of the software product.
- Any regulations, standards, guidelines, plans, and procedures against which the software product is to be inspected.
- Anomaly categories.
The walk-through shall be considered complete when
- The entire software product has been examined.
- Recommendations and required actions have been recorded.
- The walk-through output has been completed.
Posted by
Sunflower
at
10/03/2010 11:58:00 AM
0
comments
Labels: Analysis, Code, Inputs, Programmer, Software, Software testing, Strategies, Strategy, Technical Reviews, Verification, Walkthroughs
|
| Subscribe by Email |
|