Blog: Search Engine Optimization

Blog: Search Engine Optimization I found

“Excellence is not a singular act, but a habit. You are what you repeatedly do.”

Testing Continue....

Device Testing

Device Testing Services help identify defects across the device development lifecycle. By testing devices in a simulated environment, we pinpoint defects that would otherwise be noticed, only in a live environment.

Our services cover a range of enterprise mobility products - mobile phones, mobile handhelds, RFID devices and wireless scanners and printers; addressing testing across firmware, host software, operating systems, applications and interfaces, forming a part of the device.

Device Testing Services cover:

• System Testing
• Certification Testing
• OS Development Testing
• Integration Testing
• OS Porting Validation
• 802.11 Testing (Wi-Fi Testing)
• Device Management
• Data Collection

The services are accelerated by our proprietary automation environment - an integrated framework that enables us to track and test multiple devices (across platforms like Windows, Unix, Symbian) using a single view. The framework eliminates the need for device set-up each time a scenario is executed. By eliminating device set-up, (the most time consuming activity) the framework helps reduce effort by 50% to 60%.

Lifecycle Testing Services

Lifecycle Testing Services support you with rigorous checks across the testing lifecycle from requirement validation to test execution. Our services start from the initial stages of the software development lifecycle - allowing for early detection of defects leading to average cost reductions of 40% or more.
Lifecycle Testing Services cover:

• Functional Testing: Validation of functional requirements of your applications
• Regression Testing: Retesting your applications post modification on account of functionality change or defect correction
• Integration Testing: Testing of interfaces and integrated components/modules of applications
• System Testing: Testing of completely integrated applications to ensure they meet your specifications

Our Lifecycle Testing Services are specifically tailored to work in the waterfall, iterative, and agile models of software development. They are built on standards adhering to ITIL and conform to ISO 9126 Guidelines. The services also utilize a proprietary model (an enhanced form of the industry standard V model) enabling closer mapping of testing to development activities. Governed by well-defined processes, metrics, service level and operating level agreements; our Lifecycle Testing Services extend testing of your applications beyond the software development stages to maintenance and production support.

The Competition era.. Survival in Career ....

Many people find interesting careers, many find their career interesting, still some search careers where their interests lie and there are those who pursue their interests at the cost of their normal career path".

In this era of competition the most important thing a person should look in whatever career he is in by choice or chance is the survival of his interest i.e. food, money, social service, or hegemony.........although the degree may vary from case to case and time to time.

Now in this era of competition the career makes little difference but the real motivator is your interest...... i.e money, food, house, living, hegemony- power, service to society... etc..

So career is not important as you could be in it by choice or chance but try to search and survive your interest by using your intelligence, is the smartest thing to do in this competition era.

As all careers provide ample opportunity for survival of all kinds of interests...

Example:- 

1)  Now lets take a situation where a person is in the IAS which gives him scope to enjoy power and glamour, serve the people, earn money, enjoy the admiration of others for commendable performance and sometimes become a scapegoat for some fault of the bosses.

2) A businessman who runs a corporate house or a small shop where he is able to earn profits(money), serve the people by providing goods and services which are otherwise unavailable easily and handyly, enjoy monopoly(Power), fat customer base(glamour), awards and recognition and ire of the authorities through raids and compelled to bribe to save harassment.

3) A doctor who practises to earn money, serve the people, admiration for curing people, power and glamour(fat clientele), etc.

4) A Lawyer who advocates for people to earn money, name and fame for being able to get prompt relief from Courts, power and glamour(huge number of cases) and contacts and also serve the people by giving legal aid to poor and deprived.

5) An academician who teaches for money, name and fame, also serve the poor but meritorious............

Same for actors, models, engineers............ scientists.......

the list goes on................and on…….

Thank You...

Introducing a new Google Docs

It’s been almost 4 years since we launched Google Docs. Back then people were excited about being able to access their documents from anywhere and edit those documents collaboratively online. But as Google documents became more mainstream, we started to hear more and more of you asking for features like margins, tabs, and floating images that were only available in desktop word processors. To make these features possible, we started working on a complete rewrite of Google documents over a year ago.

This week we released a preview of that new document editor for anyone who wants to try it out. This version supports a brand new ruler, alignment features, per-paragraph line spacing and more.


You’ll also notice a huge improvement in the import quality when uploading and importing documents from desktop word processors into

Google Docs.

But we didn’t want to just bring you traditional word processing features. We also wanted to extend collaboration capabilities in documents. We added a sidebar that lets you see who else is editing at the same time, and, if you click the sidebar, you can chat with collaborators right next to the document. And when other editors type, you can now see their edits as they happen character-by-character.

Software Testing & Types...

Software Testing Types

Black box testing - Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.

White box testing - This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing - Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.

Incremental integration testing - Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.

Integration testing - Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing - This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.

System testing - Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.

End-to-end testing - Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Sanity testing - Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.

Regression testing - Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types.

Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application.

Load testing - Its a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.

Stress testing - System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load.


Performance testing - Term often used interchangeably with ’stress’ and ‘load’ testing. To check whether system meets performance requirements. Used different performance and load tools to do this.

Usability testing - User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing.

Install/uninstall testing - Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment.

Recovery testing - Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Security testing - Can system be penetrated by any hacking way. Testing how well the system protects against unauthorized internal or external access. Checked if system, database is safe from external attacks.

Compatibility testing - Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.

Comparison testing - Comparison of product strengths and weaknesses with previous versions or other similar products.

Alpha testing - In house virtual user environment can be created for this type of testing. Testing is done at the end of development. Still minor design changes may be made as a result of such testing.

Beta testing - Testing typically done by end-users or others. Final testing before releasing application for commercial purpose.

More details visit this link:- http://www.chillarege.com/authwork/TestingBestPractice.pdf


What is a Test Case?

A test case is a set of conditions or variables and inputs that are developed for a particular goal or objective to be achieved on a certain application to judge its capabilities or features.
It might take more than one test case to determine the true functionality of the application being tested. Every requirement or objective to be achieved needs at least one test case. Some software development methodologies like Rational Unified Process (RUP) recommend creating at least two test cases for each requirement or objective; one for performing testing through positive perspective and the other through negative perspective.

Test Case Structure

A formal written test case comprises of three parts -

1. Information
   Information consists of general information about the test case. Information incorporates Identifier, test case creator, test case version, name of the test case, purpose or brief description and test case dependencies.
2. Activity
   Activity consists of the actual test case activities. Activity contains information about the test case environment, activities to be done at test case initialization, activities to be done after test case is performed, step by step actions to be done while testing and the input data that is to be supplied for testing.
   
3. Results
   Results are outcomes of a performed test case. Results data consist of information about expected results and the actual results.

Designing Test Cases

Test cases should be designed and written by someone who understands the function or technology being tested. A test case should include the following information -

• Purpose of the test
• Software requirements and Hardware requirements (if any)
• Specific setup or configuration requirements
• Description on how to perform the test(s)
• Expected results or success criteria for the test

Designing test cases can be time consuming in a testing schedule, but they are worth giving time because they can really avoid unnecessary retesting or debugging or at least lower it. Organizations can take the test cases approach in their own context and according to their own perspectives. Some follow a general step way approach while others may opt for a more detailed and complex approach. It is very important for you to decide between the two extremes and judge on what would work the best for you. Designing proper test cases is very vital for your software testing plans as a lot of bugs, ambiguities, inconsistencies and slip ups can be recovered in time as also it helps in saving your time on continuous debugging and re-testing test cases.