mandatory requirements

looking at melb0urne software testing job requirements and advertisements, this one looks very serious:

• Proven experience and understanding of software testing methodologies.

• Strong experience in preparing and analysing test conditions based on Business Requirements.

• Demonstrated ability developing Test Cases from Functional Specifications & Design Documents.

• Proven experience and an understanding of System, Integration, and Functional testing execution.

• Proven experience in testing EAI solutions.

• A level of technology adeptness that enables the successful translation of requirements in test scripts.

• Experience in the use of Test Tools, particularly Mercury Quality Centre.

• Ability to work in a fast paced environment with possible dynamic priorities without compromising quality.

• Ability to quickly understand the organisation’s systems and applications and its integration with other systems.

• Proven, strong analytical and technical troubleshooting abilities.

my experience would not let to apply, still enough space to grow.


Comments

Offshore Software Development said…
IP & Data Security - Companies considering outsourcing their software development need to know and protect themselves against the risks related to the Intellectual property violations as well as Data Security. In order to mitigate this risk, clients need to check with the vendors on steps that they will take to protect their IP and the sensitive data such as customer information, employee information, financial data and market research data. This should be done during the Vendor Selection process.

Software Development Company
12:01 AM
senthil said…
Hi
i have seen your site it's very usefull
this is my site url pls give me u'r feedback

http://interviewskills.orgfree.com/

http://interviewskills.orgfree.com/
9:37 AM
Post a Comment

Popular posts from this blog

Retrofitting testing - what is it?

It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'.   Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog  http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/    article " Retrofit vs Retest vs Regression Testing " : Retrofit testing  is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ...
Read more

tester's day!

Happy testers day! Top 24 replies by programmers when their programs don't work: 24. "It works fine on MY computer" 23. "Who did you login as ?" 22. "It's a feature" 21. "It's WAD (Working As Designed)" 20. "That's weird..." 19. "It's never done that before." 18. "It worked yesterday." 17. "How is that possible?" 16. "It must be a hardware problem." 15. "What did you type in wrong to get it to crash?" 14. "There is something funky in your data." 13. "I haven't touched that module in weeks!" 12. "You must have the wrong version." 11. "It's just some unlucky coincidence." 10. "I can't test everything!" 9. "THIS can't be the source of THAT." 8. "It works, but it's not been tested." 7. "Somebody must have changed my code." 6. "Did you check for a virus on your system?...
Read more