here my git hub link where i attached my work, can you guys please review it and give your valuable feedback, Since I’m beginnerMy github profile.
3 Likes
If you are following a video tutorial, I would sugges to stick with it till the end instead of switching channels. Every instructor has a different teaching style, and on changing channel for same content it might confuse you.
If you are still exploring content, there are free tutorials on YouTube and paid ones on Udemy. But do not rely completely on video tutorials go beyond that. Work on real projects, build a portfolio, and showcase your work on LinkedIn and GitHub.
If you are not familiar with API testing, start with manual testing using Postman. Once you get comfortable, move on to automation with Rest Assured.
And do not get overwhelmed. Taking one step at a time will lead to better progress than trying to do everything at once. Patience is needed.
Since you have picked Java, you will find a huge automation community, especially around Selenium. Connect with them to see what they are exploring and learning.
Read blogs and articles from experienced professionals in automation. You can easily find great content on LinkedIn, MoT .
And most importantly, practice daily, even if it is just one program.
4 Likes
Thank you for your valuable suggestion! I will definitely stick to one channel instead of switching between multiple platforms.
As a beginner, I have been uploading my work on GitHub, but I’m unsure if I’m doing it correctly. If you could take a look at my profile and provide feedback, it would be extremely helpful. Your insights will help me understand whether I’m on the right track or if there are areas I need to improve.
Additionally, I am documenting my daily progress on X to share my learning journey. Any feedback or suggestions would be greatly appreciated!
#SoftwareTesting #GitHub #LearnInPublic
2 Likes
Okay sure, I will check your profile and will share my thoughts with you.
2 Likes
Thank you, Ujjwal! I really appreciate your time and feedback. Looking forward to your insights!
To add onto what has been said. I always say look around in your area, or the area you want to work in. Look up some vacancies and their requirements; some might say Cypress, some might say A11Y, some Usability, etc etc … the things that will pop up the most is something you could look into.
2 Likes
All replies are right. To supplement what has already been said.
I think, first of all, you need a plan with a deadline. And you need a final goal. For instance, a job interview at a company that you enjoy.
And you need to check your progress every week.
Thank you, Elena! I really appreciate your thoughtful advice. Setting a plan with a deadline and tracking progress weekly sounds like a great approach. I’ll definitely keep this in mind as I work towards my goals.
1 Like
Thank you, Kristof! That’s a great suggestion. I’ll definitely look into job vacancies and their requirements to understand what skills are in demand. I appreciate your insights!
1 Like
‘i have learn manual testing’
I consider myself decent at testing overall (been in Software Engineering and Testing my whole life so far), but I barely scratched the surface of having ‘learnt’ it.
- It’s a social science: one studies the relationship between software and people. There’s so many people with so many facets, desires, thoughts, expectations. And so much software that’s built badly. I doubt you can have a clear head when reconciling what’s risky, what’s quality, what’s value, what to look into, who matters every single day in every single instance when you evaluate a product.
- It’s experimental, about exploring, experiencing: one can only tell about a product once he’s done with this, which can never happen.
- It’s about learning: product, business, domain, technical aspects, project, people, value and relationship between things, users, quality, and so on.
Always be learning deeply about testing!
2 Likes