Monday, September 16, 2013
What are the differences between inter-network routing and intra-network routing?
Posted by
Sunflower
at
9/16/2013 11:03:00 PM
0
comments
Labels: Connection, Data, device, efficient, Information, Infrastructure, Internetwork Routing, Intranetwork Routing, Network, Networking, Organization, Packets, Protocols, Resources, Router, Routing, Switch, System
![]() | Subscribe by Email |
|
Tuesday, May 7, 2013
What is meant by Time sharing system?
- SDS 940
- PDP – 10
- IBM 360
Posted by
Sunflower
at
5/07/2013 09:30:00 PM
0
comments
Labels: Application, computers, Cost, Data, Design, efficient, Expensive, Interactive, Interface, Multi-programming, Multi-tasking, Multiple, Organization, program, Resources, System, Technology, Time sharing System, Users
![]() | Subscribe by Email |
|
Wednesday, April 24, 2013
What is multi-tasking, multi-programming and multi-threading?
What is Multitasking?
What is Multi-Programming?
What is Multi-threading?
Posted by
Sunflower
at
4/24/2013 07:30:00 PM
0
comments
Labels: CPU, Data, Devices, efficient, Memory, Multi-programming, Multi-tasking, Multi-threading, Performance, peripherals, Process, program, Resources, System, Tasks, Threads, Time
![]() | Subscribe by Email |
|
Tuesday, July 3, 2012
What are the main attributes of test automation?
What does Test Automation do?
- Data driven testing
- Regression testing
- Performance testing and so
on.
Attributes of Test Automation
Posted by
Sunflower
at
7/03/2012 08:45:00 PM
0
comments
Labels: Accurate, Attributes, Automate, Characteristics, Development, efficient, Execution, Flexible, Manual, Methodology, Outcomes, Reliable, Repeatable, Software, Speed, Test automation, Test cases, Testing, Tests, Users
![]() | Subscribe by Email |
|
Wednesday, May 2, 2012
TestLink is a Free, open source test case management tool? - Explain?
Concepts of Open Source Models
What purposes are facilitated by Test Link?
Features of TestLink
Benefits of TestLink
Posted by
Sunflower
at
5/02/2012 11:30:00 PM
0
comments
Labels: Benefits, Concepts, Cost, efficient, Features, Integration, Models, Open Source Test Case Management Tool, Peers, Principle, Purpose, Requirements, Software testing, STLC, Test cases, Test Scripts, TestLink, Time, Tool
![]() | Subscribe by Email |
|
Friday, March 16, 2012
What are three main purposes of software testing?
It is a world wide established fact that the software testing has proved all the way very effective in improving the satisfaction of the clients and customers by delivering them a software product that is quite free of defects, errors and bugs.
Only the stable, error free and reliable software systems and applications are accepted in to the business. There is no place for the unstable and buggy software systems.
WHAT HAPPENS IF TESTING IS NOT DONE PROPERLY?
- There is a substantial increase in the chances of the failure of a software system or application if it is not tested or tested only up to a small extent.
- This in turn increases the rates of wastage of time as well as one’s precious efforts.
- The rework and rewrites and their maintenance cost the organization so much and also annoys the customers and clients.
- If a software system fails, it only gives an indication towards the inadequacy of the efficiency of the system and a lack of testing.
- The failure of the software systems or applications can cost too much in certain cases where very sensitive and critical matters are dependent on the working of the software.
- Software testing has been scientifically defined as a process that deals with the verification and validation of the software system or application.
- It ensures whether or not the system meets all the requirements specifications that have been used all along its development cycle to guide its designing and makes sure that the software system or application is working as expected by the makers.
THREE MAIN PURPOSES OF SOFTWARE TESTING
Three main purposes of the software testing have been laid down as mentioned below:
1. Verification
This purpose deals with the verification of the development process of the software system or application and ensures that the software is being developed or built in the right way.
2. Validation
This is all about making sure that the right software artefact is being produced.
3. Defect finding verification
This is for the purpose of ensuring that the software system or application that is being built, meets the technical specifications and requirements stated for it by the customer or the clients. It also checks out for the variation of the defect range between the actual outcome and the expected outcome.
BENEFITS OF SOFTWARE TESTING
- Software testing has very well taken up the responsibility for ensuring that the software system or application meets the business requirements as specified for it and thus whether or not works as expected.
- The compatibility of the software system or application with a range of different platforms is also evaluated and the performance rating is given.
- Whether the software system or application should be released or not, is determined on the basis of the results of the software testing.
- Software testing has a whole lot of benefits, the greatest ones being the saving of the time and efforts which are indeed very priceless commodities.
- Defects, bugs and errors if detected earlier eat up less time and money and reduce development time and also if the application or system is kept error free in the beginning itself, then less problems will be faced in the future development phases.
Software failures as mentioned above can give rise to life threatening issues to the:
- People (for example, control system failure resulting in a plane crash, life support system failure in hospitals causing deaths)
- Environment (for example, a software failure causes the harmful radiations and chemicals to be released in to the environment and thus affecting the whole eco system)
- Companies (for example, some times the software might do the bill incorrectly due to some discrepancy in it causing the company a great money loss) and so on.
Posted by
Sunflower
at
3/16/2012 04:36:00 PM
0
comments
Labels: Application, Benefits, Bugs, Clients, Compatibility, Customers, Defects, efficient, Effort, Errors, Failure, Purpose, Requirements, Software Systems, Software testing, Time, Validation, Verification
![]() | Subscribe by Email |
|
Saturday, January 21, 2012
What is the difference between automated testing and manual testing?
Automated scripted testing and manual scripted are two most common and popular ways of carrying out the scripted testing. Scripted testing is performed by a set of test scripts which can be defined as a set of instructions that are to be performed on the software system or application under the test to test a particular functionality as required.
Automated testing is mostly used.
- In automated testing the test cases are executed automatically and there is no need of human intervention.
- Non- requirement of human intervention is the best advantage of automated testing.
- It can be easily repeated and is faster than manual testing.
- It is very useful when it is required to run the same tests over and over again.
- It is performed as a part of regression testing.
- The main drawback of automated testing is that the automated tests are poorly written and they may break down or crash during the execution.
- They only test what has been programmed into them.
- They only ensure that old bugs do not reappear and don’t prove to be a good methodology to find out new bugs and errors.
In contrast to automated testing the manual scripted testing is the oldest and most rigorous form of software and application testing.
- In manual testing the test cases are reviewed by the whole testing team before putting them in to execution.
- These test cases are created at two levels.
- The first level is basic functionality level and the second one is the scenario level.
- Apart from reviewing of test cases, the designing is also done by the whole software development team.
- Manual scripted testing is considered to be a waste of resources by most of the testers.
- According to some testers the scripted manual testing inhibits the mind of the tester to use their creativity and also this testing requires heavy documentation as well as considerable amount of resources to create them.
- They often get out dated since the changes in the system are inevitable.
- Though being so criticized manual scripted testing is used by many organizations.
- The test cases are made repeatable and easy enough for a tester to perform testing with minimum supervision.
- Manual scripted testing is used in contracts where contractual agreement states that written requirements and specifications of the software must be met.
- Scripted test cases are useful where the tests are used for the benchmarking purpose and have to be executed in the same way, every time.
- The testers should have a strong knowledge of the software system or application since in manual scripted testing; the test cases are created beforehand.
- The primary sources of information to the testers are functional design specifications, requirements documents etc and so on.
- To make the testing more effective, the testers are free to use supplementary sources of information to increase their knowledge of the software system or application by rigorous discussions with the development team.
- Manual scripted testing is used in situations or programs where a waterfall methodology along with the V-Model has been implemented.
- Apart from waterfall and v model methodology, this approach can also be used for projects where requirements and specifications are frozen and likelihood of modifications in those requirements and specifications is very less and this is also suitable for the situations where safety and regulatory situations demand proof of testing.
- Generally, this manual testing approach is considered old but, it is quite relevant in this current era of market driven applications.
The best methodology is mixing manual testing and automated testing together and using it for exploratory testing.
Posted by
Sunflower
at
1/21/2012 03:33:00 PM
0
comments
Labels: Application, Automated Testing, Bugs, Defects, Design, Differences, Drawbacks, efficient, Errors, Execute, Faster, Manual Testing, Methods, Software testing, Test cases, Test Scripts, Testers
![]() | Subscribe by Email |
|
Friday, January 20, 2012
What do we mean by automated test data generation?
First let us clear up what is meant by Test automation? Test automation can be defined as the use of software system, program or application to carry out the following tasks:
- control the process of execution of tests
- to compare the actual outcomes with the predicted outcomes
- to set up the preconditions for test cases
- to keep test control and
- to implement the function of reporting tests.
WHY TEST AUTOMATION IS USED?
Test automation as the term itself suggests involves automation of a manual testing process which is already in progress.
- It is used for automating manual testing processes which use a formal approach for testing.
- Although manual testing also holds good for finding defects in a software program or application, it is a very laborious and time consuming testing process and also it is not so effective in finding certain kinds of defects.
- To overcome these drawbacks of manual testing, automated Testing is employed.
- It involves a process of writing a computer program or software to carry out testing that would otherwise requires to be done manually.
- Once the tests have been automated, they can be run, easily, quickly and repeatedly.
- All these plus points make the automated testing a very cost effective method for software applications.
- Even minor bugs or discrepancies can cause the program to break or crash over the lifetime of the application.
Two general approaches to test automation have been discovered so far:
- Code driven testing
Elements like classes, public interfaces, libraries and modules are tested under code driven testing with a assorted data arguments in order to validate the results for their correctness.
- Graphical user interface testing
As the name suggests this testing approach creates user interface events such as mouse clicks, key strokes etc. the changes that occur in the user interface are observed and that observable behavior is validated for its correctness.
TOOLS FOR TEST AUTOMATION
Unlike tools required for manual testing, test automation tools are quite expensive, and are usually employed or used in combination with the tools of manual testing.
- Nevertheless, the tools can be cost-effective in the longer term if used repeatedly in regression testing.
WAYS TO GENERATE DATA
Now coming to the automated test data generation, there are several ways for generating data and test cases.
- One of the ways to generate test cases automatically is model- based testing and it generates test cases through use of a model of the system.
- Data is the most important thing needed to execute any test.
- Generating data again and again for repeating tests becomes a time consuming task.
- You need to design the test data again and again to execute your test cases.
- You need to design the test data at the current instant if you are running tests in an exploratory manner.
- Generating test data on your own takes a lot of your valuable time.
- Automated tests need a large amount of distinct test data.
- Another alternative can be copying and pasting data for running tests if the production data is available.
- However, this does not prove to be a very good approach.
- But, nowadays several tools have been developed which can be used for automated test data generation.
So the good thing is that you need not waste your precious time generating test data by hand. These tools help you by creating large quantities of test data based on the conditions and constraints specified by you.
Automated test data generation has got the below mentioned benefits:
- Fast data generation
- Accurate data
- Uses built in algorithms
- Creates both valid and invalid test data
- Data is exportable
Posted by
Sunflower
at
1/20/2012 02:04:00 PM
0
comments
Labels: Automated, Automated Test Generation, Bugs, Control, Data, Defects, efficient, Errors, Generate, Manual Testing, Outcomes, Test automation, Test cases, Test Execution, Testing tools, Tests
![]() | Subscribe by Email |
|