Different ways to be a happy employee
When an employee is under-productive he or she will be the first target when companies look for opportunities to give pink slips.Being happy is always in your hands. A happy employee is more productive and gives more than an unhappy employee. So let's look at some ways to up the happiness factor. 1. Plan your week on Sunday night 2. Undertake activities that you are passionate about even though it might not be in your job profile 3. Do not indulge in the blame game 4. Communicate more often in person 5. Know what is happening at your workplace Attend all meetings that are addressed by the CEO to your immediate manager to know what is going to happen around you. It could be the company's growth plan or your department's next big project. Jack Welch mentions in his book Winning "every employee, not just the senior people, should know how a company is doing." You will also get an extra edge if you are in a position to answer queries raised by your peers or juniors. This is not just for the good reasons, but bad reasons as well. You do not want to be the last employee to know if your company is laying off employees (in the worst case, if you are the one who is on that list). 6. Participate in organisation-level activities 7. Have a hobby that keeps you busy and happy 8. Take up a sport 9. Keep yourself away from office politics Politics is everywhere and the office is no exception. Playing politics might be beneficial but only for the short term. So the best thing to do is play fair. 10. Wish and smile 11. Volunteer for some activity "The value of a man resides in what he gives and not in what he is capable of receiving." by Albert Einstein Do at least one activity without expecting anything in return. There is no set frequency for this. This could be once in a day or once in a week or thrice in a week. It could be as simple as making tea at the office for your colleague, helping a colleague who is working in another department by using your skills, dropping your colleague at his door step in your car, going to your manager or colleague to ask if there is any help you can extend, contributing to technical or knowledge management communities in your organisation etc. This article has been picked from www.rediffmail.com (http://in.rediff.com/getahead/2008/oct/29career.htm)
Look at your work calendar and plan your week on Sunday night or Monday morning. This would include important meetings, deliverables, a brief summary of things that are pending from last week and any tasks to be achieved during the week. Though this might look like a time management tip, at the end of the week, on Friday night when you re-visit what you have achieved over the last five days, the satisfaction is immense.
Start an initiative that you would love to do irrespective of whether it is required for you to do or not.
If something goes wrong do not blame others blindly. If you commit a mistake, do not hesitate to accept it. As Gauthama Buddha said, there are three things we can't hide for long: the sun, earth and the truth. Accepting your mistake gracefully will only make you look like a true professional and also give you the satisfaction of not cheating.
Utilise all the opportunities where you can speak to an individual in person rather than e-mail or phone. But be aware of the other person's time and availability. Listening to a positive answer from a person will give you more happiness than if it is done over the phone or via e-mail.
Will this make a person happy? Truly, yes! Imagine a cricket team that doesn't know how many runs to score to win a match? More than losing the game, the player will never be interested or motivated to play well.
This could be as simple as spending one weekend for a corporate social responsibility activity or attending a recruitment drive to help your HR team or arranging a technical/sports event at the organisational level. Most of these events will be successful as people do come on their own to contribute.
Many people say their hobby is watching TV or listening to music or reading the newspaper. These aren't hobbies, they are just ways of passing the time. Some hobbies are evergreen and will keep you evergreen as well: dancing, painting, writing short stories, poems, blogs and sharing your experiences.
While choosing a sport make sure that there is physical activity. There is the danger of becoming addicted to sports where there is less physical activity (like computer games, chess, cards etc). Physical activity keeps a person healthy and happy. If you pick up one sport well, you can represent your organisation in corporate sports event too.
Politics, as a practice, whatever its profession, has always been the systematic organization of hatreds. -- Henry Brooks Adams
More often than not, there are fair chances that the other person will smile back. This could be your security guard at the gate, your receptionist, your office boy, your CEO or your manager -- never forget to wish them and smile.
Posted byPrashanthNaik at 2:33 AM 0 comments
Labels: Article, Corporate, Employee, Entrepreneurs, Happy, Job
Who is telling tulu doesn't have script???
Tulu language is one of the five Dravidian languages of South India (Pancha- Bhasha, others are Tamil, Telugu, Kannada and Malayalam). The four major languages spoken today are dominantly spoken in their respective states (Tamilnadu, Andhra Pradesh, Karnataka and Kerala), whereas Tulu is spoken in a small niche, mainly in coastal Karnataka and Northern Karala (Kasaragod district). About 2.5 million people speak Tulu and call it their mother tongue. Tulu nadu is a region where many languages are spoken. While Kannada is the official state language, different ethnic communities in Tulu Nadu speak different languages. Tulu, derived from proto-Dravidian is the predominant language spoken by Hindus of various castes and by the Jains of Tulu Nadu. Konkanasthas and Catholics speak two variants of Konkani. Muslims speak a language of their own that is derived from Tulu as well as Malayalam.
For More Info Please Visit the Site: http://www.boloji.com/places/0020.htm
Posted byPrashanthNaik at 6:12 PM 0 comments
Labels: Fun, Language, Society, Tulu
Dell Recruiting 2007 & 2008 Freshers
Hi all please forward your 2007 & 2008 passed out resumes to below
mentioned emails.
Dell is planning to recruit more than 1000 new graduates for their new
web mail development, in various locations. This is Great Opportunity
for Fresh Graduates to work with Dell
Qualification:
ØBE / B. Tech. - 2008 pass outs (Computer Science, Information
Technology, Electronics and all Electronics, Electronics &
Telecommunication, Electronics & Instrumentation etc.) Ø MCA / M.Sc.
-2007/08: Only Computer Science & Information Technology Branch Ø
B.Sc./BCA - 2007/08: Computer Science, Information Technology,
Physics, Mathematics, Chemistry, Statistics, Electronics
Eligibility Criteria:
ØGraduation 60% and Above
Ø 10th/12th: 60% and above
Ø No Gap in education
Ø Willingness to work in shifts, any platform & any location Ø No
Supplementary (un-cleared) subjects as on date Ø Good Communication
Skills
If you have resumes meeting the above criteria you can send it to:
Bangalore: offcampus.bangalore @dellmail. com
Chennai: offcampus.chennai@ dellmail. com
Hyderabad : offcampus.hyderabad @dellmail. com
It will be great if you could forward this message to any of your
acquaintances who are keen in participating in this test. Please note
that as per our regular hiring norms, the students clearing this test
with go thru the various levels of Interviews before being made the
FTE offers.
Posted byPrashanthNaik at 6:38 PM 0 comments
Labels: Dell, Freshers, Job, Recruit
Cool Meanings of some of the Words!!!!
Cigarette:
A pinch of tobacco rolled in paper with fire at one end & a fool at the other.
***********
Love affairs :
Something like cricket where one-day internationals are more popular than a five-day test.
***********
Marriage :
It's an agreement in which a man loses his bachelor degree and a woman gains her master
***********
Divorce:
Future tense of marriage
***********
Lecture:
An art of transferring information from the notes of the lecturer to the notes of the students without passing through the minds of either.
***********
Conference:
The confusion of one man multiplied by the number present.
***********
Compromise :
The art of dividing a cake in such a way that everybody believes he got the biggest piece.
***********
Tears:
The hydraulic force by which masculine will power is defeated by feminine waterpower.. .
***********
Dictionary:
A place where divorce comes before marriage.
***********
Conference Room:
A place where everybody talks, nobody listens & everybody disagrees later on.
***********
Ecstasy:
A feeling when you feel you are going to feel a feeling you have never felt before.
***********
Classic:
A book which people praise, but do not read.
***********
Smile:
A curve that can set a lot of things straight.
***********
Office :
A place where you can relax after your strenuous home life.
***********
Yawn:
The only time some married men ever get to open their mouth.
***********
Etc:
A sign to make others believe that you know more than you actually do.
***********
Committee:
Individuals who can do nothing individually and sit to decide that nothing can be done together.
***********
Experience :
The name men give to their mistakes.
***********
Atom Bomb:
An invention to end all inventions.
***********
Philosopher :
A fool who torments himself during life, to be spoken of when dead.
***********
Diplomat:
A person who tells you to go to hell in such a way that you actually look forward to the trip.
***********
Opportunist:
A person who starts taking bath if he accidentally falls into a river.
***********
Optimist :
A person who while falling from Eiffel Tower says in midway See I am not injured yet.
***********
Pessimist:
A person who says that O is the last letter in ZERO, Instead of the first letter in word OPPORTUNITY
***********
Miser:
A person who lives poor so that he can die rich.
***********
Father:
A banker provided by nature.
***********
Criminal:
A guy no different from the rest... Except that he got caught.
***********
Boss:
Someone who is early when you are late and late when you are early.
***********
Politician:
One who shakes your hand before elections and your Confidence after.
***********
Doctor:
A person who kills your ills by pills, and kills you with his bills .
***********
Posted byPrashanthNaik at 1:30 AM 0 comments
Creative Ads...Watch This...
Posted byPrashanthNaik at 1:30 AM 0 comments
Labels: Entertainment, Fun, Job, Joke, Video
BEST JOKE COMPETITION
A Chinese walks into a bar in America late one night and he saw Steven Spielberg.
As he was a great fan of his movies,he rushes over to him, and asks for his autograph.
Instead, Spielberg gives him a slap and says,
"You Chinese people bombed our Pearl Habour, get outta here."
The astonished Chinese man replied,
"It was not the Chinese who bombed your Pearl Harbour,
it was the Japanese".
"Chinese, Japanese, Taiwanese, you're all the same," replied Spielberg.
In return, the Chinese gives Spielberg a slap and says,
"You sank the Titanic, my forefathers were on that ship."
Shocked, Spielberg replies, "It was the iceberg that sank the ship, not me."
The Chinese replies,
"Iceberg, Spielberg, Carlsberg, you're all the same."
Posted byPrashanthNaik at 1:30 AM 0 comments
Labels: Entertainment, Fun, Humour, Joke
What is Love???
A group of 4 to 8 year-olds was asked, "What does love mean?"
The answers they gave were broader and deeper than anyone could have
imagined.
--"When my grandmother got arthritis, she couldn't bend
over and paint her toe nails anymore. So my grandfather does it for her all
the time, even when his hands got arthritis too. That's love." (Rebecca -
age 8)
--"When someone loves you, the way they say your name is
different. You know that your name is safe in their mouth." (Billy - age 4)
--"Love is when you go out to eat and give somebody most of
your French fries without making them give you any of theirs." (Chrissy -
age 6 )
--"Love is what makes you smile when you're tired." ( Terri - age 4 )
--"Love is when my mommy makes coffee for my daddy and she
takes a sip before giving it to him, to make sure the taste is OK." (Danny
- age 7)
--"Love is when you tell a guy you like his shirt, then he
wears it everyday" (Tina - age 7)
--"Love is like a little old woman and a little old man who
are still friends even after they know each other so well." (Tommy - age 6
)
--"During my piano recital, I was on a stage and scared. I
looked at all the people watching me and saw my daddy waving and smiling!
He was the only one doing that. I wasn't scared anymore. That's love"
(Cindy -age 8)
--"My mommy loves me more than anybody. You don't see anyone
else kissing me to sleep at night." (Clare - Age 5)
--"Love is when mommy gives daddy the best piece of
chicken." (Elaine - age 5)
--"Love is when your puppy licks your face even after you
left him alone all day." (Mary Ann - age 4 )
Smile and spread some love today.........
Posted byPrashanthNaik at 1:00 AM 0 comments
Labels: Kids, Life, Love, Society
How you can bring back the joy in your job
Here's how you can bring back the joy in your job
Feeling trapped in your job? Well, in that case, stop fretting, for here are few ways to help you fall back in love with work.
Psychologist Dr Timothy Sharp, who calls himself ''Mr Happy'' and teaches people how to get more enjoyment out of their work, has offered the tips to make you feel good while working.
"Not everyone will be 100 per cent happy 100 per cent of the time," News.com.au quoted Dr Sharp, as saying.
"You have to be realistic, but you can be more satisfied. Being 60 per cent satisfied with your job is better than being 30 per cent satisfied,” the expert added.
According to the expert, be grateful and focus on the good things about your workplace, your role or your co-workers.
"Many of us have a tendency to focus on the bad things," says Sharp.
"However there are very few organisations that are totally terrible and for every problem or colleague you don’t like there are almost certainly good things and nice people,” the expert added.
If something is making you unhappy, try to fix it.
"Don't complain, do something," says Sharp.
Most employees sit back and criticise, but assume management will step in.
"Even if it's turning up with the right mindset, even if it's doing something nice for the other person, or finding a way to bring fun into the workplace," says Sharp.
According to the expert, stop getting bogged down on details and mind numbing daily minutiae. Instead, focus on how your job fits into the big picture.
Also, remind yourself of the purpose of your job – this will make the work more meaningful.
People often spend a lot of time doing tasks we think are essential, but are really optional. Don't quit your job, just quit doing the stuff you hate, and see if anyone notices, says the expert.
This Article has been copied from samcha.com (http://publication.samachar.com/pub_article.php?id=2735217&navname=General&moreurl=http://publication.samachar.com/sify/websites/general/sifynews.php&homeurl=http://general.samachar.com&nextids=2736301|2735740|2735215|2735216|2735217&nextIndex=0)
Posted byPrashanthNaik at 5:22 AM 0 comments
Software Testing Glossary
Acceptance Testing: Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.
Accessibility Testing: Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).
Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.
Agile Testing: Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.
Application Binary Interface (ABI): A specification defining requirements for portability of applications in binary forms across defferent system platforms and environments.
Application Programming Interface (API): A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.
Automated Software Quality (ASQ): The use of software tools, such as automated testing tools, to improve software quality.
- Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing.
- The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
Backus-Naur Form: A metalanguage used to formally describe the syntax of a language.
Basic Block: A sequence of one or more consecutive, executable statements containing no branches.
Basis Path Testing: A white box test case design technique that uses the algorithmic flow of the program to design tests.
Basis Set: The set of tests derived using basis path testing.
Baseline: The point at which some deliverable produced during the software engineering process is put under formal change control.
Benchmark Testing:Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration.
Beta Testing: Testing of a re release of a software product conducted by customers.
Binary Portability Testing: Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.
Black Box Testing: Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.
Bottom Up Testing:An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.
Boundary Testing: Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).
Boundary Value Analysis: In boundary value analysis, test cases are generated using the extremes of the input domaini, e.g. maximum, minimum, just inside/outside boundaries, typical values, and error values. BVA is similar to Equivalence Partitioning but focuses on "corner cases".
Branch Testing: Testing in which all branches in the program source code are tested at least once.
Breadth Testing: A test suite that exercises the full functionality of a product but does not test features in detail.
Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner.
CAST: Computer Aided Software Testing.
Capture/Replay Tool: A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.
CMM: The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.
Cause Effect Graph: A graphical representation of inputs and the associated outputs effects which can be used to design test cases.
Code Complete: Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.
Code Coverage: An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.
Code Inspection: A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.
Code Walkthrough: A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.
Coding: The generation of source code.
Compatibility Testing: Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.
Component: A minimal software item for which a separate specification is available.
Component Testing: See Unit Testing.
Concurrency Testing:Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
Conformance Testing: The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.
Context Driven Testing: The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.
Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Cyclomatic Complexity: A measure of the logical complexity of an algorithm, used in white-box testing.
Data Dictionary: A database that contains definitions of all data items defined during analysis.
Data Flow Diagram: A modeling notation that represents a functional decomposition of a system.
Data Driven Testing: Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.
Debugging: The process of finding and removing the causes of software failures.
Defect: Nonconformance to requirements or functional / program specification
Dependency Testing: Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.
Depth Testing: A test that exercises a feature of a product in full detail.
Dynamic Testing: Testing software through executing it. See also Static Testing.
Emulator: A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.
Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.
End-to-End testing: Testing 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.
Equivalence Class: A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.
Equivalence Partitioning: A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test.
Functional Decomposition: A technique used during planning, analysis and design; creates a functional hierarchy for the software.
Functional Specification: A document that describes in detail the characteristics of the product with regard to its intended features.
Functional Testing: See also Black Box Testing.
- Testing the features and operational behavior of a product to ensure they correspond to its specifications.
- Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.
Glass Box Testing: A synonym for White Box Testing.
Gorilla Testing: Testing one particular module,functionality heavily.
Gray Box Testing: A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.
High Order Tests: Black-box tests conducted once the software has been integrated.
Independent Test Group (ITG): A group of people whose primary responsibility is software testing,
Inspection:A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).
Integration Testing: Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.
Installation Testing:Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.
Load Testing: See Performance Testing.
Localization Testing: This term refers to making software specifically designed for a specific locality.
Loop Testing: A white box testing technique that exercises program loops.
Metric:A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.
Monkey Testing: Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.
Mutation Testing: Testing done on the application where bugs are purposely added to it.
Negative Testing: Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.
N+1 Testing:A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+1. The cycles are typically repeated until the solution reaches a steady state and there are no errors. See also Regression Testing.
Path Testing: Testing in which all paths in the program source code are tested at least once.Performance Testing: Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".
Positive Testing: Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.
Quality Assurance: All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.
Quality Audit:A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.
Quality Circle:A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.
Quality Control: The operational techniques and the activities used to fulfill and verify requirements of quality.
Quality Management: That aspect of the overall management function that determines and implements the quality policy.
Quality Policy: The overall intentions and direction of an organization as regards quality as formally expressed by top management.
Quality System: The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.
Race Condition: A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.
Ramp Testing: Continuously raising an input signal until the system breaks down.
Recovery Testing:Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.
Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.
Release Candidate:A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).
Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.
Scalability Testing: Performance testing focused on ensuring the application under test gracefully handles increases in work load.
Security Testing:Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.
Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
Soak Testing:Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.
Software Requirements Specification:A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/
Software Testing: A set of activities conducted with the intent of finding errors in software.
Static Analysis: Analysis of a program carried out without executing the program.
Static Analyzer: A tool that carries out static analysis.
Static Testing: Analysis of a program carried out without executing the program.
Storage Testing:Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.
Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.
Structural Testing: Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.
System Testing: Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.
Testability:The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.
- The process of exercising software to verify that it satisfies specified requirements and to detect errors.
- The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829).
- The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component.
Test Automation: See Automated Testing.
Test Bed: An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.
- Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.
- A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
Test Driven Development:Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.
Test Driver: A program or test tool used to execute a tests. Also known as a Test Harness.
Test Environment:The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.
Test First Design:Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.
Test Harness: A program or test tool used to execute a tests. Also known as a Test Driver.
Test Plan: A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.
Test Procedure: A document providing detailed instructions for the execution of one or more test cases.
Test Scenario: Definition of a set of test cases or test scripts and the sequence in which they are to be executed.
Test Script: Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.
Test Specification: A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.
Test Suite: A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.
Test Tools: Computer programs used in the testing of a system, a component of the system, or its documentation.
Thread Testing: A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.
Top Down Testing:An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.
Total Quality Management: A company commitment to develop a process that achieves high quality product and customer satisfaction.
Traceability Matrix: A document showing the relationship between Test Requirements and Test Cases.
Usability Testing: Testing the ease with which users can learn and use a product.
Use Case:The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.
User Acceptance Testing: A formal product evaluation performed by a customer as a condition of purchase.
Unit Testing: Testing of individual software components.
Validation:The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.
Verification:The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.
Volume Testing:Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner.
Walkthrough: A review of requirements, designs or code characterized by the author of the material under review guiding the progression of the review.
White Box Testing: Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing. Contrast with Black Box Testing.
Workflow Testing: Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.
Posted byPrashanthNaik at 8:28 PM 1 comments
Labels: Article, Glossary, QA, Quality Assurance, Software Testing, Testing
Posts
