Guru.com Defect

How I reproduced this defect?

1.log in to guru.com

2.click on update existing profile

3.Click on Resume summary

4.Enter more than 1500 characters( this should allow only 1500 characters)

5.Click submit

6.see error displayed and trim the characters to more than 1500

7.Again click on submit

8. Now trim the characters to <=1500 and click submit

9. And it displays the below image showing by changing the font ( my initial fonts are in verdena and now it is another)

10 .Click on Submit Nothing will happen

P.S. : in the error it says I had entered 1787 characters and at left side of the bottom of the summary box ,it is saying 449 characters remaining. I am expecting the message should be 287 characters more or when I click on submit that should display a pop up of saying the 287 characters are more and trim them

While updating my profile in www.guru.com I just came across a defect which will not allow me to change the font of the provided text in the summary page as above

2. Next time when I tried with 3342 characters and clicked on submit below is the message displayed in pop up with correct calculations of figures

A post on the relationship between Programmer and Tester

Dear Programmer,

My job is to help you look good. My job is to support you as you create quality; to ease that burden instead of adding to it.

What follows are twelve commitments a tester should make to their programmers. They include things like:

• I provide a service. You are an important client of that service. I am not satisfied unless you are satisfied.
• I will learn the product quickly, and make use of that knowledge to test more cleverly.
• I will not carelessly waste your time. Or if I do, I will learn from that mistake.

But James is not in usual form unless he invites controversy, and that first bullet struck quite a chord with some of his readers. Testers provide a service!? Since when?

James wrote some follow-up that makes a fascinating and compelling case for more “service” between people within an organization, and that it’s not a bad thing for someone to serve their peers:

Please meditate on the difference between service and subservience. I am a servant and I am proud of that. I am support crew. I spent my time as a production programmer and I’m glad I don’t do that any more. I don’t like that sort of pressure. I like to serve people who will take that pressure on my behalf.

This doesn’t make me a doormat. Nobody wipes their feet on me– I clean their feet. There’s a world of difference. Good mothers know this difference better than anyone.

Source :

http://blog.utest.com/the-relationship-between-testers-and-programmers/2011/11/?utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Feed%3A+UtestBlog+%28uTest+Blog%29

steps to Upgrade to QC 11

To upgrade to v11...

1. Get v11
2. Get a license for v11
3. Install v11
4. Upgrade a COPY of the existing schema
5. Create a TEST domain and project in the existing production system
6. Deactivate it, run the Verify and Repair on the test project in v11 (this preps the project by adding tables to the project.)
7. Run the upgrade option located in the Verify and Repair area.
8. If all goes well, it will be successful, repeat the same process for all the other projects. (you don't have to create a new domain and project each time.)
9. Test, test, test to ensure everything is good.
10. Provide your users with the new URL (if there is one)
11. Sit back, pop open your favorite beverage of choice and celebrate your awesomeness!

Oracle Application system testing script - AP module

Download a document that explains the system testing of Oracle Applications AP module with system test scripts and detailed design document for the same

Restricting large attachments in Quality Center

Once your Quality Center users discover that they can add attachments to defects (and test cases, and test sets etc etc), your storage requirements increase dramatically. Here is a neat way to prevent your users from attaching files over a certain size anywhere in Quality Center.

A client had a requirement to reduce the use of QC attachment storage as a lot of users are using up a lot of space unnecessarily. In one instance I found over 80GB of file space taken up with a 100MB file endlessly repeated. The attachment was on a “template” test and the users had duplicated it whenever they copied and pasted the “template”

I had to get this working today so investigated the attachment object and found it has some hooks so we could get it working quite simply.

The “Attachment” object available in the sub can give you access to the “CR_ENTITY” it is linked to. This gives us ALL the areas where a user can create an attachment. From there it was simply trial and error until I had the attachment record (attRec) described correctly for each “CR_ENTITY”.

The code goes directly into the QC workflow Common scripts area and replaces the existing Sub “Attachment_New”.

Sub Attachment_New(Attachment)   'Use ActiveModule and ActiveDialogName to get the current context.   On Error Resume Next       'Remove new attachment if file size is too big     If Attachment.Type = 1 then 'Attachment is of type TDATT_FILE - a file.        MaxFileSize = 3145728 'Set the maximum attachment size in Bytes <<- 3mb is our limit!        If Attachment.FileSize > MaxFileSize then           Select Case Attachment.Field("CR_ENTITY")                  'Requirement                  Case "REQ"                       Set attRec = ReqFactory.Item(Attachment.Field("CR_KEY_1"))                  'TestPlan                  Case "ALL_LISTS" 'Folder                       Set attRec = TreeManager.NodeByID(Attachment.Field("CR_KEY_1"))                       msgbox attRec.ID                  Case "TEST" ' Test                       Set attRec = TestFactory.Item(Attachment.Field("CR_KEY_1"))                  Case "DESSTEPS" 'Test step                       Set attTest = TestFactory.Item(Test_Fields("DS_TEST_ID").Value)                       Set attRec = attTest.DesignStepFactory.Item(Attachment.Field("CR_KEY_1"))                  'TestLab                  Case "CYCL_FOLD" 'Folder                       Set attRec = TestSetTreeManager.NodeById(Attachment.Field("CR_KEY_1"))                  Case "CYCLE" 'Test Set                       Set attRec = TestSetFactory.Item(Attachment.Field("CR_KEY_1"))                  Case "TESTCYCL" 'TestInstance                       Set attRec = TSTestFactory.Item(Attachment.Field("CR_KEY_1"))                  Case "RUN" 'Run                       Set attRec = RunFactory.Item(Attachment.Field("CR_KEY_1"))                  Case "STEP"  'Run Step                       Set attRun = RunFactory.Item(Step_Fields("ST_RUN_ID").Value)                       Set attRec = attRun.StepFactory.Item(Attachment.Field("CR_KEY_1"))                  'Defects                  Case "BUG"                       Set attRec = BugFactory.Item(Attachment.Field("CR_KEY_1"))           End Select           set AttFac = attRec.Attachments           Msgbox "Please exit this record and refresh the QC page. The file: " & vbLF & _                  Attachment.Name & vbLf & " has been removed as it exceeds the required file size of 3mb."           AttFac.RemoveItem(Attachment.ID)        End If     End If     On Error GoTo 0 End Sub

SOURCE : JDS Australia Website

"Program: \bin\QTPro.exe. R6025 Pure Virtual Function Call"i1

Title:

Document ID:

Product:

Version:

OS:

Updated:

Error: "Program: \bin\QTPro.exe. R6025 Pure

Virtual Function Call"i1

KM211301

QuickTest Professional

Unspecified

2007-Nov-04

While replaying a test, a "Microsoft Visual C++ Run Library" error message appears.

Error: "Program: \bin\QTPro.exe.

R6025 - Pure Virtual Function Call"

Solution

Solution Title TUI 2830Install patch QTP60P23

We have a patch for the "Pure Virtual Function Call" error, which can be downloaded from our

patches database.

Patch description:

QTP60P23 - Fix the "Pure virtual function call" error in IE6 and various crashes in cases of heavily

dynamic frames loading

Installation instructions:

Run the installation application

Just for Indians : 10 classic Indianisms: 'Doing the needful' and more

We are a unique species, aren’t we? Not humans. Indians, I mean. No other race speaks or spells like we do.

Take greetings for example.

A friendly clerk asking me for my name is apt to start a conversation with, “What is your good name?” As if I hold that sort of information close to my heart and only divulge my evil pseudonym. Bizarre.

I call these Indianisms.

Which got me thinking about a compilation, a greatest hits of the most hilarious Indianisms out there. And here they are. The most common ones, and my favorites among them.

1. 'Passing out'

When you complete your studies at an educational institution, you graduate from that institution.

You do not "pass out" from that institution.

To "pass out" refers to losing consciousness, like after you get too drunk, though I’m not sure how we managed to connect graduating and intoxication.

Oh wait … of course, poor grades throughout the year could lead to a sudden elation on hearing you’ve passed all of your exams, which could lead to you actually "passing out," but this is rare at best.

2. 'Kindly revert'

One common mistake we make is using the word revert to mean reply or respond.

Revert means "to return to a former state."

I can’t help thinking of a sarcastic answer every time this comes up.

“Please revert at the earliest.”

“Sure, I’ll set my biological clock to regress evolutionarily to my original primitive hydrocarbon state at 1 p.m. today."

3. 'Years back'

If it happened in the past, it happened years ago, not "years back."

Given how common this phrase is, I’m guessing the first person who switched "ago" for "back" probably did it years back. See what I mean?

And speaking of "back," asking someone to use the backside entrance sounds so wrong.

“So when did you buy this car?”

“Oh, years back.”

“Cool, can you open the backside? I’d like to get a load in.”

4. 'Doing the needful'

Try to avoid using the phrase "do the needful." It went out of style decades ago, about the time the British left.

Using it today indicates you are a dinosaur, a dinosaur with bad grammar.

You may use the phrase humorously, to poke fun at such archaic speech, or other dinosaurs.

“Will you do the needful?”

“Of course, and I’ll send you a telegram to let you know it's done too.”

5. 'Discuss about'

“What shall we discuss about today?”

“Let’s discuss about politics. We need a fault-ridden topic to mirror our bad grammar.”

You don't "discuss about" something; you just discuss things.

The word "discuss" means to "talk about". There is no reason to insert the word "about" after "discuss."

That would be like saying "talk about about." Which "brings about" me to my next peeve.

Source : Yahoo News on November 13th,2011