Tag Archives: errors

Tips for writing a killer software testing QA resume

As we know, the resume is very important while looking for jobs. It’s an opportunity to advertise yourself and demonstrate that you are the best person for the available position. Here we’ll talk about how to write a masterpiece of software testing resume that will turn into an interview call. Let’s learn some tips:

1. Keep CV brief but comprehensive in expression

2. Single spelling error is sufficient to reject your resume. Spell chect for twice.

3. CV should be easily readable

4. Make a clear job objective

5. Highlight relevant skills

6. Do not put fake experience or skills

7. Focus on what employer’s perspective.

8. Always think from employer’s perspective.

9. Avoid table structure. Use tables to mention your qualification and skills only.

10. Do not write resume more than 3 pages unless you are applying for team lead or managerial positions.

11. Do not add irrelevant personal details.

12. No need to write ‘Curriculum Vitae’ or ‘Resume’ word at the top of your resume.

13. Do not use word ‘I’ while describing project responsibilities.

14. Make sure you write your name, email address and phone number on top of the resume.

15. While writing education always start with recent education first.

16. Write qualification details with columns – Education/Qualification, School/College, Year, Percentage/Grade, Class

17. Write relevant skills and on-job-accomplishments on first page of your resume and work experience, educational details on second page.

Additionally, you need to write an effective software testing job cover letter before applying for software testing jobs.

Source: http://www.softwaretestinghelp.com/how-to-write-a-killer-software-testing-qa-resume-that-will-turn-into-an-interview-call/

Did you like this? Share it:

How to write bug reprot

After testing your computer and finding some bugs, you will need to report a bug in bug tracking tool. Here is a sample for bug report.

Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005

Once again the seven steps you should remember while making bug report.

1. Logon into the application

2. Navigate to the Users Menu > New User

3. Filled all the user information fields

4. Clicked on ‘Save’ button

5. Seen an error page ‘ORA 1090 Exception: Insert values Error…’

6. See the attached logs for more information

7. See the attached screenshot of the error page

Source: http://www.softwaretestinghelp.com/sample-bug-report/

Did you like this? Share it:

The improtance of software testing documentation

Documentation is important. However, many people haven’t realized it. Projects that have all the documents have high level of maturity. And careful documentation can save an organization’s time, efforts and money. Here we will list some improtant software testing documetns.

1. Test plan

2. Test design and Test case specification

3. Test Strategy

4. Test summary reprots

5. Weekly Status Report

6. User Documents/ manuals

7. User Acceptance Report

8. Risk Assessmetn

9. Test Log

10. Bug reports

11. Test data

12. Test analysis

Also there are two documents refered to for software testers: Software requiremetn specifications, and Functional documetns.

Source: http://www.softwaretestinghelp.com/why-documentation-is-important-in-software-testing/

Did you like this? Share it:

The 2011 Top 25 common programming bugs

As a software tester, you should know the 25 common programming errors. Through it you can get insight on how developers can unknowingly leave bugs in software programs. Furthermore, the top 25 security bugs will help prigrammers to avoid some common but serious coding mistakes. Here is the Top 25 list:

1. SQL Injection

2. OS command Injestion

3. Classic Buffer Overflow

4. Cross-site Scripting

5. Missing Authentication for Critical Function

6. Missing Authorization

7. Use of Hard-coded Credentials

8. Missing Encryption of Sensitive Data

9. Unrestricted Upload of File with Dangerous Type

10. Reliance on Untrusted Inprts in a Security Decision

11. Execution whit Unnecessary Privileges

12. Cross-Site Request Forgery

13. Path Traversal

14. Download of Code Without Integrity Check

15. Incorrect Authorization

16. Inclusion of Functionality from Untrusted Control Sphere

17. Incorrect Permission Assignment for Critical Resource

18. Use of Potentially Dangerous Function

19. Use of a Broken or Risky Cryptographic Algorithm

20. Incorrect Calculation of Buffer Size

21. Improper Restriction of Excessive Authentication Attempts

22. Open Redirect

23. Uncontrolled Format String

24. Integer Overflow or Wraparound

25. Use of a One-Way Hash without a Salt

This year’s Top 25 entries are prioritized using inputs from over 20 different organizations, who evaluated each weakness based on prevalence, importance, and likelihood of exploit.

Source: http://www.softwaretestinghelp.com/top-25-common-teprogramming-bugs-every-tester-should-know/

Did you like this? Share it:

7 tips to be more innovative in the age of agile testing

The definition of agile testing in wikipedia is that testing from the customer perspective al early as possible and testing early and often as code becomes available and stable enough from module/unit level testing. There are some challenges in agile testing testers having to face while working with agile development team.

1. Obtain number of hours commitment up front

2. Gather Requirements / Estimates up front

3. Entering the actual hours and estimated hours daily

4. Daily builds

5. Keep the daily scrum meetings short

6. Code inspections are paramount

Hence, an agile tester needs to be innovative with the tools that they have so as to meet the challenges above. Here are important keys to innovation: creative, talented, fearless, visionary, empowered, passionate, and multiple disciplines. Watts Humpry said “Innovation is the process of turning ideas into manufacturable and marketable form.”

Source: http://www.softwaretestinghelp.com/7-tips-to-be-more-innovative-in-the-age-of-agile-testing-and-to-survive-an-economic-crisis/

Did you like this? Share it:

Top 25 most dangerous software errors

A very short article to share you something I found on internet today: the most dangerous software errors. I think it is important for testers to know it because it can be useful to keep in mind what kind of bugs developers can leave in their softwares.

Here are a few bugs discussed in this ranking:

- Improper neutralization of special elements used in an SQL Command (‘SQL Injection’)

- Buffer copy without checking size of input (‘Classic buffer overflow’)

- Download of code without integrity check

- …

Everything is discussed in details in this website: http://cwe.mitre.org/top25/

Have a look !

Did you like this? Share it: