IOmundo - A new beginning
dateSeptember 06 2013 | comments 0 comments
The first phase of a new job is exciting but it can also be a bit painful. Hopes and expectations are high but so is your dependence on others to show you how to do things at a time when you’re anxious to prove yourself.
It is difficult to share your thoughts... You don’t know these people sitting next to you at the office or at lunch but they are the ones who will share with you their morning coffee and... the same project.

As a new tester I will share with you some useful tips for a better accommodation and better results in your project.
There are no 'best practices' in software testing. All the best practices are context driven and are not standard. So, the practice that fits well in your project is the best practice for you. You may not necessarily go by a certain 'standard' that people follow in their organizations. Instead, you may have to look around your organization for existing processes.
First of all, take it slow. It might be small steps but it is the safe and useful way. In the first month, taking decisions should not be a priority, first immerse yourself in the project and be open to new ideas.
One other thing I would suggest is not to make your own assumptions unless it is mentioned clearly in requirements. You also should assume that your work contains mistakes, you need to check your own work. However, some mistakes come from bad assumptions and blind spots, so you might make the same mistakes when you check your own work as you made when you did it. You may not notice the flaws in what you have done. Ideally, you should get someone else to check your work - another person is more likely to spot the flaws.

What are the basic questions that should be asked when starting a new testing project?
Well...this set of questions will change depending on what test you want to conduct – it could be hardware testing, software testing, performance testing, load testing or functional testing. The basic and important ones are those who can lead you to a better understanding of project purpose.
Testing can give confidence in the quality of the software if it finds few or no defects. Of course, a poor test may uncover few defects and leave us with a false sense of security. A well-designed test will uncover defects if they are present and so you will be more confident in the software and be able to assert that the overall level of risk of using the system has been reduced. When testing does find defects, the quality of the software system increases and you can feel that you are a part of this process.

Another very useful lesson I learned in my first month of accomodation at IOmundo is getting help from people. It is easy to get frustrated by your dependence on others in a new job so you need to be patient with yourself.
And so I did... I asked for help, we communicated and I finally felt like taking part in a great team.

logo_iomundo-(1).jpg



dateSeptember 06 2013 | comments 0 comments

IOmundo - A new beginning
Comments
Blog post currently doesn't have any comments.
Leave comment



 Security code