My Key Skills 2020-2021

Industries:

Software Development, Software Quality control, Manual Testing, Test Automation, Black-box Testing, White-box Testing, Database Testing, API Testing, Performance Testing, Security Testing, Mobile Testing, Agile, Version Control, Cloud Computing, Configuration Management, Continuous Integration, DevOps.

Tools and Technologies:

§  Testing/Automation: NUnit, TestNG, Selenium IDE/WebDriver/Grid, Katalon, Appium, Protractor, Cucumber, SpecFlow, Postman, JMeter, Fiddler, SoapUI, MS Test Manager.

§  Tracking/Collaboration: TFS, Jira, Trello, Slack.

§  Source Control: Git, TFVC, GitHub, Bitbucket.

§  CI Tools: Azure DevOps, Docker.

§  Languages/Frameworks: C#, .NET Core, Java, Maven, Python, Entity Framework.

§  IDE/Editors: Visual Studio, Visual Studio Code, IntelliJ IDEA, PyCharm, Notepad++.

§  Web Technologies: HTML, CSS, Bootstrap, JavaScript, jQuery, AJAX, JSON, XML, ASP.NET, MVC, Web API.

§  Databases: MS SQL Server, MySQL, SQLite, MongoDB.

§  Operating Systems: Windows, Windows server, Linux, Android.

Software Quality in the lifecycle

Internal quality is the totality of characteristics of the software product from an internal view. Internal quality is measured and evaluated against the internal quality requirements. Details of software product quality can be improved during code implementation, reviewing and testing, but the fundamental nature of the software product quality represented by internal quality remains unchanged unless redesigned.

External Quality is the totality of characteristics of the software product from an external view. It is the quality when the software is executed, which is typically measured and evaluated while testing in a simulated environment with simulated data using external metrics. During testing, most faults should be discovered and eliminated. However, some faults may still remain after testing. As it is difficult to correct the software architecture or other fundamental design aspects of the software, the fundamental design usually remains unchanged throughout testing.

Quality in Use is the user’s view of the quality of the software product when it is used in a specific environment and a specific context of use. It measures the extent to which users can achieve their goals in a particular environment, rather than measuring the properties of the software itself.