Threats in LLM2 / GenAI , a note from NIST #MLOps #DevSecOps
According to the cyber security r&d, 
Popular posts from this blog
Typical Project flow with QA Loop in Jira (Atlassian)
Last week, one of my friend needs some help to establish Project\QA workflows on Jira (Atlassian) So here I am happy to share some of my odd solution. Project Flow problems or hard to implement in Jira were * One stage splits with multiple stages in flow. * More than one stages merges to one stage. Here We have Brainstorming splits to UT - ST stage and Dev Review - QA Review merges with Review stage executed by System Group Members in project flow. One issue splits with more than one issues, can also be implemented with sub-tasks feature but it may not push next stage in the project flow as the project progresses; all sub-tasks are linked to the parent task only, may not execute inline flow; may not give more control to administrator\lead and may be more complicated to maintain. Sub-tasks may not be merged to one task on transitions after Dev. Review / QA Review merges to Review stage. Core objective is to implement flow that anyone can see each stage of the flow and can
Increase ROI in your organization with Automation Testing
This article offers answers for below questions with case-study Why do we need automation s/w testing in organization? What if organization does not have fund to purchase license for expensive automation tools? In simple way, we can say the core objective of automation is helping to finish any testing\QA task more accurate, easier and faster way with less risk involved for failure. Say for example Tools like # Functional automation tools QTPro, SilkTest, Canoo, Selenium, VBMacro. # Load/Stress automation tools LoadRunner, SilkPerformer. # Cookies reader tools. # HTTP request / response reader tools. # File comparison tools. # Tesecase Management Tools. # Web Page link / image finder Tools. # Broken link finder Tools. and many other tools we can categorize in automation testing fashion to make QA Process more smoother; Automation Testing also used for Repetitive testing task activities… As a human nature, manual tester can not perform repetitive tasks more accurately comparing to mach
Test Plan IEEE 829-1983 explained by me
Tip to create workflow in JIRA quickly
To my colleagues who want to create quickly new workflow and don't want to touch xml \ property files. On Administrator \ Workflows If you don't have default workflow then create default Workflow with default JIRA "workflow" - it will show status as "active" so we cannot update its scheme \ workflow steps. Copy this workflow -- it has status as "Inactive" so we can update workflow scheme. Go to link "steps" and add new status \ transitions for new steps as required in your workflow. On Administrator \ Workflow Schemes Create new "Workflow Scheme" then click on "Workflows" link operation of new workflow just created. Assign workflow to scheme,... Issue type "Bug" and select our workflow from the list. Assign other workflows for issue types : Task, New Feature or Improvement with default workflow ( named JIRA ) or your workflow. Now our workflow scheme is ready to associate with our project. Go to you
Headless Automation Testing
Headless Testing means testing without GUI. There are couple of testing such as Unit testing, Component Testing, Module Testing, Integration Testing, CC (Code Coverage of Condition) Testing \ Base Path Testing, Mutation Testing, DB Testing, API Testing and or Web Service Testing may fall under Headless Testing. As you can see most of testing are white box or gray box testing. In XP\XT (Extreme Programming\Extreme Testing) of agile, It is the first step in implementing story. Open Source tools such as Watir, Warin, Junit, Nunit, HTTPUnit, HTMLUnit, WebTest Canoo, Fitness, Selenium RC and scripts like shell, vbscript, groovy, SoapUI (and some good paid tools Autoczar, QTP, SilkTest, TestComplete) are helping to automate this type of testing and play effective and efficient role in the QA feedback of product lifecyle. It actually tells us where is the issue. So, always say "Yes" to Headless Testing in your project.
QuickTest Pro and Traceability Matrix
I like to share one automation experience or in other sense the challenge I had in automation. I joined one company as an Automation Quality Analyst Consultant. It is fast growing Company. I was as a tool smith like person recommending tools for QA team to make manual testing tasks more easier\reliable and fast way. We had established freeware tools for testcase management, defect repository and qa\project process and developed test-suites for regression and smoke testing in QTP. As we all know regression test-suite is bulky one and at that time, mine was including more then 617 testcases automated and that’s why taking more than 3 hours to finish execution. I have split test scripts on functionality vise and created test batch but the problem is test batch report does not give status for each testcases in automation execution and that encourage me to develop “TM live” tool interfaced with QTP 9.1. “TM live” means Traceability Matrix on live (parallel with automation suite execution)
AFT (Automation Framework Team) should not take developers' false catches
What does It mean by "developers' false catches" ? It means those implementations or application unexpected behaviors which should not be automated with automation framework. Why those should not be the candidates for automation? It is observed that adding these kinds of requirements in automation may set short ROI for organizations but it never becomes for long terms – You may ask “why” again, below are couple of examples which put more lights on this question. Case-Study : #1 “Product Team has new requirements in build 1.2.x like objects inputs are changed with prefix or suffix strings and that affects more than 1000 automated test-case(s)” Due to limited resources and short dead line to certify build(1.2.x) of the product, Product lead comes to AFT and asks for help. He requests to update Automation Framework in such a way that manages prefix and suffix inputs and his team does not have to update their test-case(s). As part of the service team (AFT), we provided soluti
Testing Priciples & Vocabulary
The principles can be defined as 1. a rule or code of conduct; 2. a general or fundamental, law, doctrine or assumption; In software domain, these principles focus lights to test engineers on software systems, how suppose to build them and how they expect to behave. Principle #1 Testing is the process of exercising a software component using a selected set of test cases, with the intent of (a) revealing defects, (b) evaluating quality. The term “defects” used in this and in subsequent principles represents any deviations in the software that have negative impact on its functionality, performance, reliability, security and or any other of its specified quality attributes. Principle #2 When the test objective is to detect defects, then a good test case is one that has a high probability of revealing a yet undetected defect(s). The test engineer expects to work as scientist does like he creates hypotheses to prove or disprove them; that is determine if the specific defect is present or
QA Project Checklist
Here is I want to share qa project management checklist I used in real scenarious. Project Initiation Prepare System Test Estimates Define System Test Approach Define Testing Scope Prepare DRAFT System Test Plan Review System Test Plan Prepare Test Schedule Request Test Resources Request Business Expert Request Management Support Request Environment / Technical Support Request Facilities (Desk, Chair etc.) Setup Test Project Folder Revise Test Estimates Define Entrance / Acceptance Criteria Agree Communication Channels Agree Reporting Procedures, Methods and Frequency Define Exit Criteria Design Release Notes Template Test Preparation Agree Builds / Drops Schedule and Contents Agree Release Notes Contents and Format Agree Error Management Procedures Define System Test Roles and Responsibilities Assign Test Roles and Responsibilities Assign Test Case Preparation Primary Responsibilities Assign Test Case Preparation Secondary Responsibilities Prepare High Level Test Cases Prepare Low Lev
How to automate test-scenarios which have Java Objects built on JMesa , JQuery, JSON and AJAX technology.
I had a challenging project to automate Java Objects on the fly – sharing some part of it. Challenges I faced 1. Objects which are built on top of JMesa , JQuery, JSON and AJAX technology -- are not recognized by professional automation tools (such as QTP and SilkTest). 2. How to automate Dynamic Graphs which are implemented with technologies like Flotr and 3D Canvas. 3. Web application needs to automate with cross-browsers ( IE 6.0+ , FF 2.0+ or Safari 2.0+ ) It focus objects screen rendering issues which are different from one browser to other. How can we overcame • Challenge #1 and #2 can be resolved with below automation approach. Verify HTTP Responses when user does some actions like objects fire specific AJAX calls; We simulate these AJAX calls ( HTTP requests ), capture valid\expected response, set them as baseline and in QA loop we simulate user actions again with automation, capture actual response and compare with baseline. • Challenge #3 can be resolved with below automatio
Comments
Post a Comment