Micheal Jackson

Michael Joseph Jackson (August 29, 1958 – June 25, 2009[2]) was an American recording artist and entertainer.

In the early 1980s, he became a dominant figure in popular music and the first African-American entertainer to amass a strong crossover following on MTV. The popularity of his music videos airing on MTV, such as "Beat It", "Billie Jean" and Thriller—credited for transforming the music video into an art form and a promotional tool—helped bring the relatively new channel to fame. Videos such as "Black or White" and "Scream" made Jackson an enduring staple on MTV in the 1990s. With stage performances and music videos, Jackson popularized a number of physically complicated dance techniques, such as the robot and the moonwalk. His distinctive musical sound and vocal style influenced many hip hop, pop and contemporary R&B artists.

The seventh child of the Jackson family, he debuted on the professional music scene at the age of 11 as a member of The Jackson 5 and began a solo career in 1971 while still a member of the group. Referred to as the "King of Pop" in subsequent years, four of his solo studio albums are among the world's best-selling records: Off the Wall (1979), Bad (1987), Dangerous (1991) and HIStory (1995), while his 1982 Thriller is the world's best-selling record of all time.

One of the few artists to have been inducted into the Rock and Roll Hall of Fame twice, his other achievements include multiple Guinness World Records—including one for "Most Successful Entertainer of All Time"—13 Grammy Awards, 13 number one singles in his solo career—more than any other male artist in the Hot 100 era. Jackson's highly publicized personal life, coupled with his successful career, made him a part of popular culture for almost four decades. Michael Jackson died of cardiac arrest on June 25, 2009, aged 50.

Starving Makes It Fat

Starving Makes It Fat

"Anger as soon as fed is dead - 'Tis starving makes it fat." - Emily Dickinson


Matthew stepped onto the scales. Trish, the coordinator, read out his weight. He'd lost three pounds, bringing him to his target weight. He got the loudest cheer of the night. He smiled modestly. Under cover of writing down his achievement on his Weight Warriors pocket card, he looked the women over.

He'd already had four of them: Angie, Claire, Jane and Sonya. He could have had Trish too, but he never did coordinators. They were inclined to be vengeful and more intelligent than their clients. If he got Sharon in the sack tonight, he wouldn't have to come back next week. He glanced at her. She blushed. He looked around the room. Angie simpered, Claire grinned, Jane looked down, and Sonya refused to catch his eye. A good haul. Of course, they were oblivious to their collective nature, each thought herself the only recipient of his attentions - these women didn't boast about sex. He could never have got away with it if they did.

Sometimes, when he looked at women, he saw them composed of food. Claire, the fast food queen, with vanilla milkshake flesh-tones, and hair the stringy, bleached texture of reconstituted French fries. Jane: cocoa-colored skin and candy pink lips. Sonya - a dairy maid with dimpled hands like cheese fingers, and acres of creamy curves.

He timed his exit so Sharon was shoulder to shoulder with him. More accurately, her shoulder - mottled but solid, like prime beef sausage - brushed his elbow. She was nearly as wide as she was tall, and her blonde moustache showed how inefficient facial bleach could be. Matthew wished she waxed. Smooth skin was much easier to transmute in his imagination, especially with his eyes closed.

'May I offer you a lift home?' He spoke gently, both to avoid startling her if she was skittish, and to ensure the other women didn't overhear.

Tonight Sharon would be his J-Lo. He hoped she wasn't a grunter. It was hard to imagine Jennifer's sultry tones and lavish love-gifts of Rolex and iMac, if the woman beneath him was honking and squealing. He hoped she wasn't a virgin either. He hated the tedium of it, and deflowering was always followed by much emotional guff. He began to hum under his breath, 'I should be so lucky, lucky, lucky, lucky, I should be so lucky in love.' Sharon giggled.

<>
Five hours later, tired and smelling of the magnolia shampoo that was all he could find in Sharon's bathroom, he escaped. It was easy to get away.

'Sharon, I'm so sorry, I don't know what came over me. You know I'm getting married soon? It's why I'm at Weight Warriors - to lose weight before the wedding. I just couldn't resist you, but please ... can we pretend it was just a wonderful dream? I love my fiancèe and although she could never match up to you physically... well, she's blind, and so ....' No fat woman ever impeded his departure once he mentioned the sightless bride-to-be.

He sat in the car and dictated a long message to Liz's mailbox. Now it was over to her. Tonight's Fat Fighters was his last meeting in Stroud. He would be home with her in three hours. They'd have two weeks together before it was her turn to come up here. He swung the Volvo around Stroud's rain-slick streets. Overweight women appreciated a big safe car. The seduction started there, in a seat that didn't cramp them, riding a suspension that didn't groan under their bulk, with space to relax and appreciate how Matthew attended to them. The car was his introduction to their bedrooms - and it worked every time.

Lazily he calculated the takings. Twenty women in five weeks. Monday night: Weight Warriors - six women. Tuesday night: Lighter Ladies - six women. Wednesday: Yoga for Weight loss - only three women bedded there, a disappointing score. Thursday's Fat Fighters - five women, all of them coy and respectable. His quota was met; twenty bed-post notches meant he could go home to Liz and relax for a while. He grinned to imagine how much money they would make from these lovelorn fatties, then scowled, remembering the strenuous evening with Sharon. Catching sight of his forehead in the rear view mirror, he relaxed it immediately. Women fell for his boyish, tousle-haired sensuality. He couldn't afford frown lines.

For a while now he'd been wondering how they would make their money when he couldn't do this any more. Nobody stayed young and charming forever. He found it ever more wearisome to superimpose imaginary women on the chunky bodies he seduced. He'd never failed yet. But one day, morbid obesity would defeat him - the tickle of a walrus moustache would not translate in his mind to the silky tresses of a visionary inamorata and he would wilt ... forever.

<>
Liz said not to worry. She said she was thinking about what scam to operate when he ceased to conquer weight-challenged women. He should feel reassured, but he didn't. Suppose Liz decided he was expendable?

He pushed the thought back into the mental crevice from which it had crawled and resolved to think only about money. Money was his aphrodisiac: if all else failed he could imagine the women - Buddha-like - were composed of soft buttery gold. Infinitely attractive. Then the bigger they were, the better.

*

'Good morning, may I speak to Miss Claire Henderson, please?'

'Speaking.'

The voice was bright, conveying feminine bubbliness. There was nothing to suggest the speaker was six stone overweight. Liz pondered that, as she continued the conversation. Very few women had fat voices.

'Miss Henderson, are you able to speak privately, or would there be a better time to call you?'

'Why, what's this about?' Most of the bubbles had popped now, replaced by flat urgency. Liz always wondered how many of them expected what was coming next. What proportion of the large unloved had a premonition of certain punishment for their one horizontal transgression? Suppose she just said, 'Two weeks ago you had sex with my Matt. You must have known he didn't want you for your looks. Now he wants payment for services rendered and I'm ringing on his behalf to collect.' How many would pay up? But that would be the lazy approach. Dear Matt had worked hard, now it was her turn.

'Miss Henderson, I'm afraid it's not good news. Mr. Matthew Helme has asked me to contact you on his behalf. Are you alone?'

'Yes. Yes I am, what's wrong?' Now the voice was leaden - old, and at least as heavy as its owner.

'Possibly nothing. I do not wish to alarm you unduly, however ...' Liz allowed the pause to grow, opening a crack in the universe through which the woman's worst fears could crawl. '... I am sorry to say Mr. Helme has a communicable disease.' Another pause. Sometimes the women rushed to fill it, sometimes they were mute. Neither response reliably predicted their future conduct. Some garrulous ones baulked at Liz's fees and refused her appointments, while silent ones could cave in swiftly, handing over cash for three or four 'repeat treatments'.

<>
'He is deeply ashamed. He has paid for you to have a private consultation with me to establish whether he has transmitted any infection to you. This consultation will be completely confidential and avoid the need for you to visit your doctor or a clinic for sexual diseases.'

Liz used 'clinic for sexual diseases' to shock the women into submission. Miss Henderson was no exception. She accepted the first appointment offered to her. Liz hung up before the woman could bid for reassurance. Time for a reward: she hit the media player button on her laptop and the rich sound of Josè Carreras singing Nessun Dorma filled the room. She loved Carreras - he had a voice bigger than himself, unlike Pavarotti whose voice was smaller than the man.

The Regency office in which she sat was a sweet gem of architecture. Mellow brick and paned windows wrapped her in the comforting illusion of old money. It was on a short lease, of course. Six weeks. The scam always started with the short lease. She flicked through the spreadsheet, checking the future office rentals.

After Stroud, it was Taunton. Matthew - dear boy - would have bedded all the lardy ladies he could manage, and Liz would spend a fortnight dispensing placebo treatments at £500 a pop from an office in a barn conversion. Then Telford, a rather austere but impressive office there, and then they'd be off to Spain. Matthew would need to restore his tan and Liz liked the Algarve. It gave her a chance to inspect the half a dozen villas which brought in enough genuine income to keep the taxman at bay.

She logged onto the Internet and updated the appointment diary. When Matt got up, he'd be able to see how many of Stroud's largest ladies were already wriggling in the net. Then she checked her e-mail account.

Normally she was good at spotting spam, but this time a message got past her, and she found herself confronted by a hideous image. A pale, huge woman, to whom a robe clung in obscene detail. It molded over lumpy nipples that showed bruise-purple through the white fabric. It clung to vile curves, delineating not just their general form but hugging even the cellulite craters and deep ominous dimpling on the woman's upper arms and thighs. Her legs were spread and between them the seaweed tendrils of pubic hair smeared nightmare undertones on the wet cloth. The woman's expression was blank, her eyes were closed, her skin maggot pale.

<>
Liz stared, transfixed with horror. Her thoughts whirled round the giantess like sparrows caught in a storm. It would be better if the behemoth were naked. The clothing gave spurious dignity to her gargantuan ugliness. It was terrible to think people paid to look at this vileness. Even worse - was this the kind of thing darling Matthew had to deal with? Poor boy, no wonder he was exhausted at the end of a seduction period. Suppose a woman like this rolled on top of him in bed? He'd never get her off.

She shook her head free of the gruesome picture, deleted the e-mail, hit the pause button so Carreras vanished in mid-note, and moved on to the next call. Angie Blake was about to have a nightmare come true.

*

Matthew checked the diary. Liz had surpassed herself. Every woman he had penetrated in Stroud had taken up her offer of a free private consultation with Dr Elizabeth Cavella. He wondered if any would dare refuse the treatment Liz prescribed: three courses of sugar pills discreetly posted on receipt of check.

Today he had to go to the Carvery for lunch. He'd be back on duty soon and he needed to be at least thirty-five pounds overweight for the Taunton diet circuit. The thought of eating made his gorge rise, but he'd force down the garlic bread, roast chicken and New York Cheesecake. He used as much imagination on meals as he did on women. As he ate fried food, he imagined fresh sardines, charred over a fire on a Spanish beach. In his imagination the rich sauces became piquant olives, and the creamy, sugared coffee turned to sharp wine from an Algarve vineyard.

*

Claire Henderson was a nervous eater. Since discovering Matthew might have given her the almighty hellish clap, she'd put on six pounds. That was the first thing she said.

Liz sighed before speaking. Far too many of them were like this. Didn't they understand the severity of their plight?

'If you have contracted syphilis you need not worry about your weight. Before it kills you, the disease will reduce you to a bald-headed stick.'

Henderson, whom Matt had nicknamed The Stroud Sow, had gone a vile shade of dirty white. Her skin was exactly the color of a peeled banana, but much less appetizing.

<>
Liz had a special seat for the women. They must be properly cowed and humiliated to be convinced to hand over money on a regular basis and the seat was a major instrument of their suffering. An old birthing chair, patented in the 1950s, it had levers and cogs to realign her victims. They sat down as fat women, and she turned them into vast mounds of supine blubber. The ultimate refinement of this nastiness was the way the women were reflected back to themselves in the chair's chrome surfaces and levers. She polished it herself and transported it in a van Matthew drove. Few women survived the chair with self-esteem intact.

Once the Stroud Sow was installed, Liz pulled on surgical gloves and resumed her patter. In the back of her head she could hear dear Josè singing 'Some Enchanted Evening'. The Sow might wish it was 'I'm Gonna Wash That Man Right Outa My Hair' but a simple rinse and run wasn't going to work for her - she was about to invest in a high maintenance regime.

'Of course, you're very lucky to have caught me. In a month's time I'm closing my private practice. I shall be running a fascinating research program for a pharmaceutical company - it will take up all my time. I shall support any clients already on my books but I shall not take on any new ones. Now ...'

She poked vaguely at the Sow's nethers with a wooden tongue depressor. Then with great care and ceremony she placed the instrument in a clear bag, labeled it, and stripped off the gloves. Only then did she return the victim to an upright position.

'We should have results within a week, or - if you wish to pay for premium service - I can have the analysis completed by six this evening. Rapid analysis costs seventy pounds for the lab and my courier costs are another hundred, so adding in my time to call you at home tonight ... let's say £200?'

The Sow, weeping, handed over £200. Liz laid out the programme.

'If you should be unfortunate enough to have contracted the disease, you have two choices. You may go to your own doctor and request treatment or ...,' in the long pause, the victim's frightened eyes welled again with salty terror. 'I can prescribe it for you privately, and confidentially.' The Sow's gusty sigh of relief rattled papers on the desk. Liz continued inexorably.

<>
'Some cases clear in twelve weeks, more intransigent ones can require twenty-four or even thirty-six weeks of treatment. Each treatment regime will cost you £500 and is supplied by mail. At the end of a course of treatment I will send you a small kit to use and return, to see if we have succeeded in eradicating the disease. Each kit costs £500.'

Here she paused. The Sow nodded so vigorously several of her chins began random Brownian motion, shivering sideways or galumphing up and down at eccentric angles. Liz frowned and continued.

'Today's consultation has been paid for by Mr. Helme. He wishes me to convey his sincere regret for any distress caused to you. Is there anybody with whom you have had sexual contact since then?

It was a hundred to one against, of course, but every so often one of these behemoths had been inspired by Matt's attentions to trap another man. It was easy to double the income from one appointment by arranging to 'examine' the poor fool. The patient shook her head dolefully. That was no surprise, generally if they were fat, they were also stupid, gullible and naïve. They were scared to consult their own doctors and they had too little life experience to see they were being gulled. Normal people, non-fat people, would never fall for this kind of thing. She knew it served them right.

'Good,' said Liz, 'then we don't have to notify anybody else. If you'd like to rearrange your clothing I'll ring the laboratory on my mobile and organize a priority analysis.'

Once outside, Liz inhaled the wet Stroud air greedily. She would give the pig-woman long enough to poke through the papers on her desk. If the Sow was inquisitive, she would be reassured by a letter asking Dr Liz to sit on a Royal Commission, tickets for the Ballet, a receipt for the annual servicing of a Porsche. All forgeries, of course. Liz was good at this. She knew how to cover her back. Even if one of the women had second thoughts, she would remember Dr Cavella had already left general practice to administer research, so there would be no obvious way to check up on her credentials.

She texted a quick message to Matt, reminding him to buy sun-cream for their Algarve trip. She'd missed a call while she was dealing with the Sow, but when she hit the replay button there was nothing but a strange underwater sighing, like whale song. She deleted it.

<>

*

Matt stared dolefully at his chicken. It reminded him of the ruched hips of a big woman with poor circulation. The kind of woman he knew only too well. The cheesecake was pale and flat, like a face with features smoothed by excess weight. Raisins took the place of small eyes, glinting with hurt and shock. For the first time, he failed to finish his dessert. He looked at the cheeseboard: crumbly pale slabs, rich golden mounds, sheeny acres of pallid soft calories, like the spread limbs of victims. He stumbled from the restaurant without leaving a tip.

*

The Sow was sent off, lumbering and fearful. Liz turned to lunch. She lifted a vacuum flask of bouillon from her bag and opened the fridge to extract a box labeled 'medical supplies - refrigerate'. From it she took a bag of pre-packed salad.

As she sipped her soup she studied the hand holding her spoon. Wrist-bones showed elegantly through amber skin that diet and sun kept lean and glowing. Matt called her his 'gazelle'. She'd never been fat, not even plump, even though for a while she'd seen a fat woman in the mirror. She despised people who had blubber, except for sweet Matt of course, when he was bulked up for work. She knew he worried about the drastic weight swings their scheme required, but she'd said dieting had never done her any real harm, which reassured him.

Idly she flicked up the laptop screen, wondering if he'd emailed her. It didn't look like it. But he had installed a new desktop image. Sweet boy. It was of marble or perhaps ice. Something blue-white and chilly anyway. The draperies of a Greek statue? Wind-sculpted snow in the Arctic? She shivered, peered closer. She saw a blue hollow like ... a navel? Diagonal lavender shadows were folds of white fabric drawn across a body. It was a close-up of the disgusting female she'd seen in the earlier e-mail. It must have contained a virus that had invaded her machine. How ghastly.

She slammed the laptop shut. Suddenly she didn't feel hungry. She'd make up a few treatment packs to post out and then have some salad - she didn't want to get too thin. She was in control of her food, of course, it didn't control her anymore. No, she'd learned that lesson. It was understandable that she'd lost her appetite when she saw that grotesque monster, that hideous creature, on her computer screen. Involuntarily her eyes turned to the closed laptop and she shivered again. First work - then lunch. She was managing her diet, she would eat; she wasn't making excuses to skip a meal. She didn't do that anymore.

<>

*

Matthew felt fat. Gravity pulled his six course meal down, and his heart with it. He was soundly, roundly, utterly, depressed. He sat in the car for a while, trying to summon the energy to drive. Big lunches always did this, drained his vitality and left him prostrate with melancholy. Eventually he turned the key, wishing Liz would hurry up and think of another way to make money.

*

Liz looked at the neat pile of padded brown envelopes - discreet and lucrative. She wondered how much longer Matt could play his role. One of the women hadn't followed up on her last test kit by placing a new order ... odd. Liz flicked through the address labels, unwilling to open the laptop and look at the spreadsheet of names there. It was Cynthia Edwards, first course completed two weeks ago, kit used and returned to the PO Box that Liz maintained for just this purpose. Liz had sent out the standard letter, saying Miss Edwards wasn't yet clear of disease but a new treatment would probably 'resolve the situation'. No reply. Which one was Edwards? Oh yes, the Grantham Gargantua. Probably the biggest woman Liz had ever seen. The chair had creaked and groaned under her weight like a foundering ship. Rich too. It would be a shame if she didn't pay for a new course of treatment. Something else about the Edwards woman nagged at her mind. Manacles. That was it. When Matt got to the huge woman's huge house he'd found a pair of handcuffs hanging over the front door. He'd wondered what he was getting into - but it turned out handcuffs were the woman's logo, meant to show how businesses were manacled to the big software companies. Edwards had described herself to Matt as the key that unlocked the cuffs of business. She'd said she hated the way people were tricked into paying for things they didn't need and couldn't use, just because technology moved so fast.

Her phone beeped, probably Matt ringing to tell her what he'd had for lunch. She grabbed it. The same sound again ... eerie sighing, long bubbling ripples like waves on a beach. It must be a fault. She looked at the screen and saw an image forming with portentous slowness. Maybe it was an advertisement. Scuba-diving? Tropical holidays? A beach holiday would be fun - they could skip Spain this time and go to the Caribbean. The image resolved into a pallid arm, pale as marble, monumental, powerful. It flexed and turned as though reaching for something. It dripped water. The huge wet hand plunged out of the screen, fingers spread wide ....

<>
Liz felt her throat constrict. A vast power squeezed her airways shut. Scooting backwards on her wheeled chair, she tried to escape the pressure on her throat. Her hands fluttered around her neck, the bird-like bones no match for the strength that held her. Terror congested her face and panicked her heart into surges and troughs. By degrees she quieted until she sat still, eyes wide and dark, staring at nothing. Her hands fell to her sides, shaping a gentle composition of loss. Even in death she was elegant.

*

Matt felt a bump. Had he run over something? Surely he'd have seen it though. He glanced in the mirror. Nothing in the road. Another bump: harder. Was something trapped beneath the car? A third bump, this time a bang on the grille so violent it made the steering wheel shudder. He thought he saw a vague white shape. He shook his head hard. Too much food had made him slow. He needed to pull over and work out what had happened.

The next blow struck the car from behind, so it jumped forward, kangarooing along the road. In the rear-view mirror Matt could see a huge dent in the boot. He struggled to regain control, but the vehicle jounced along as though pummeled by a giant fist. Fenders crumpled and dints the size of footballs appeared in the bonnet and wings. Within seconds the car had banged off the road and embedded itself in a grove of trees. The airbag inflated and deflated, but Matt was past saving. His neck had snapped and his head hung at an obscene angle, eyes gazing sadly down at his well-nourished frame.

*

'Sarge, you remember that Edwards woman?' W.P.C. Carter asked.

'It'll be a cold day in Hell before I forget her,' said the Desk Sergeant. 'The nastiest suicide I've ever seen. What kind of person handcuffs themselves to the steps at the deep end of their own swimming pool?'

'A rich person?' quipped Carter before returning to her task. 'Anyway, there's a report here that relates to her. Except ...'

'Except what? Don't start what you can't finish, and that includes sentences.' The Sergeant had an aphorism for every situation.

'Well ... you know that vehicular death I queried? The man who'd driven his Volvo into a wood? The reason I asked for details was the trace evidence suggested he'd hit somebody. No victim was found, but Scene of Crime Officer reported it was a person wearing a cotton garment impregnated with chlorine. They found blood, pool-water, and clothing scraps adhering to the car.'

<>
'Did they really?' The Sergeant paused for a second, shook his head, and carried on filling in the Day Book.

'The Edwards woman had cuts on her legs and hands, remember? When we queried them, the pathologist said they were 'inconclusive'. They must have happened post mortem, because they hadn't bled, but there was no evidence of anything in the pool that could have caused them.' W.P.C. Carter wasn't sure where she was going with this conversation. She didn't like anything about it. The Edwards suicide had been a grim business.

They'd been called to the house by a hysterical cleaning woman. Cynthia Edwards had climbed into her pool, cuffed herself to the steps and sat down to die. She'd been a big woman, huge in fact. They'd had to drain the pool to get her out. There was no obvious reason for her to have killed herself. She was rich and solvent, and apparently she'd seemed happy enough recently. Her business as an internet technology consultant was lucrative enough for her purchase a substantial mansion on the outskirts of town. Until around three months ago she'd even been a member of some diet club. She'd recently visited a Harley Street clinic, which refused to disclose anything - except to say the health concern which had brought her to them was a false alarm. She had not been unwell and was not suffering any disease that could have triggered a death-wish.

The immense bulk of her, sitting implacable and pale, under the lucent water had haunted the officers called to the scene. There was something horribly powerful about her, even in death. Something stubborn and forceful projected from her, and surrounded the scene with a tangible, threatening misery. Worse than all of it was Kylie in the background, warbling 'I should be so lucky, lucky, lucky, lucky ....' You had to be irredeemably sick in the head to commit suicide to the sound of Kylie Minogue.

'So - the way I see it, Sarge - we've got a car that drove off the road after hitting somebody wearing cotton clothing and dripping pool water and we've got a dead woman in a pool wearing a torn cotton robe, with lots of cuts and grazes. Doesn't that sound odd to you? The only problem is, we found Cynthia Edwards dead, about ... um ... two days before the crash.'

<>
'W.P.C. Carter, if I were you, I'd keep my wilder imaginations to myself.' The Sergeant moved closer though, to peer over her shoulder at the fax. 'What's that then? That's not a hit and run report.'

'No, it's not. It's a murder. Elizabeth Cavella; the wife of the man who died in the car crash. She was found strangled in her office earlier today. The analysis of the fingerprints on her neck shows the killer was very large and covered in chlorine.'

'Odd,' said the Sergeant.

'Mmm, something else too,' Carter shivered. 'The same music playing at all the scenes: the swimming pool, the car stereo and the laptop - all belting out Kylie Minogue, singing 'I Should Be So Lucky'.


Disclaimer:

None as yet

Software Testing

Software Testing is the process of evaluating the features of software and finding the differences between existing and expected requirements.

In today’s scenario following are some of the major problems:

1. Some of the new development methodologies are developed through trial. Generally, these methods typically don't produce specifications for the tester to test against. So, testers have to find bugs by hit and trial.
2. In today’s tough competition in the market, software development has been driven by entrepreneurial pressures, tight schedule, and constantly evolving product definition. For these reasons, sometimes, it is difficult to convince management that testing is necessary or worthwhile.
3. There are only few trained testers using formal methods and metrics. Most of the software testers out there are just passing through testing on their way to some other career. So, overall the testing effort is not giving the high-quality results that may help demonstrate how the testing effort improves the quality of the product.
4. In the past few years, the quality of standards of software development is improved drastically. It has a profound effect on the quality of the final product. It has also removed the need for extensive low-level testing in these areas, so the demand for white box tester is decreased.

Also, please remember that “A test effort that just finds bugs is not enough.” As a software tester, you must be able to demonstrate that your effort is adding value to the quality of the software. Measure that value in order to demonstrate the value added.

Management would also take interest in knowing that which parts of the software development life cycle is contributing in achieving the product quality. So, add the value as you can.

Effectiveness Vs Efficiency

I've seen that many test engineers are confused with the understanding of Software Test Efficiency and Software Test Effectiveness. Below is the summary of what I understand from Efficiency and Effectiveness.

Software Test Efficiency:

- It is internal in the organization how much resources were consumed how much of these resources were utilized.
- Software Test Efficiency is number of test cases executed divided by unit of time (generally per hour).
- Test Efficiency test the amount of code and testing resources required by a program to perform a particular function.

Here are some formulas to calculate Software Test Efficiency (for different factors):

Test efficiency = (total number of defects found in unit+integration+system) / (total number of defects found in unit+integration+system+User acceptance testing)

Testing Efficiency = (No. of defects Resolved / Total No. of Defects Submitted)* 100

Software Test Effectiveness:Software Test Effectiveness covers three aspects:

- How much the customer's requirements are satisfied by the system.
- How well the customer specifications are achieved by the system.
- How much effort is put in developing the system.

Software Test Effectivness judge the Effect of the test enviornment on the application.

Here are some formulas to calculate Software Test Effectiveness (for different factors):

- Test effectiveness = Number of defects found divided by number of test cases executed.

- Test effectiveness = (total number of defects injected +total number of defect found) / (total number of defect escaped)* 100

- Test Effectiveness = Loss due to problems / Total resources processed by the system

Interview Questions

1. How Does Run time data (Parameterization) is handled in QTP?
A). You can then enter test data into the Data Table, an integrated Spreadsheet with the full functionality of Excel, to manipulate data Sets and create multiple test iterations, without programming, to Expand test case coverage. Data can be typed in or imported from Databases, spreadsheets, or text files.

2) What is keyword view and Expert view in QTP?
A) Quick Test’s Keyword Driven approach, test automation experts Have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.
Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

3) Explain about the Test Fusion Report of QTP?
A) Once a tester has run a test, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team.

4) To which environments does a QTP support?
A) QuickTest Professional supports functional testing of all enterprise environments, including Windows, Web, NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.

5) What is QTP?
A) QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework applications.

6) Explain QTP testing process?
A) The QuickTest testing process consists of 6 main phases:

1. Create your test plan: Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.

2. Recording a session on your application: As you navigate through your application, QuickTest graphically displays each step you perform in the form of a collapsible icon-based test tree . A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.

3. Enhancing your test: Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly.

NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process.

Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data. Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.

4. Debugging your test: If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.

5. Running your test on a new version of your application: You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.

6. Analyzing the test results: You examine the test results to pinpoint defects in your application.

7. Reporting defects: As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

7) Explain the QTP Tool interface.

A) It contains the following key elements:

- Title bar, displaying the name of the currently open test

- Menu bar, displaying menus of QuickTest commands

- File toolbar, containing buttons to assist you in managing tests

- Test toolbar, containing buttons used while creating and maintaining tests

- Debug toolbar, containing buttons used while debugging tests.

Note: The Debug toolbar is not displayed when you open QuickTest for the first time. You can display the Debug toolbar by choosing View > Toolbars > Debug.

- Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow.

Note: The Action toolbar is not displayed when you open QuickTest for the first time. You can display the Action toolbar by choosing View > Toolbars > Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically.

- Test pane, containing two tabs to view your test-the Tree View and the Expert View Test Details pane, containing the Active Screen.

- Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.)

- Status bar, displaying the status of the test.

8) How QTP recognizes Objects in AUT?
A) QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object.

Each line in the QuickTest script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.

9) What are the types of Object Repository’s in QTP?
A) QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test.

The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.

10) Explain the check points in QTP?

A). A checkpoint verifies that expected information is displayed in a Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.

- A page checkpoint checks the characteristics of a Application.
- A text checkpoint checks that a text string is displayed in the appropriate place on a Application.
- An object checkpoint (Standard) checks the values of an object on a Application.
- An image checkpoint checks the values of an image on a Application.
- A table checkpoint checks information within a table on a Application.
- An Accessibility checkpoint checks the web page for Section 508 compliance.
- An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
- Adatabase checkpoint checks the contents of databases accessed by your web site.

11) In how many ways we can add check points to an application using QTP. A) We can add checkpoints while recording the application or we can add after recording is completed using Active screen

(Note : To perform the second one The Active screen must be enabled while recording).

12) How does QTP identifies the object in the application?
A) QTP identifies the object in the application by Logical Name and Class.

13) If an application name is changes frequently i.e while recording it has name "Window1" and then while running its "Windows2" in this case how does QTP handles?

A) QTP handles those situations using "Regular Expressions".

14) What is Parameterizing Tests?
A) When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.

15) What is test object model in QTP?
A) The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that QuickTest can record for it.

A test object is an object that QuickTest creates in the test or component to represent the actual object in your application. QuickTest stores information about the object that will help it identify and check the object during the run session.
A run-time object is the actual object in your Web site or application on which methods are performed during the run session.

When you perform an operation on your application while recording, QuickTest identifies the test object class that represents the object on which you performed the operation and creates the appropriate test object reads the current value of the object's properties in your application and stores the list of properties and values with the test object chooses a unique name for the object, generally using the value of one of its prominent properties records the operation that you performed on the object using the appropriate QuickTest test object method. For example, suppose you click on a Find button with the following HTML source code:



QuickTest identifies the object that you clicked as a WebButton test object. It creates a WebButton object with the name Find, and records the properties and values for the Find WebButton. It also records that you performed a Click method on the WebButton. QuickTest displays your step like this:

Browser("Mercury Interactive").Page("Mercury Interactive").
WebButton("Find").Click

16) What is Object Spy in QTP?
A) Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object's hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.

17) What is the Diff between Image check-point and Bit map Check point?
A) Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map.

Using the bitmap checkpoint, you can check that the map zooms in correctly. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins is loaded). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

18) How many ways we can parameterize data in QTP?

A) There are four types of parameters:

- Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test.

- Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, QuickTest uses a different value from the Data Table.

- Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that QuickTest generates for you based on conditions and options you choose.

- Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have QuickTest generate a random number and insert it in a number of tickets edit field.

19. How do u do batch testing in WR & is it possible to do in QTP, if so explain?
Ans: Batch Testing in WR is nothing but running the whole test set by selecting "Run Testset" from the "Execution Grid". The same is possible with QTP also. If our test cases are automated then by selecting "Run Testset" all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in "Waiting" mode.

20. What does it mean when a check point is in red color? what do u do?
Ans : A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.

21. What do you call the window test director - testlab?
Ans : "Execution Grid". It is place from where we Run all Manual / Automated Scripts.

22. How does u create new test sets in TD?

Ans :

- Login to TD.
- Click on "Test Lab" tab.
- Select the Desired folder under which we need to Create the Test Set. (Test Sets can be grouped as per module.)
- Click on "New Test Set or Ctrl+N" Icon to create a Test Set.

23. How do u do batch testing in WR & is it possible to do in QTP, if so explain?
Ans : You can use Test Batch Runner to run several tests in succession. The results for each test are stored in their default location.

Using Test Batch Runner, you can set up a list of tests and save the list as an .mtb file, so that you can easily run the same batch of tests again, at another time. You can also choose to include or exclude a test in your batch list from running during a batch run.

24. How to Import data from a ".xls" file to Data table during Runtime.

Ans :

- Datatable.Import "...XLS file name..."
- DataTable.ImportSheet(FileName, SheetSource, SheetDest)
- DataTable.ImportSheet "C:\name.xls" ,1 ,"name"

25. How to export data present in Datatable to an ".xls" file?
Ans : DataTable.Export "....xls file name..."

26. Syntax for how to call one script from another and Syntax to call one "Action" in another?
Ans: RunAction ActionName, [IterationMode , IterationRange , Parameters]

Here the actions become reusable on making this call to any Action.
IterationRange String Not always required. Indicates the rows for which action iterations will be performed. Valid only when the IterationMode is rngIterations. Enter the row range (i.e. "1-7"), or enter rngAll to run iterations on all rows.
If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the value of the ExitAction's RetVal argument.

27. How to export QTP results to an ".xls" file?
Ans : By default it creates an "XML" file and displays the results.

28. Differences between QTP & Winrunner?
Ans :

- QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.
- QTP supports ".NET" application Automation not available in Winrunner.
- QTP has "Active Screen" support which captures the application, not available in WR.
- QTP has "Data Table" to store script values , variables which WR does not have.
Using a "point and click" capability you can easily interface with objects, their definitions and create checkpoints after having recorded a script without having to navigate back to that location in your application like you have to with WinRunner. This greatly speeds up script development.

29. How to add a runtime parameter to a datasheet?
Ans: By using LocalSheet property. The following example uses the LocalSheet property to return the local sheet of the run-time Data Table in order to add a parameter (column) to it:

MyParam=DataTable.LocalSheet.AddParameter("Time", "5:45")

30. What scripting language is QTP of?
Ans : VB Script.

31. Analyzing the Checkpoint results
Standard Checkpoint: By adding standard checkpoints to your tests or components, you can compare the expected values of object properties to the object's current values during a run session. If the results do not match, the checkpoint fails.

32. Table and DB Checkpoints: By adding table checkpoints to your tests or components, you can check that a specified value is displayed in a cell in a table on your application. By adding database checkpoints to your tests or components, you can check the contents of databases accessed by your application.

The results displayed for table and database checkpoints are similar. When you run your test or component, QuickTest compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails.

You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object. To add a table checkpoint, you use the Checkpoint Properties dialog box.

Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments.

You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query.

Database checkpoints are supported for all environments supported by QuickTest, by default, as well as for a variety of external add-in environments.

There are two ways to define a database query:

- Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office.
- Manually define an SQL statement.

The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint.

33. Checking Bitmaps:
A.) You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk space.

When you run the test or component, QuickTest compares the object or selected area of the object currently displayed on the Web page or application with the bitmap stored when the test or component was recorded. If there are differences, QuickTest captures a bitmap of the actual object and displays it with the expected bitmap in the details portion of the Test Results window. By comparing the two bitmaps (expected and actual), you can identify the nature of the discrepancy.

For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.

You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins is loaded).

Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

34. Text/Text Area Checkpoint: In the Text/Text Area Checkpoint Properties dialog box, you can specify the text to be checked as well as which text is displayed before and after the checked text. These configuration options are particularly helpful when the text string you want to check appears several times or when it could change in a predictable way during run sessions.

Note: In Windows-based environments, if there is more than one line of text selected, the Checkpoint Summary pane displays [complex value] instead of the selected text string. You can then click Configure to view and manipulate the actual selected text for the checkpoint.

QTP automatically displays the Checked Text in red and the text before and after the Checked Text in blue. For text area checkpoints, only the text string captured from the defined area is displayed (Text Before and Text After are not displayed).

To designate parts of the captured string as Checked Text and other parts as Text Before and Text After, click the Configure button. The Configure Text Selection dialog box opens.

35. Checking XML: XML (Extensible Markup Language) is a meta-markup language for text documents that is endorsed as a standard by the W3C. XML makes the complex data structures portable between different computer environments/operating systems and programming languages, facilitating the sharing of data.

XML files contain text with simple tags that describe the data within an XML document. These tags describe the data content, but not the presentation of the data. Applications that display an XML document or file use either Cascading Style Sheets (CSS) or XSL Formatting Objects (XSL-FO) to present the data.

You can verify the data content of XML files by inserting XML checkpoints. A few common uses of XML checkpoints are described below:

- An XML file can be a static data file that is accessed in order to retrieve commonly used data for which a quick response time is needed—for example, country names, zip codes, or area codes. Although this data can change over time, it is normally quite static. You can use an XML file checkpoint to validate that the data has not changed from one application release to another.

- An XML file can consist of elements with attributes and values (character data). There is a parent and child relationship between the elements, and elements can have attributes associated with them. If any part of this structure (including data) changes, your application's ability to process the XML file may be affected. Using an XML checkpoint, you can check the content of an element to make sure that its tags, attributes, and values have not changed.

- XML files are often an intermediary that retrieves dynamically changing data from one system. The data is then accessed by another system using Document Type Definitions (DTD), enabling the accessing system to read and display the information in the file. You can use an XML checkpoint and parameterize the captured data values in order to check an XML document or file whose data changes in a predictable way.

- XML documents and files often need a well-defined structure in order to be portable across platforms and development systems. One way to accomplish this is by developing an XML schema, which describes the structure of the XML elements and data types. You can use schema validation to check that each item of content in an XML file adheres to the schema description of the element in which the content is to be placed.

36. Object Repositories types, which & when to use?
A.) To choose the default object repository mode and the appropriate object repository mode for each test, you need to understand the differences between the two modes. In general, the object repository per-action mode is easiest to use when you are creating simple record and run tests, especially under the following conditions:

- You have only one, or very few, tests that correspond to a given application, interface, or set of objects.

- You do not expect to frequently modify test object properties.

- You generally create single-action tests.

Conversely, the shared object repository mode is generally the preferred mode when:

- You have several tests that test elements of the same application, interface, or set of objects.

- You expect the object properties in your application to change from time to time and/or you regularly need to update or modify test object properties.

- You often work with multi-action tests and regularly use the Insert Copy of Action and Insert Call to Action options.

37. Can we Script any test case with out having Object repository? or Using Object Repository is a must?
Ans: No. U can script with out Object repository by knowing the Window Handlers, spying and recognizing the objects logical names and properties available.

38. How to execute a WinRunner Script in QTP?
Ans :

(a) TSLTest.RunTest TestPath, TestSet [, Parameters ] --> Used in QTP 6.0 used for backward compatibility

Parameters: The test set within Quality Center , in which test runs are stored. Note that this argument is relevant only when working with a test in a Quality Center project. When the test is not saved in Quality Center , this parameter is ignored.
e.g : TSLTest.RunTest "D:\test1", ""

(b) TSLTest.RunTestEx TestPath, RunMinimized, CloseApp [, Parameters ]
TSLTest.RunTestEx "C:\WinRunner\Tests\basic_flight", TRUE, FALSE, "MyValue"
CloseApp : Indicates whether to close the WinRunner application when the WinRunner test run ends.
Parameters : Up to 15 WinRunner function argument

39. How to handle Run-time errors?
Ans: On Error Resume Next : causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. This allows execution to continue despite a run-time error. You can then build the error-handling routine inline within the procedure. Using "Err" object msgbox "Error no: " & " " & Err.Number & " " & Err.description & " " & Err.Source & Err.HelpContext

40. How to change the run-time value of a property for an object?
Ans : SetTOProperty changes the property values used to identify an object during the test run. Only properties that are included in the test object description can be set.

41. How to retrieve the property of an object?
Ans : using "GetRoProperty".

42. How to open any application during Scripting?
Ans : SystemUtil, object used to open and close applications and processes during a run session. A SystemUtil.Run statement is automatically added to your test when you run an application from the Start menu or the Run dialog box while recording a test
E.g : SystemUtil.Run "Notepad.exe"
SystemUtil.CloseDescendentProcesses (Closes all the processes opened by QTP)

43. Types of properties that Quick Test learns while recording?

Ans : (a) Mandatory (b) Assistive .

In addition to recording the mandatory and assistive properties specified in the Object Identification dialog box, QuickTest can also record a backup ordinal identifier for each test object. The ordinal identifier assigns the object a numerical value that indicates its order relative to other objects with an otherwise identical description (objects that have the same values for all properties specified in the mandatory and assistive property lists). This ordered value enables QuickTest to create a unique description when the mandatory and assistive properties are not sufficient to do so.

44. What is the extension of script and object repository files?
Ans : Object Repository : .tsr , Script : .mts, Excel : Default.xls

45. How to supress warnings from the "Test results page"?
Ans : From the Test results Viewer "Tools > Filters > Warnings"...must be "Unchecked".

46. When we try to use test run option "Run from Step", the browser is not launching automatically why?

Ans : This is default behaviour.

47. How to "Turn Off" QTP results after running a Script?
Ans : Goto "Tools > Options > Run Tab" and Deselect "View results when run session ends". But this supresses only the result window, but a og will be created and can viewed manulaly which cannot be restricted from getting created.

48. How to verify the Cursor focus of a certain field?
Ans : Use "focus" property of "GetRoProperty" method"

49. How to make arguments optional in a function?
Ans : this is not possible as default VBS doesn't support this. Instead you can pass a blank scring and have a default value if arguments r not required.

50. How to covert a String to an integer?
Ans : CInt()---> a conversion function available.

51. Inserting a Call to Action is not importing all columns in Datatable of globalsheet. Why?
Ans : Inserting a call to action will only Import the columns of the Action called

52. How to get "FontSize" of a "WebEdit"?

53. Does QTP is "Unicode" compatible?

54. How to get "FontSize" of a "WebEdit"?

55. Is there anyway to automatically update the Datasource name in Database Checkpoints object when we migrate tests to a new release?

56. Any limitation to XML Checkpoints?

57. What do you to script when objects are removed from application?

58. How to create a Runtime property for an object?

59. How to attach a file to TD?

Sofware - Testing

Q1. Deliverables of test design phase include all the following except:
a) Test data
b) Test data plan
c) Test summary report
d) Test procedure plan

Q2. Which of the following is not decided in the test-planning phase?
a) Schedules and deliverables
b) Hardware and software
c) Entry and exit criteria
d) Types of test cases

Q3. Typical defects that are easier to find in reviews than in dynamic testing are:
A. deviations from standards,
B.requirement defects,
C.design defects,
D.insufficient maintainability and incorrect interface specifications.
E.All of the above.

Q4. Load Testing Tools
a) reduces the time spent by the testers
b) reduces the resources spent (hardware)
c) mostly used in web testing
d) all of the above

Q5. Reviews, static analysis and dynamic testing have the same objective –
A.identifying defects.
B. fixing defects.
C. 1 and 2
D. None

Q6. Defect arrival rate curve:
A. Shows the number of newly discovered defects per unit time
B. Shows the number of open defects per unit time.
C. Shows the cumulative total number of defects found up to this time.
D. Any of these, depending on the company.

Q7. What are the 2 major components taken into consideration with risk analysis?
a) The probability the negative event will occur
b) The potential loss or impact associated with the event
c) Both a and b
d) Neither a nor b

Q8. We can achieve complete statement coverage but still miss bugs because:
A. The failure occurs only if you reach a statement taking the TRUE branch of an IF statement, and you got to the statement with a test that passed through the FALSE branch.
B. The failure depends on the program's inability to handle specific data values, rather than on the program's flow of control.
C. Both A and B
D. We are not required to test code that customers are unlikely to execute.

Q9. Who is responsible for conducting test readiness review?
a. Test manager
b. Test engineer
c. both A & B
d. Project Manager

Q10. What if the project isn't big enough to justify extensive testing?
a) Use risk based analysis to find out which areas need to be tested
b) Use automation tool for testing
c) a and b
d) None of the above

Q11. What are the key features to be concentrated upon when doing a testing forworld wide web sites
a) Interaction between html pages
b) Performance on the client side
c) Security aspects
d) All of the above

Q12. What can be done if requirements are changing continuously?
a) Work with the project's stakeholders early on to understand howrequirements might change so that alternate test plans and strategiescan be worked out in advance, if possible.
b) Negotiate to allow only easily-implemented new requirements into theproject, while moving more difficult new requirements into futureversions of the application
c) Both a and b
d) None of the above

Q13. The selection of test cases for regression testing
a) Requires knowledge on the bug fixes and how it affect the system
b) Includes the area of frequent defects
c) Includes the area which has undergone many/recent code changes
d) All of the above

Q14. Measurement dysfunction is a problem because:
A. Even though the numbers you look at appear better, to achieve these numbers, people are doing other aspects of their work much less well.
B. We don't know how to measure a variable (our measurement is dysfunctional) and so we don't know how to interpret the result.
C. You are measuring the wrong thing and thus reaching the wrong conclusions.
D. All of the above.

Q15. What do you mean by “Having to say NO”
a. No, the problem is not with testers
b. No, the software is not ready for production
c. Both a & b
d. none of the above

Q16. According to the lecture, there are several risks of managing your project's schedule with a statistical reliability model. These include:
A. Testers spend more energy early in the product trying to find bugs than preparingto do the rest of the project's work more efficiently
B. Managers might not realize that the testing effort is ineffective, late in the project,because they expect a low rate of bug finding, so the low rate achieved doesn'talarm them.
C. It can increase the end-of-project pressure on testers to not find bugs, or to notreport bugs.
D. All of the above

Q17. Operations testing is:
a. compliance testing
b. disaster testing
c. verifying compliance to rules
d. functional testing
e. ease of operations

Q18. Tools like change Man, Clear case are used as
a. functional automation tools
b. performance testing tools
c. configuration management tools
d. none of the above.

Q19. Important consequences of the impossibility of complete testing are
A. We can never be certain that the program is bug free.
B. We have no definite stopping point for testing, which makes it easier for somemanagers to argue for very little testing.
C. We have no easy answer for what testing tasks should always be required,because every task takes time that could be spent on other high importance tasks.
D. All of the above.

Q20. Which is not in sequence in 11 Step Software Testing process
a) Assess development plan and status
b) Develop the test plan
c) Test software design
d) Test software requirement

Q21. In the MASPAR case study:
A. Security failures were the result of untested parts of code.
B. The development team achieved complete statement and branch coverage butmissed a serious bug in the MASPAR operating system.
C. An error in the code was so obscure that you had to test the function with almostevery input value to find its two special-case failures.
D. All of the above.

Q22. Complete statement and branch coverage means:
A. That you have tested every statement in the program.
B. That you have tested every statement and every branch in the program.
C. That you have tested every IF statement in the program.
D. That you have tested every combination of values of IF statements in the program

Q23. What if the project isn't big enough to justify extensive testing
a) Use risk based analysis to find out which areas need to be tested
b) Use automation tool for testing
c) a and b
d) None of the above

Q24. Security falls under
a. compliance testing
b. disaster testing
c. verifying compliance to rules
d. functional testing
e. ease of operations

Q25. Which is the best definition of complete testing:
A. You have discovered every bug in the program.
B. You have tested every statement, branch, and combination of branches in theprogram.
C. You have completed every test in the test plan.
D. You have reached the scheduled ship date.

Q26. What is the concept of introducing a small change to the program and having theeffects of that change show up in some test?
a) Desk checking
b) Debugging a program
c) A mutation error
d) Performance testing
e) Introducing mutations

Software Testing Metrics

1. Cost of finding a defect in testing (CFDT)

= Total effort spent on testing / defects found in testing

Note: Total time spent on testing including time to create, review, rework, execute the test cases and record the defects. This should not include time spent in fixing the defects.

2. Test Case Adequacy: This defines the number of actual test cases created vs estimated test cases at the end of test case preparation phase. It is calculated as

No. of actual test cases / No: of test cases estimated

3. Test Case Effectiveness: This defines the effectiveness of test cases which is measured in number of defects found in testing without using the test cases. It is calculated as

No. of defects detected using test cases*100/Total no: of defects detected

4. Effort Variance can be calculated as

{(Actual Efforts-Estimated Efforts) / Estimated Efforts} *100

5. Schedule Variance: It can be calculated as

{(Actual Duration - Estimated Duration)/Estimated Duration} *100

6. Schedule Slippage: Slippage is defined as the amount of time a task has been delayed from its original baseline schedule. The slippage is the difference between the scheduled start or finish date for a task and the baseline start or finish date. It is calculated as

((Actual End date - Estimated End date) / (Planned End Date – Planned Start Date) * 100

7. Rework Effort Ratio:

{(Actual rework efforts spent in that phase / Total actual efforts spent in that phase)} * 100

8. Review Effort Ratio:

(Actual review effort spent in that phase / Total actual efforts spent in that phase) * 100

9. Requirements Stability Index:

{1 - (Total No. of changes /No of initial requirements)}

10. Requirements Creep:

(Total No. of requirements added / No of initial requirements) * 100

11. Weighted Defect Density:

WDD = (5*Count of fatal defects)+(3*Count of Major defects)+(1*Count of minor defects)

Note: Here the Values 5, 3, 1 correspond to severities as mentioned below: