Skip to main content

How to earn money using your Software Testing expertise

How to earn money using your Software Testing expertise ?

 1. Start your Own blog ?

 Start your own blog in Blogspot or with your own Domain and write your own content  share knowledge with fellow testing community.

 Content for your blogs may create interest in fellow testers.

 write a review about the software testing tools you are using currently  .

 Or evavualate a Open source Testing Tool and give your feed back about pros and cons.

 Start writing content for Software Testing Blogs who will pay for Article also a good choice of Revenue. Softwaretestinghelp.com paying for articles who share with them

  2. Become a member in UTest or 99 Tests

 Now a days with the increase of Gadgets , Mobiles, Smart TV and (IOT) Internet of things , The scope of testing  is changed .
 Companies developing Apps or specified programs for General public are relied on Crowd source companies like UTest,99 Tests etc.
 Create your own profile with all your Electronic inventory like mobiles,Tabs, Smart tv, Smart Appliance and complete the Sand box or a Free project which will evaluate your skills on QA knowledge.

 Based on your Ratings you will be invited for Paid projects.

 Utest and 99 Test are most active Crowd source Platform for QA and Testing Community.

 some times you can upto $ 1** for referrals on specific projects. for more info Visit UTEST forum and Blogs .

 Forums like UTEST or 99 Tests giving oppurtunity for novoice testers.

Freshers who are looking for Job in Software testing field these forums are training ground, they can horn their software testing skills and learn testing new technologies.

 I will keep updating this post whenever i get encounter with something new in Software testing field.

Thanks for reading this article,

Please provide your feedback in comments column.

Comments

Popular posts from this blog

Internet is harmful for you: Google thinks so

Click the image to see it in full size:



Today, for a few minutes Google suddenly started warning all of its indexed sites as Harmful to your computer! Perhaps it was a glitch in their algorithm, but we managed to make a snap of it for the record.

test coverage matrix vs traceblity matrix

Test coverage matrix:

Test coverage matrix is a checklist which ensures that the functionality of the given screen(unit) is checked in all possible combinations (positive and negative) which have not been covered in test cases. Test coverage matrix is usually prepared for a screen having large number of controls (textboxes, dropdowns, buttons etc) usually, test coverage matrix is prepared in a spread sheet having all the controls (textboxes, dropdowns, buttons etc) in the columns and then all possible entries in those fields in the rows with an ''yes'' or ''no'' in the rows against the controls listed in the columns. For example, consider a ''login'' screen wherein we have ''username'' and ''password" textfields.

While preparing test coverage matrix, the first column will be ''s.no'' and the second will be ''username" and ''password" will be the third field followed by …

Cyclomatic complexity

Cyclomatic complexity is a software metric (measurement). It was developed by Thomas McCabe and is used to measure the complexity of a program. It directly measures the number of linearly independent paths through a program's source code. It is computed using a graph that describes the control flow of the program. The nodes of the graph correspond to the commands of a program. A directed edge connects two nodes if the second command might be executed immediately after the first command.


Definition

M = E − N + 2P

where

M = cyclomatic complexity
E = the number of edges of the graph
N = the number of nodes of the graph
P = the number of connected components.

"M" is alternatively defined to be one larger than the number of decision points (if/case-statements, while-statements, etc) in a module (function, procedure, chart node, etc.), or more generally a system.

Separate subroutines are treated as being independent, disconnected components of the program's control flow graph.