Tuesday, 28 August 2018

Things to be Learned During QA Internship

Today I would like to add some information, guidance for the fresh graduates or undergraduate who is doing an internship (SQA Interns) or wants to start their professional career with an internship. My topic is especially related to the students in Pakistan. It is being considered a good opportunity to have an internship in the various organization depending on their domain sizes. Usually, organizations offer the internship for a couple of months depending on their environment. Most of the organization offer small amount during internship period & most of them do not offer a single penny. It actually depends on organization culture. 
Student avail these opportunities without having any critic review about the organization. Because at that time we got so much excited about the opportunity & forget that we might get a better opportunity in future. M not saying availing an internship opportunity is bad, m saying that availing an opportunity that doesn't add skills to your existing skills set is bad. Because it might harm your motivation level towards starting your career in the fields. Here is the list of the points you must be kept in your mind during your internship period so you can judge own your own that either you are doing the right internship or not:
1. Make sure organization have proper authenticity in the market.
2. The person (lead/manager) to whom you have been considered to report must have sound knowledge of the field.
3. Make sure the person train you for practical things like:

 4. Test cases writing

Make sure that person taught you everything "Positive (Happy) Scenario" as well as "Negative Scenario" too. In your next interview, the interviewer will definitely ask you about the negative testing scenario of any product.

5. SRS (software requirements specification document)

Make sure your lead shows you or give you an idea about the SRS document. Usually, it is confidential; an organization does share it with anyone. But at least you should have information about it. You can search it on your own. Mostly organization follow agile methodology & keep product backlog document for requirements updates.

6. Design's Testing (Mockups Testing)

You should have an awareness that GUI Issues have been recognized/highlighted in this phase. These defects are also called "Cosmetic Defects". Common/non-technical persons confused these issues with functional issues. And being a tester you'll listen to these dialogues in your career that, "Anybody can become the tester." or "Those who aren't good in development choose this field". It is totally wrong. Testing is a passion. It is an attitude. Not everybody can be a tester. Those who haven't information about this will definitely demotivate you. Don't bother some people have the bad habit of underestimating others. GUI issues have low priority and normally includes alignment issues, design issues, text issue & spelling mistakes etc. Although they are much important in some cases but often considered as minor issues. You can start learning about these issues but don't expect appreciation for such issues.

7. Functional Issues

After having general domain session or product overview, your focus should be on finding functional issues. After successful execution of happy/positive scenario try to find out functional issues by running test case with all possible negative scenarios.

8. Project Management Tools

Again this selection is also comprehended by the organization in which you are working as an internee. But you can explore by yourself. JIRA, Redmine, Yodiz is one of the most popular projects management tools. You must have familiarity with this tool. You can learn more about JIRA.

9. Bug Priority

During your internship be assured that you got known information about bug prioritization. Although is normally decided by the project manager in case you should have awareness about this prioritization. Because in the future when you have been assigned to manage a project by yourself at that time it will help you a lot. There are 3 types of bug priority which are low, medium & high. You can learn for about the factor Severity & Priority by the following link.

10. Documentation

For documentation, you must familiar with how to make a presentation of the bug report with using MS. Word, Ms. PowerPoint, Ms. Excel and much more. The list of document you should learn to make during your internship includes:
  • Test Cases Doc.
  • Bug Reporting.
  •  KT Doc. (Knowledge Transfer Document)
  • Smoke Report Writing
  • Compatibility/Responsive Testing Report
  • This is enough for internship level experience.

11. How to Communicate with Developers?

Make sure he/she taught you how to communicate with developers. You should be experienced enough how to communicate developers about the bug, reporting issues & if they couldn’t reproduce your reported issues than how you’ll going to behave & what to do in this scenario.

Conclusion:

In the end, I would like to conclude my topic as nobody will going to teach you unless you yourself show eager to learn new things. Be a quick learner. Try to explore more about the things & topics in which you find yourself bit weak. In my next topic, I’ll teach you some important websites & question that you must remember in order to prepare for "QA Fresh Interview Question". Don't forget to add your reviews in comments I would like to hear from your side. If you find it worthy, don't forget to share ... :)
Re