Is SQL knowledge must for a test engineer?

tanvi91jain

@tanvi91jain-auojNQ • Oct 26, 2024

Oct 26, 2024

1.4K

For system testing is it mandatory to know SQL....?

Like 0 Replies 17

Replies

Welcome, guest

Join CrazyEngineers to reply, ask questions, and participate in conversations.

CrazyEngineers powered by Jatra Community Platform

Kaustubh Katdare

@thebigk • Feb 3, 2014

tanvi91jain
For system testing is it mandatory to know SQL....?
Nope, it's not a must. But is incredibly useful if you ever get into database testing.
0
tanvi91jain

@tanvi91jain-auojNQ • Feb 3, 2014

Kaustubh Katdare
Nope, it's not a must. But is incredibly useful if you ever get into database testing.
ok... as compared to developer opportunities for test engineer is less???? i m hardly getting calls according to ma profile.....😔
0
Kaustubh Katdare

@thebigk • Feb 3, 2014

tanvi91jain
ok... as compared to developer opportunities for test engineer is less???? i m hardly getting calls according to ma profile.....😔
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.
0
tanvi91jain

@tanvi91jain-auojNQ • Feb 5, 2014

thanks...
0
Ankita Katdare

@abrakadabra • 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.
0
Anand Tamariya

@anand-tamariya-DnfjEX • Feb 7, 2014

tanvi91jain
ok... as compared to developer opportunities for test engineer is less???? i m hardly getting calls according to ma profile.....😔
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.
0
Kaustubh Katdare

@thebigk • Feb 7, 2014

Anand Tamariya
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.
Disagree. Testing is an ongoing , continuous process.
0
Anand Tamariya

@anand-tamariya-DnfjEX • Feb 7, 2014

Kaustubh Katdare
Disagree. Testing is an ongoing , continuous process.
When did I say it's not an ongoing process. I was just talking about the team composition.
0
Kaustubh Katdare

@thebigk • Feb 7, 2014

Anand Tamariya
When did I say it's not an ongoing process. I was just talking about the team composition.
I disagree that development of a functionality takes more time than testing it. There cannot be a set standard for this.
0
Anand Tamariya

@anand-tamariya-DnfjEX • Feb 8, 2014

Kaustubh Katdare
I disagree that development of a functionality takes more time than testing it. There cannot be a set standard for this.
How many testers vs. developers does CE have?
0
Anoop Kumar

@anoop-kumar-GDGRCn • 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.

Anand Tamariya
In a typical development team of 9 people, there's only one tester.
This way too less ration and I don't think proper documentation being done on testing.
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.
0
Kaustubh Katdare

@thebigk • Feb 8, 2014

Anand Tamariya
How many testers vs. developers does CE have?
One developer and 5 testers.
0
Anoop Kumar

@anoop-kumar-GDGRCn • Feb 8, 2014

Kaustubh Katdare
One developer and 5 testers.
(bow) to mighty developer 😀
0
Anand Tamariya

@anand-tamariya-DnfjEX • Feb 9, 2014

Kaustubh Katdare
One developer and 5 testers.
Thanks for the information. We are probably placed on the opposite side of the spectrum!!
0
tanvi91jain

@tanvi91jain-auojNQ • Feb 10, 2014

Kaustubh Katdare
Disagree. Testing is an ongoing , continuous process.
exactly... a test engineer starts working,d moment requirements come.....as he reads,reviews n then starts preparing the test documents....
0
Kaustubh Katdare

@thebigk • 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.
0
Mrinmoy Swarnakar

@mrinmoy-swarnakar-pqfdvP • 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.
0