tanvi91jain
Member • Feb 3, 2014
Is SQL knowledge must for a test engineer?
For system testing is it mandatory to know SQL....?
Howdy guest!
Dear guest, you must be logged-in to participate on CrazyEngineers. We would love to have you as a
member of our community. Consider creating an
account or login.
Replies
-
Administrator • Feb 3, 2014
Nope, it's not a must. But is incredibly useful if you ever get into database testing.tanvi91jainFor system testing is it mandatory to know SQL....?Are you sure? This action cannot be undone. -
Member • Feb 3, 2014
ok... as compared to developer opportunities for test engineer is less???? i m hardly getting calls according to ma profile.....😔Kaustubh KatdareNope, it's not a must. But is incredibly useful if you ever get into database testing.Are you sure? This action cannot be undone. -
Administrator • Feb 3, 2014
Where you get a call or not will depend on several factors. Your skills set; location, experience etc. Keep updating your skills set and be prepared for the next opportunity that knows your door.tanvi91jainok... as compared to developer opportunities for test engineer is less???? i m hardly getting calls according to ma profile.....😔Are you sure? This action cannot be undone. -
Member • Feb 5, 2014
thanks...Are you sure? This action cannot be undone. -
Administrator • Feb 5, 2014
Companies looking for a tester for either a database or for a heavily data driven application will look for your SQL knowledge.
It is entirely project based.
If it is a database project, you should be comfortable with writing queries including JOINS, UNIONS etc.
You should also have a good understanding of what some of the different performance implications are around inserts and updates, how indexing works for the various database platform they are using and that sort of thing.
PS: Any kind of knowledge can't go to waste. Try to improve your skills in related areas when you have time at hand.Are you sure? This action cannot be undone. -
Member • Feb 7, 2014
In a typical development team of 9 people, there's only one tester. After all, development of a piece of functionality takes more effort than testing the same.tanvi91jainok... as compared to developer opportunities for test engineer is less???? i m hardly getting calls according to ma profile.....😔Are you sure? This action cannot be undone. -
Administrator • Feb 7, 2014
Disagree. Testing is an ongoing , continuous process.Anand TamariyaIn a typical development team of 9 people, there's only one tester. After all, development of a piece of functionality takes more effort than testing the same.Are you sure? This action cannot be undone. -
Member • Feb 7, 2014
When did I say it's not an ongoing process. I was just talking about the team composition.Kaustubh KatdareDisagree. Testing is an ongoing , continuous process.Are you sure? This action cannot be undone. -
Administrator • Feb 7, 2014
I disagree that development of a functionality takes more time than testing it. There cannot be a set standard for this.Anand TamariyaWhen did I say it's not an ongoing process. I was just talking about the team composition.Are you sure? This action cannot be undone. -
Member • Feb 8, 2014
How many testers vs. developers does CE have?Kaustubh KatdareI disagree that development of a functionality takes more time than testing it. There cannot be a set standard for this.Are you sure? This action cannot be undone. -
Member • Feb 8, 2014
In our team we have equal ratio of tester and developers.
Developer job to code and well unit test and tester job is to test and take responsibility of functionality, testers also take responsibility of other project activity because they have some extra bandwidth than developers.
And any wrong/delay happening is always responsibility of team not the developers.
This way too less ration and I don't think proper documentation being done on testing.Anand TamariyaIn a typical development team of 9 people, there's only one tester.
So if anything goes wrong you will blame the developer right? and when this will happen, in final stage or after delivering the project.
Any software you are developing should have proof that you have coded and executed the test script which should contains all the test scenario mentioned in Use Case (requirement). this requires to code test scenarios/writing test scripts.
These script are validated against requirement.
If anything goes wrong or in dispute this executed script are validated to ensure that software developed exactly as per requirement and script executed and find out where things went wrong.
This ensure the project quality and validate all requirement. As much as developer responsibility to code , tester responsibility to ensure the quality and all requirement met with proof.Are you sure? This action cannot be undone. -
Administrator • Feb 8, 2014
One developer and 5 testers.Anand TamariyaHow many testers vs. developers does CE have?Are you sure? This action cannot be undone. -
Member • Feb 8, 2014
(bow) to mighty developer 😀Kaustubh KatdareOne developer and 5 testers.Are you sure? This action cannot be undone. -
Member • Feb 9, 2014
Thanks for the information. We are probably placed on the opposite side of the spectrum!!Kaustubh KatdareOne developer and 5 testers.Are you sure? This action cannot be undone. -
Member • Feb 10, 2014
exactly... a test engineer starts working,d moment requirements come.....as he reads,reviews n then starts preparing the test documents....Kaustubh KatdareDisagree. Testing is an ongoing , continuous process.Are you sure? This action cannot be undone. -
Administrator • Feb 10, 2014
I'm against generalisation. This platform, called 'xenforo' itself is being developed by two developers and tested by a strong community of over 500+ people.Are you sure? This action cannot be undone. -
Member • Feb 11, 2014
Well in my experience (I have worked in mini projects and there) testing played an important role as after coding is successful only after a successful testing.Are you sure? This action cannot be undone.