We all know that since Covid-19 started we were all spooked, stressed and segregated from everything we love the most and all this started 31 December 2019 where the first infected person who reported to the hospital in Wuhan, China.
But this is all public information, what is not a public information is what most of us feel being stuck at home?
I usually think about how it would affect others but not myself. So I am going to give my experience throughout Covid-19 until the present day. …
All of us were over the Among Us game as soon as it was dropped because it had a unique idea on how it is played and how to win.
“Among Us is a multiplayer game where between four and 10 players are dropped onto an alien spaceship. Each player is designated a private role as a “crewmate” or “impostor.” … Players can be voted off the ship, so each game becomes one of survival: Successfully vote off the impostors, or complete all your tasks to win.” As stated in The New York Times
In the beginning, I wanted to write about each testing tool individually but I have not used it yet so I can honestly provide a full of information article about each one. But while waiting for the chance to test and understand those tools from my own perspective, I did some research on each tool and hopefully you get an idea of what they actually are and what they are good for.
Our job as testers is to test or audit the applications in whatever platform it is in and then raise it in a bug tracking management website. Previously, before having any kind of bug tracking systems, testers would collect a big number of tickets and notify the developers by sitting down in a meeting to discuss the bugs one by one. Please take note this is just a speculation of what happened in the past, not sure about how it really went before having any kind of bug tracking system.
Luckily now, we have multiple sources of bug tracking system…
Jira is a proprietary issue tracking product developed by Atlassian that allows bug tracking and agile project management.
Jira allows tracking bugs until they reach the status of “Done”. It’s good to do that and stay in the know throughout the team’s workflow of the bug status. Transitioning issues in Jira Software triggers notifications and automatically informs the next team members about the current state of the bug
Importing test cases in Jira is another way to follow up with strategies and scenarios previously created using excel sheets or any spreadsheets.
Manual testing step by step or process is to have a test case developed to know what to test, how to test it and etc.
When importing test cases in Jira, you would need to know few things like what are the fields to be filled and how to import it correctly in the correct project.
Security testing is a process intended to reveal flaws in the security mechanisms of an information system that protect data and maintain functionality as intended. Due to the logical limitations of security testing, passing the security testing process is not an indication that no flaws exist or that the system adequately satisfies the security requirements.
Typical security requirements may include specific elements of confidentiality, integrity, authentication, availability, authorization, and non-repudiation. Actual security requirements tested depend on the security requirements implemented by the system. Security testing as a term has a number of different meanings and can be completed in a…
One of the first decisions we face for each of our project implementations at Segue is “Which development methodology should we use?” This is a topic that gets a lot of discussions (and often heated debate). If this is not something you’ve worked with before, a definition of development methodology is in order; put very simply, it’s a way of organizing the work of software development. This is NOT about a style of project management or a specific technical approach, although you will often hear these terms all thrown together or used interchangeably.
The two basics, most popular methodologies are:
Waterfall methodology is a linear project management approach, where stakeholder and customer requirements are gathered at the beginning of the project, and then a sequential project plan is created to accommodate those requirements. The waterfall method is so named because each phase of the project cascades into the next, following steadily down like a waterfall.
It’s a thorough, structured methodology and one that’s been around for a long time because it works. Some of the industries that regularly use the waterfall method include construction, IT, and software development. However, the term “waterfall” is usually used in a software context.
In software development, agile (sometimes written Agile) practices approach discovering requirements and developing solutions through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end-user(s). It advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages flexible responses to change.
It was popularized by the Manifesto for Agile Software Development. The values and principles espoused in this manifesto were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.
While there is much anecdotal evidence that adopting agile practices and values improves the agility of software professionals, teams, and organizations, the…
Founder at StackedQA | Software QA Engineer | Writer @DevGenius | Kuala Lumpur Based | Topics: Lifestyle, Self-Improvement & Technology