mirror of
https://github.com/abhigyanpatwari/GitNexus.git
synced 2026-10-08 03:08:13 +00:00
Adds 8 fixture-driven integration test scenarios modelled after the
existing C/C++ and Python resolver test suites:
- ruby-pkg: require_relative imports, class inheritance (EXTENDS), module
include (IMPLEMENTS), method detection across 5 files
- ruby-ambiguous: two Handler classes in a/ and b/, require_relative to a/
disambiguates the EXTENDS target
- ruby-calls: arity-filtered call resolution — write_audit("hello") resolves
to one.rb (1-param) not zero.rb (0-params) via import-resolved
- ruby-member-calls: obj.method() member call resolves User.save via the
import map; verifies HAS_METHOD edge
- ruby-mixin-heritage: include / extend / prepend all produce IMPLEMENTS
edges; no EXTENDS emitted for any mixin form
- ruby-attr-properties: attr_accessor / attr_reader / attr_writer create
Property nodes with correct accessorType in description
- ruby-receiver-resolution: both User and Repo classes exist with save
methods; HAS_METHOD verified for each; at least one save call resolved
- ruby-local-shadow: local def save in main.rb shadows the require'd
utils.rb#save; run → save resolves to same-file definition
Co-authored-by: Gergő Magyar <magyargergo@users.noreply.github.com>
9 lines
134 B
Ruby
9 lines
134 B
Ruby
require_relative 'user'
|
|
require_relative 'repo'
|
|
|
|
def process_entities
|
|
user = User.new
|
|
repo = Repo.new
|
|
user.save
|
|
repo.save
|
|
end
|