A Blog for quality professional

Engineer’s life

Dear all this poem is based on true story………….

Consider your self as a character of the story (Pappu) and realized the today life

Belive me it realy work…………………….

Dedicated to all my colleagues , senior junior(India & Abroad)

************ ISSUED IN PUBLIC INTEREST*************

Pareshaan thi Pappu ki wife
Non-happening thi jo uski life
Pappu ko na milta tha aaram
Office main karta kaam hi kaam

Pappu ke boss bhi the bade cool
Promotion ko har baar jate the bhul
Par bhulte nahi the wo deadline
Kaam to karwate the roz till nine

Pappu bhi banna chata tha best
Isliye to wo nahi karta tha rest
Din raat karta wo boss ki gulami
Appraisal ke ummid main deta salami

Din guzre aur guzre fir saal
Bura hota gaya Pappu ka haal
Pappu ko ab kuch yaad na rehta tha
Galti se Biwi ko Behenji kehta tha

Aakhir ek din Pappu ko samjh aaya
Aur **** di usne Appraisal ki moh maya
Boss se bola, “Tum kyon satate ho ?”
“Appraisal ke laddu se buddu banate ho”

“Promotion do warna chala jaunga”
“Appraisal dene par bhi wapis na aunga”
Boss haans ke bola “Nahi koi baat”
“Abhi aur bhi Pappus hai mere paas”

“Yeh duniya Pappuon se bhari hai”
“Sabko bas aage badhne ki padi hai”
“Tum na karoge to kisi aur se karaunga”
“Tumhari tarah Ek aur Pappu banaunga”

Advertisements

Prototype Development

The goal of prototyping based development is to counter the first two limitations of the waterfall model discussed earlier. The basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements. Development of the prototype obviously undergoes design, coding and testing. But each of these phases is not done very formally or thoroughly. By using this prototype, the client can get an “actual feel” of the system, since the interactions with prototype can enable the client to better understand the requirements of the desired system.

Prototyping is an attractive idea for complicated and large systems for which there is no manual process or existing system to help determining the requirements. In such situations letting the client “plan” with the prototype provides invaluable and intangible inputs which helps in determining the requirements for the system. It is also an effective method to demonstrate the feasibility of a certain approach. This might be needed for novel systems where it is not clear that constraints can be met or that algorithms can be developed to implement the requirements. The process model of the prototyping approach is shown in the figure below.

Prototyping Model
Prototyping Model

The basic reason for little common use of prototyping is the cost involved in this built-it-twice approach. However, some argue that prototyping need not be very costly and can actually reduce the overall development cost. The prototype are usually not complete systems and many of the details are not built in the prototype. The goal is to provide a system with overall functionality. In addition, the cost of testing and writing detailed documents are reduced. These factors helps to reduce the cost of developing the prototype. On the other hand, the experience of developing the prototype will very useful for developers when developing the final system. This experience helps to reduce the cost of development of the final system and results in a more reliable and better designed system.

If you are freshers and willing to choose software testing as your career then this is a must read!

a common answer to all questions whether you should choose software testing as your career or not?

Let me first explain in brief about software testing. Software testing and quality control are the processes by means of which application quality is improved. Software testing is done in each phase of product life cycle i.e from requirement specifications , design, coding, to the user acceptance.

Many complex software structures require in depth analytical and technical skill to test the applications. Knowledge of programming languages is required for unit testing, scripting skill essential for Automation testing.

Now we will speak about your career in software testing. No one can guide you choosing your career more than you! Its right and you are the only person to decide your career.
Do self-assessment to figure out where you can fit well. Do study of your skills, interests, strengths, weaknesses.

Ask some questions to your self like:
What is your goal in life?
What will increase your satisfaction and skill?
What is your interest?
Which skills you have developed in your life till now?
Which training you did that can be applied to future job?

By answering these questions you will automatically come to decision.

To switch to software testing career What skills you will require? Is the most important question I think.

In my previous post what makes a good test engineer, I mentioned some of the software testing required skills.

1. Communication: Customer communication as well as team communication most important for this job. Written communication as well!

2. Technical skill: As I mentioned earlier for testing technical domain skill in languages is important.

Some of the Testing skills are:
Project life cycle,
Testing concepts,
Knowledge of testing types,
Programming languages familiarity,
Database concepts,
Test plan idea,
Ability to analyze requirements,
Documentation skill,
Testing tools

3. Leadership quality
4. Analytical and judging skill

Don’t worry if you don’t have some of the skills mentioned above. You can always learn the things if you have interest. Non-IT personas can also grow fast by gaining necessary skills.

So finally selecting testing as your career ask one question to yourself:

———For all upcoming  I.T.M Ambassador


My Real Friends

“Even though we’ve changed (Shobhit,Rohan,Abhi,Satyam,Pankaj and Rucchi) and we’re all finding our own place in the world, we all know that when the tears fall or the smile spreads across our face, we’ll come to each other because no matter where this crazy world takes us, nothing will ever change so much to the point where we’re not all still friends.”

Dear all,following question is based on my own personal experience and you can say that this question is often asked whenever you are facing some technical face to face. hope so its beneficial  for you

content referenced from  popular Testing sites

Why does software have bugs?

What’s the big deal about ‘requirements’?

What’s the role of documentation in QA?

What steps are needed to develop and run software tests?

What’s a ‘test plan’?

What’s a ‘test case’?

What should be done after a bug is found?

What if the software is so buggy it can’t really be tested at all?

What if there isn’t enough time for thorough testing?

What if the project isn’t big enough to justify extensive testing?

What can be done if requirements are changing continuously

What if the application has functionality that wasn’t in the requirements?

.How can Software QA processes be implemented without stifling productivity?

What if an organization is growing so fast that fixed QA processes are impossible?

How does a client/server environment affect testing?

How can World Wide Web sites be tested? (refer to my web testing post)

What is ‘Software Quality Assurance’?

What are some recent major computer  failures caused by software bugs?

Why is it often hard for management to get serious about quality assurance?

What is verification? validation?

What kinds of testing should be considered?

What are  common problems in the  software development process?

What is SEI? CMM? ISO? IEEE? ANSI? Will it help?

Will automated testing tools make testing easier?

hope so its beneficial  for you

content referenced from  popular Testing sites

Often in this situation we always proceed toward “error guessing” (in situation of unclear requirement)

Error guessing: A test design technique where the experience of the tester is used to
anticipate what defects might be present in the component or system under test as a result
of errors made, and to design tests specifically to expose them. Error Guessing comes with experience with the technologyand the project. Error Guessing is the art of guessing where errors can be hidden. There are no specific tools and techniques for this, but you can write test cases depending on the situation: Either when reading the functional documents or when you are testing and find an error that you have not documented.

Error Guessing is the ability to find errors or defects in the AUT by what appears to be intuition. In fact, testers who are effective at error guessing actually use a range of techniques, including:
* Knowledge about the AUT, such as the design method or implementation technology
* Knowledge of the results of any earlier testing phases (particularly important in Regression Testing)
* Experience of testing similar or related systems (and knowing where defects have arisen previously in those systems)
* Knowledge of typical implementation errors (such as division by zero errors)
* General testing rules of thumb of heuristics

web testing applying mainly in

  • Web Testing for HTML, Dynamic HTML, JavaScript/VBScript based web applications.
  • Web Testing for ASPJSPPHP.NET based web applications.
  • Web Testing for applications that include ActiveX components.
  • Web Testing for AJAX based web applications.
  • Functionality Testing – Test Web Applications/Web Sites to ensure that all aspects of your site functions properly such as images, text, form elements, dialogs, menus appear correctly, HTML links work, form submissions succeed, etc
  • Compatibility Testing – Test Web Applications/Web Sites to ensure that it is compatible with different browsers, operating systems, languages, databases and servers.
  • Localized Testing – Automate localization testing of your web applications/web sites to test multi-language deployments of your applications without re-recording.
  • Stress Testing – Test Web Applications/Web Sites to determine the system’s breaking point based on predefined failure criteria.
  • Load Testing – Test Web Applications/Web Sites to ensure that it is capable of handling a predetermined peak load by generating 1000’s of users on the Web site.
  • Web Services Functional Testing – Test Web Services to ensure that the functionality works correctly by validating the responses sent to each SOAP/HTTP request.
  • Web Services Performance Testing – Test Web Services to gather the performance and stability information of web services by realistically simulating the load on your web services.
  • Regression Testing – Test Web Applications/Web Sites/Web Services by running all day and night to ensure that it is still working between builds or releases.

Tag Cloud